ISO 27001:2022 A.8.25: Secure development life cycle
Secure development life cycle is asked by 5 of the 48 carrier applications, through 7 questions. The evidence to have on file is Documented secure development rules or SDLC standard covering environments, methodology, coding guidelines, security requirements, checkpoints, testing, repositories and version control. 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.25?
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.25, showing inclusion or justified exclusion, implementation status and the risks it treats
- Documented secure development rules or SDLC standard covering environments, methodology, coding guidelines, security requirements, checkpoints, testing, repositories and version control
- Secure coding guidelines for each language in use
- Project records showing security checkpoints or gates passed
- Security testing outputs such as static analysis, regression and penetration test results
Common gaps an assessor names
- The SDLC standard exists but projects skip the security gates under schedule pressure
- Coding guidelines cover only one language while several are used
- Low-code, scripting and spreadsheet development fall outside the rules
- Outsourced development is accepted without any evidence of secure practices
The one or two items a carrier would actually ask for
- Documented secure development rules or SDLC standard covering environments, methodology, coding guidelines, security requirements, checkpoints, testing, repositories and version control
- Secure coding guidelines for each language in use
The application questions that reach A.8.25 (7)
Controls reached by the same questions
A.6.3 (ISO 27001:2022), A.8.26 (ISO 27001:2022), A.8.28 (ISO 27001:2022), CC1.4 (SOC 2), CC2.2 (SOC 2), CC8.1 (SOC 2), ID.RA-09 (NIST CSF 2.0), PI1.3 (SOC 2), PR.AT-01 (NIST CSF 2.0), PR.PS-06 (NIST CSF 2.0), Requirement 12 (PCI DSS 4.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.