A.5.8 Organizational
Information security in project management
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (15)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- SA-3domain mandateimplements — A.5.8 requires information security to be integrated into project management across the full project life cycle; SA-3 operationalizes that exact outcome by mandating an SDLC process that incorporates security and privacy considerations throughout development and acquisition.
Aligned NIST CSF 2.0 outcomes (20)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- ID.RA-05domain mandateimplements — A.5.8 requires addressing information security risks (including threats/vulnerabilities/likelihoods/impacts) throughout the project life cycle, which directly operationalizes the risk-understanding and prioritization outcome named in ID.RA-05 within the project-management domain
- ID.RA-06domain mandateimplements — A.5.8 requires addressing information security risks (including choosing/planning/tracking responses) throughout the project life cycle, which directly operationalizes the risk-response activities named in ID.RA-06 within the project-management domain
Related OWASP ASVS 5.0 requirements (13)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Related weaknesses / CWE (4)
Weakness classes this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Mitigated MITRE ATT&CK techniques (3289)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- T1190partialprevents — Requiring threat modelling and security requirements at project inception leads to design choices that close the common entry points adversaries exploit in public-facing applications.
- T1677partialprevents — A.5.8 mandates that information security risks be assessed and treated throughout the project lifecycle, which for CI/CD pipeline projects would derive requirements like access controls on pipeline configuration, code review, and secrets management that constrain T1677; however, A.5.8 is a governance/process control that requires these be considered and implemented, not the technical control that actually blocks the poisoning — the prevention lives in the controls the process mandates, leaving a bounded remainder where projects skip or inadequately perform the required risk treatment.
Prevented OWASP Web Top 10 (2025) risks (13)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- A06partialblocks — A.5.8 mandates integrating security risk assessment, requirements derivation (including from threat modelling), and design-level protections into the project lifecycle, which directly blocks many insecure-design weaknesses from being baked in; it is not a complete barrier because flawed designs can still arise from incomplete application of the process or from risks outside the identified set.
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.