ISO 27001:2022 5.8: Information security in project management

What else in your programme already covers this

This control maps to 58 controls across 28 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 27701:2019 · 9 controls

5.4 Planning
5.4.1 Actions to address risks and opportunities
5.8 Improvement
7.4 Privacy by design and privacy by default
7.4.1 Limit collection
7.4.2 Limit processing
7.4.5 PII de-identification and deletion at the end of processing
8.4 Privacy by design and privacy by default
8.4.2 Return, transfer or disposal of PII

NIST SP 800-53 Rev 5 · 7 controls

NIST800-PL-2 PL-2 System Security and Privacy Plans
NIST800-PL-7 PL-7 Concept of Operations
NIST800-PM-11 PM-11 Mission and Business Process Definition
NIST800-PM-14 PM-14 Testing, Training, and Monitoring
NIST800-SA-3 SA-3 System Development Life Cycle
NIST800-SA-8 SA-8 Security and Privacy Engineering Principles
SP800-53-PL Planning Family

SOC 2 · 4 controls

SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

COBIT 2019 · 3 controls

BAI01.01 BAI01.01 Maintain a standard approach for program management
BAI11.01 BAI11.01 Maintain a standard approach for project management
BAI11.06 BAI11.06 Manage project risk

FedRAMP High · 3 controls

IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
PL-2 System Security and Privacy Plans
SA-3 System Development Life Cycle

FedRAMP Moderate · 3 controls

IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
PL-2 System Security and Privacy Plans
SA-3 System Development Life Cycle

ISO/IEC 42001:2023 · 3 controls

A.2.3 Alignment with other organizational policies
A.6 AI system life cycle
A.6.2.2 AI system requirements and specification

Azure Security Benchmark · 2 controls

ASBv3-DS-1 Conduct threat modeling
ASBv3-GS-10 Define and implement DevOps security strategy

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

CFTC-SS-3 Information Security Category
CFTC-SS-5 Systems Development and Quality Assurance Category

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-AIS-04 Secure Application Design and Development
CCM-DSP-07 Data Protection by Design and Default

ISO 27001:2013 · 2 controls

A.14.1.1 Information security requirements analysis and specification
A.6.1.5 Information security in project management

ISO/IEC 29100:2024 · 2 controls

29100-6.10 Information security
ISO29100-5.10.10 Information Security

APRA CPS 230 Operational Risk Management · 1 control

CPS230-P26 Assessment of Business and Strategic Decisions on the Risk Profile

AWS Well-Architected Security Pillar · 1 control

SEC01-BP07 Identify threats and prioritize mitigations using a threat model

C5 (Germany) · 1 control

C5-DEV-01 Policies for the development/procurement of information systems

CIS Controls v8 · 1 control

CIS-16.1 Establish and Maintain a Secure Application Development Process

CMMC 2.0 · 1 control

CM.L2-3.4.4 Security Impact Analysis

EU AI Act · 1 control

EUAI-Art.9 Risk management system

GDPR · 1 control

GDPR-Art.35 Data protection impact assessment

ISO 27002:2022 · 1 control

5.8 Information security in project management

NIS2 Directive · 1 control

Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-161 Rev 1 · 1 control

161R1-SA-3 System Development Life Cycle

NIST SP 800-171 Rev 3 · 1 control

03.16.01 Security Engineering Principles

NIST SP 800-172 · 1 control

3.13.2e Introduce Unpredictability into System Operations

NIST SP 800-218 · 1 control

SP800-218-PO.1.1 Define Security Requirements for Software Development

PCI DSS 4.0 · 1 control

6.5.2 6.5.2 Confirm PCI DSS controls after significant change

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 5.8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gaps If you hold ISO 27001:201383.9% covered · 15 gaps If you hold FedRAMP Moderate80.6% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gaps If you hold C5 (Germany)69.9% covered · 28 gaps If you hold NIST Cybersecurity Framework 2.063.4% covered · 34 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free