NIST SP 800-218 SP800-218-PO.1.1: Define Security Requirements for Software Development

What else in your programme already covers this

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

BSIMM · 4 controls

CP1.1 Unify regulatory pressures
CP1.2 Identify privacy (PII) obligations
CP1.3 Create software security policy
SR1.3 Translate compliance constraints to requirements

C5 (Germany) · 3 controls

C5-COM-01 Identification of applicable legal, regulatory, self-imposed or contractual requirements
C5-DEV-01 Policies for the development/procurement of information systems
C5-SP-02 Review and Approval of Policies and Instructions

ISO 27001:2022 · 3 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.26 Application security requirements

ISO 27002:2022 · 3 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.26 Application security requirements

ISO/IEC 42001:2023 · 3 controls

6.1.2 AI risk assessment
7.5.2 Creating and updating documented information
A.6.2.2 AI system requirements and specification

NIST SP 800-161 Rev 1 · 3 controls

161R1-SA-1 Policy and Procedures
161R1-SA-3 System Development Life Cycle
161R1-SA-4 Acquisition Process

NIST SP 800-53 Rev 5 · 3 controls

NIST800-SA-15 SA-15 Development Process, Standards, and Tools
NIST800-SA-3 SA-3 System Development Life Cycle
NIST800-SA-8 SA-8 Security and Privacy Engineering Principles

PCI DSS 4.0 · 3 controls

6.1.1 6.1.1 Requirement 6 policies and procedures maintained and communicated
6.2.1 6.2.1 Secure development of bespoke and custom software
6.2.3 6.2.3 Code review before release

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

FedRAMP High · 2 controls

SA-15 Development Process, Standards, and Tools (SA-15)
SA-3 System Development Life Cycle

FedRAMP Moderate · 2 controls

SA-15 Development Process, Standards, and Tools (SA-15)
SA-3 System Development Life Cycle

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
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.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

AWS Well-Architected Security Pillar · 1 control

SEC01-BP03 Identify and validate control objectives

Azure Security Benchmark · 1 control

ASBv3-GS-10 Define and implement DevOps security strategy

CIS Controls v8 · 1 control

CIS-16.1 Establish and Maintain a Secure Application Development Process

HIPAA Security Rule · 1 control

164.306 Security Standards: General Rules

NIST SP 800-171 Rev 3 · 1 control

03.15.01 Policy and Procedures

OpenSSF Best Practices Badge Criteria · 1 control

silver.documentation_security documentation_security (Silver, MUST)

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 NIST SP 800-218 have you already done?

NIST SP 800-218 SP800-218-PO.1.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-218 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 30 of 42 NIST SP 800-218 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.4% covered · 12 gaps If you hold C5 (Germany)61.9% covered · 16 gaps If you hold NIST SP 800-161 Rev 161.9% covered · 16 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.152.4% covered · 20 gaps If you hold ISO 27002:202252.4% covered · 20 gaps If you hold Azure Security Benchmark50% covered · 21 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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