ISO 27001:2022 · Organizational controls
ISO 27001:2022 5.8: Information security in project management
ISO 27001:2022 5.8 covers Information security in project management. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.5.8, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Security is only considered for ICT development projects, not facilities or business process projects.
Information security is to be built into the way projects are managed. Purpose (stated in ISO/IEC 27002:2022): ensures security risks of projects and their deliverables are addressed throughout the project life cycle. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.8.
What evidence supports 5.8?
- Annex A organizational controlStatement of Applicability entry for control A.5.8, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A organizational controlThe project management methodology showing mandatory security steps at initiation and at defined stage gates
- Annex A organizational controlProject risk registers containing information security risks assessed early and revisited during the project
- Annex A organizational controlDocumented security requirements for the deliverable, derived from policy, regulation, threat modelling and classification of the information involved
- Annex A organizational controlStage-gate or steering committee minutes recording review of the security work
Where this requirement comes from
This is our own statement of ISO 27001:2022 5.8, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Security is only considered for ICT development projects, not facilities or business process projects
- Security requirements are added late, after design decisions are fixed
- Risks from running the project itself, such as insecure sharing with external partners, are ignored
- No stage gate checks whether security treatments actually work
How it maps to SOC 2
No reviewed link is held for this control.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.