ISO 27001:2022 8.26: Application security requirements

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 8 controls

NIST800-RA-8 RA-8 Privacy Impact Assessments
NIST800-SA-15 SA-15 Development Process, Standards, and Tools
NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design
NIST800-SA-22 SA-22 Unsupported System Components
NIST800-SA-4 SA-4 Acquisition Process
NIST800-SA-8 SA-8 Security and Privacy Engineering Principles
NIST800-SC-3 SC-3 Security Function Isolation
NIST800-SI-10 SI-10 Information Input Validation

FedRAMP High · 6 controls

SA-11 Developer Testing and Evaluation
SA-15 Development Process, Standards, and Tools (SA-15)
SA-3 System Development Life Cycle
SA-4 Acquisition Process
SA-8 Security and Privacy Engineering Principles
SI-10 Information Input Validation

FedRAMP Moderate · 6 controls

SA-11 Developer Testing and Evaluation
SA-15 Development Process, Standards, and Tools (SA-15)
SA-3 System Development Life Cycle
SA-4 Acquisition Process
SA-8 Security and Privacy Engineering Principles
SI-10 Information Input Validation

ISO 27002:2022 · 5 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.26 Application security requirements
8.28 Secure coding
8.29 Security testing in development and acceptance

NIST SP 800-218 · 5 controls

SP800-218-PO.1.1 Define Security Requirements for Software Development
SP800-218-PO.4.1 Criteria for Software Security
SP800-218-PW.1.1 Design Software to Meet Security Requirements
SP800-218-PW.1.2 Track Security Requirements, Risks, and Decisions
SP800-218-PW.4.4 Verify Acquired Components Meet Security Requirements

PCI DSS 4.0 · 5 controls

6.2.1 6.2.1 Secure development of bespoke and custom software
6.2.4 6.2.4 Engineering techniques against common software attacks
6.4.1 6.4.1 Public web application review or automated protection
6.3.1 6.3.1 Vulnerability identification and risk ranking
6.5.1 6.5.1 Change control procedure for production

CIS Controls v8 · 4 controls

CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.10 Apply Secure Design Principles in Application Architectures
CIS-16.11 Leverage Vetted Modules or Services for Application Security Components
CIS-16.14 Conduct Threat Modeling

SOC 2 · 4 controls

SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

Azure Security Benchmark · 3 controls

ASBv3-DS-1 Conduct threat modeling
ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
ASBv3-NS-6 Deploy web application firewall

C5 (Germany) · 3 controls

C5-DEV-01 Policies for the development/procurement of information systems
C5-PI-01 Documentation and safety of input and output interfaces
C5-PSS-09 Authorisation Mechanisms

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP03 Identify and validate control objectives
SEC01-BP07 Identify threats and prioritize mitigations using a threat model

COBIT 2019 · 2 controls

BAI02.01 BAI02.01 Define and maintain business functional and technical requirements
BAI02.03 BAI02.03 Manage requirements risk

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

CCM-AIS-01 Application and Interface Security Policy and Procedures
CCM-AIS-02 Application Security Baseline Requirements

EU AI Act · 2 controls

EUAI-Art.15 Accuracy, robustness and cybersecurity
EUAI-Art.8 Compliance with the requirements

ISO 27001:2013 · 2 controls

A.14.1.2 Securing application services on public networks
A.14.1.3 Protecting application services transactions

NIST SP 800-161 Rev 1 · 2 controls

161R1-SA-17 Developer Security and Privacy Architecture and Design
161R1-SA-4 Acquisition Process

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-5 Systems Development and Quality Assurance Category

ISO 27701:2019 · 1 control

6.11.1 Security requirements of information systems

ISO/IEC 42001:2023 · 1 control

A.6.2.2 AI system requirements and specification

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-172 · 1 control

3.13.2e Introduce Unpredictability into System Operations

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 8.26 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