ISO 27001:2022 A.8.28: Secure coding
Secure coding is asked by 5 of the 48 carrier applications, through 6 questions. The evidence to have on file is Secure coding standards and a minimum baseline applying to in-house and outsourced development, updated from current threat and vulnerability information. This page maps the control to the questions that reach it; it never says whether an applicant will be offered cover.
ISO 27001:2022 is read as the publisher's combined inventory: 93 Annex A controls plus 30 management-system clauses. Every requirement here is our statement of its clause, cited to it, not the instrument verbatim.
Which carriers ask this control?
5 carrier applications reach this control: Arch Insurance, Aspen American Insurance Company, Hiscox, Markel, Munich Re. A carrier named here is a source document, never a customer or an endorsement.
What evidence should be on file for A.8.28?
Evidence guidance is our wording, not a statement of any standard and not binding on a carrier or an assessor.
- Statement of Applicability entry for control A.8.28, showing inclusion or justified exclusion, implementation status and the risks it treats
- Secure coding standards and a minimum baseline applying to in-house and outsourced development, updated from current threat and vulnerability information
- IDE and pipeline configuration enforcing secure coding checks, including SAST results and remediation records
- Threat models and peer review records for significant changes
- Pre-release records of attack surface review and mitigation of common programming errors
Common gaps an assessor names
- Hard-coded credentials and secrets appear in source code
- Open source libraries are pulled in without inventory or update tracking
- SAST findings are ignored or suppressed without review
- Vendor packages are modified locally with no assessment of future maintenance impact
The one or two items a carrier would actually ask for
- Secure coding standards and a minimum baseline applying to in-house and outsourced development, updated from current threat and vulnerability information
- IDE and pipeline configuration enforcing secure coding checks, including SAST results and remediation records
The application questions that reach A.8.28 (6)
Controls reached by the same questions
A.8.25 (ISO 27001:2022), A.8.26 (ISO 27001:2022), CC8.1 (SOC 2), ID.RA-09 (NIST CSF 2.0), PI1.3 (SOC 2), PR.PS-06 (NIST CSF 2.0), Requirement 6 (PCI DSS 4.0).
This control on the island, all controls on the controls index, the framework on the ISO 27001:2022 page, the carriers on sources. Map your own answers in the tool.