NIST SP 800-218 SP800-218-PW.1.2: Track Security Requirements, Risks, and Decisions

What else in your programme already covers this

This control maps to 27 controls across 15 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 · 4 controls

NIST800-SA-11 Developer testing and evaluation
NIST800-SA-15 Development process, standards, and tools
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

ISO/IEC 42001:2023 · 3 controls

6.1.2 Risk assessment
7.5.3 Control of documented information
A.6.2.3 Documentation of AI system design and development

NIST SP 800-161 Rev 1 · 3 controls

161R1-PL-2 System Security and Privacy Plans
161R1-RA-7 Risk Response
161R1-SA-17 Developer Security and Privacy Architecture and Design

BSIMM · 2 controls

AM1.2 Create a data classification scheme and inventory
AM1.5 Gather and use attack intelligence

C5 (Germany) · 2 controls

C5-DEV-05 Risk assessment, categorisation and prioritisation of changes
C5-OIS-06 Risk Management Policy

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

CCM-AIS-02 Application Security Baseline Requirements
CCM-GRC-02 Risk Management Program

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

SOC 2 · 2 controls

SOC2-CC8.1 Change management processes are in place
SOC2-PI1.1 Obtains or generates and uses relevant quality information to support processing integrity

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

FedRAMP High · 1 control

SA-4(2) Acquisition Process | Design and Implementation Information for Controls. Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: [Selection (one or

FedRAMP Moderate · 1 control

SA-4(2) Acquisition Process | Design and Implementation Information for Controls. Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: [Selection (one or

NIST SP 800-172 · 1 control

3.11.4e Security Solution Rationale Document

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