NIST SP 800-218 218-PW.1.1: Design Software to Meet Security Requirements

What else in your programme already covers this

This control maps to 51 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-161 Rev 1 · 5 controls

161R1-PL-8 Security and Privacy Architectures
161R1-RA-3 Risk Assessment
161R1-SA-17 Developer Security and Privacy Architecture and Design
161R1-SA-3 System Development Life Cycle
161R1-SA-8 Security and Privacy Engineering Principles

BSIMM · 4 controls

AA1.4 Use a risk-ranking methodology for applications
AA2.1 Perform architecture analysis using STRIDE or equivalent
AM1.3 Identify potential attackers
SFD1.2 Engage architecture teams with security

NIST SP 800-53 Rev 5 · 4 controls

NIST800-PL-8 Security and privacy architectures
NIST800-RA-3 Risk assessment
NIST800-SA-17 Developer Security and Privacy Architecture and Design. Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that: Is consistent with the organization's
NIST800-SA-8 Security and privacy engineering principles

C5 (Germany) · 3 controls

C5-DEV-01 Policies for the development/procurement of information systems
C5-DEV-05 Risk assessment, categorisation and prioritisation of changes
C5-OIS-07 Application of the Risk Management Policy

FedRAMP High · 3 controls

RA-3 Risk Assessment
SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses. Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing
SA-8 Security and Privacy Engineering Principles

FedRAMP Moderate · 3 controls

RA-3 Risk Assessment
SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses. Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing
SA-8 Security and Privacy Engineering Principles

SOC 2 · 3 controls

SOC2-CC3.2 COSO principle 7: Identifies risks and analyzes to determine how managed
SOC2-CC8.1 Change management processes are in place
SOC2-PI1.3 System processing is complete, valid, accurate, timely, and authorized

CIS Controls v8 · 2 controls

CIS-16.10 Apply Secure Design Principles in Application Architectures
CIS-16.14 Conduct Threat Modeling

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:2022 · 2 controls

8.26 Application security requirements
8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 2 controls

8.26 Application security requirements
8.27 Secure system architecture and engineering principles

ISO/IEC 42001:2023 · 2 controls

6.1.2 Risk assessment
6.1.3 Risk treatment

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-ID.RA-03 Internal and external threats to the organization are identified and recorded
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-171 Rev 3 · 2 controls

03.11.01 Risk Assessment
03.16.01 Security Engineering Principles

NIST SP 800-172 · 2 controls

3.11.1e Threat-Aware Risk Assessment
3.13.2e Introduce Unpredictability into System Operations

NIST SP 800-53 Rev 5 LOW · 2 controls

RA-3 Risk Assessment
SA-8 Security and Privacy Engineering Principles

NIST SP 800-53 Rev 5 MODERATE · 2 controls

RA-3 Risk Assessment
SA-8 Security and Privacy Engineering Principles

NIST SP 800-53 Revision 5.1 HIGH · 2 controls

RA-3 Risk Assessment
SA-8 Security and Privacy Engineering Principles

AWS Well-Architected Security Pillar · 1 control

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

Azure Security Benchmark · 1 control

ASBv3-DS-1 Conduct threat modeling

CMMC 2.0 · 1 control

SC.L2-3.13.2 Security Engineering

PCI DSS 4.0 · 1 control

6.2.1 Bespoke and custom software are developed securely, as follows: • Based on industry standards and/or best practices for secure development. • In accordance with PCI DSS (for example, secure authentication and logging). • Incorporating

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 218-PW.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