ISO 27001:2022 8.28: Secure coding

What else in your programme already covers this

This control maps to 54 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.

CIS Controls v8 · 6 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.12 Implement Code-Level Security Checks
CIS-16.14 Conduct Threat Modeling
CIS-16.9 Train Developers in Application Security Concepts and Secure Coding

ISO 27002:2022 · 5 controls

8.25 Secure development life cycle
8.26 Application security requirements
8.27 Secure system architecture and engineering principles
8.28 Secure coding
8.29 Security testing in development and acceptance

NIST SP 800-218 · 5 controls

SP800-218-PW.4.1 Reuse Trusted Software Components
SP800-218-PW.5.1 Secure Coding Practices
SP800-218-PW.6.1 Configure Compilation and Build Processes Securely
SP800-218-PW.7.1 Code Review
SP800-218-PW.7.2 Perform Code Review and Analysis

NIST SP 800-53 Rev 5 · 5 controls

NIST800-SA-11 SA-11 Developer Testing and Evaluation
NIST800-SA-15 SA-15 Development Process, Standards, and Tools
NIST800-SI-11 SI-11 Error Handling
NIST800-SI-15 SI-15 Information Output Filtering
NIST800-SI-7 SI-7 Software, Firmware, and Information Integrity

PCI DSS 4.0 · 4 controls

6.2.1 6.2.1 Secure development of bespoke and custom software
6.2.3.1 6.2.3.1 Manual code review independence and approval
6.2.4 6.2.4 Engineering techniques against common software attacks
8.6.2 8.6.2 No hard-coded passwords for interactive system accounts

AWS Well-Architected Security Pillar · 3 controls

SEC11-BP01 Train for application security
SEC11-BP02 Automate testing throughout the development and release lifecycle
SEC11-BP04 Conduct code reviews

Azure Security Benchmark · 3 controls

ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
ASBv3-IM-8 Restrict the exposure of credential and secrets
DS-6 Enforce security of workload throughout DevOps lifecycle

FedRAMP High · 3 controls

SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
SA-15 Development Process, Standards, and Tools (SA-15)
SI-11 Error Handling

FedRAMP Moderate · 3 controls

SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
SA-15 Development Process, Standards, and Tools (SA-15)
SI-11 Error Handling

C5 (Germany) · 2 controls

C5-DEV-04 Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools
C5-PSS-04 Error handling and Logging Mechanisms

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

CCM-AIS-04 Secure Application Design and Development
CCM-AIS-05 Automated Application Security Testing

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

SOC 2 · 2 controls

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)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-01 Train Operational Teams in Information System Security

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-4 Formal vulnerability management program

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

CFTC-SS-5 Systems Development and Quality Assurance Category

CMMC 2.0 · 1 control

SC.L2-3.13.2 Security Engineering

COBIT 2019 · 1 control

BAI03.03 BAI03.03 Develop solution components

ISO 27701:2019 · 1 control

6.11.2 Security in development and support processes

NIS2 Directive · 1 control

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

NIST SP 800-161 Rev 1 · 1 control

161R1-SA-15 Development Process, Standards, and Tools

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.28 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