ISO 27001:2022 A.8.26: Application security requirements
Application security requirements is asked by 5 of the 48 carrier applications, through 7 questions. The evidence to have on file is Approved application security requirements documents for new or acquired applications, derived from risk assessment with security specialist input. 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.26?
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.26, showing inclusion or justified exclusion, implementation status and the risks it treats
- Approved application security requirements documents for new or acquired applications, derived from risk assessment with security specialist input
- Requirement checklists covering authentication, classification, access segregation, attack resilience, legal and privacy needs, data protection, encryption, input and output controls, logging and error handling
- Additional requirements for partner transactional services covering identity trust, integrity mechanisms, approval authority and non-repudiation
- Payment and ordering application requirements covering verification, duplication prevention and storage away from public exposure
Common gaps an assessor names
- Applications are bought on functionality alone with security requirements never specified
- Requirements are generic and not derived from any risk assessment
- Free-text fields collect personal data that nobody planned to protect
- Verbose error messages disclose internal details to users
The one or two items a carrier would actually ask for
- Approved application security requirements documents for new or acquired applications, derived from risk assessment with security specialist input
- Requirement checklists covering authentication, classification, access segregation, attack resilience, legal and privacy needs, data protection, encryption, input and output controls, logging and error handling
The application questions that reach A.8.26 (7)
Controls reached by the same questions
A.6.3 (ISO 27001:2022), A.8.25 (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.