NIST SP 800-218 SP800-218-PW.1.3: Support Standardized Security Features

What else in your programme already covers this

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

C5 (Germany) · 3 controls

C5-CRY-01 Policy for the use of encryption procedures and key management
C5-PSS-06 Session Management
C5-PSS-09 Authorisation Mechanisms

Azure Security Benchmark · 2 controls

ASBv3-IM-5 Use single sign-on (SSO) for application access
IM-3 Manage application identities securely and automatically

CIS Controls v8 · 2 controls

CIS-16.10 Apply Secure Design Principles in Application Architectures
CIS-16.11 Leverage Vetted Modules or Services for Application Security Components

NIST SP 800-161 Rev 1 · 2 controls

161R1-SA-8 Security and Privacy Engineering Principles
161R1-SC-27 Platform-Independent Applications

NIST SP 800-53 Rev 5 · 2 controls

NIST800-SA-8 SA-8 Security and Privacy Engineering Principles
NIST800-SC-13 SC-13 Cryptographic Protection

AWS Well-Architected Security Pillar · 1 control

SEC01-BP05 Reduce security management scope

BSIMM · 1 control

SFD1.1 Build and publish security features

CMMC 2.0 · 1 control

SC.L2-3.13.2 Security Engineering

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-CEK-04 Encryption Algorithm

FedRAMP High · 1 control

SA-8 Security and Privacy Engineering Principles

FedRAMP Moderate · 1 control

SA-8 Security and Privacy Engineering Principles

ISO 27001:2022 · 1 control

8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 1 control

8.27 Secure system architecture and engineering principles

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-171 Rev 3 · 1 control

03.16.01 Security Engineering Principles

OpenSSF Best Practices Badge Criteria · 1 control

passing.crypto_published crypto_published (Passing, 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-PW.1.3 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