NIST SP 800-171 Rev 3 03.16.01: Security Engineering Principles

What else in your programme already covers this

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

AWS Well-Architected Security Pillar · 4 controls

SEC01-BP06 Automate deployment of standard security controls
SEC01-BP07 Identify threats and prioritize mitigations using a threat model
SEC11-BP02 Automate testing throughout the development and release lifecycle
SEC11-BP04 Conduct code reviews

ISO 27002:2022 · 4 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.26 Application security requirements
8.27 Secure system architecture and engineering principles

NIST SP 800-218 · 4 controls

SP800-218-PW.1.1 Design Software to Meet Security Requirements
SP800-218-PW.1.3 Support Standardized Security Features
SP800-218-PW.2.1 Qualified Review of Software Design
SP800-218-PW.5.1 Secure Coding Practices

Azure Security Benchmark · 3 controls

ASBv3-DS-1 Conduct threat modeling
ASBv3-GS-10 Define and implement DevOps security strategy
ASBv3-GS-4 Define and implement network security strategy

FedRAMP High · 3 controls

PL-8 Security and Privacy Architectures
SA-3 System Development Life Cycle
SA-8 Security and Privacy Engineering Principles

FedRAMP Moderate · 3 controls

PL-8 Security and Privacy Architectures
SA-3 System Development Life Cycle
SA-8 Security and Privacy Engineering Principles

ISO 27001:2022 · 3 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.27 Secure system architecture and engineering principles

NIST SP 800-53 Rev 5 · 3 controls

NIST800-PL-8 PL-8 Security and Privacy Architectures
NIST800-SA-3 SA-3 System Development Life Cycle
NIST800-SA-8 SA-8 Security and Privacy Engineering Principles

SOC 2 · 3 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)
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

CFTC-SS-5 Systems Development and Quality Assurance Category
CFTC-SS-7 Generally Accepted Standards and Best Practices

CIS Controls v8 · 2 controls

CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.10 Apply Secure Design Principles in Application Architectures

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

6.11.1 Security requirements of information systems
6.11.2 Security in development and support processes

NIST SP 800-161 Rev 1 · 2 controls

161R1-PL-8 Security and Privacy Architectures
161R1-SA-8 Security and Privacy Engineering Principles

NIST SP 800-172 · 2 controls

3.13.2e Introduce Unpredictability into System Operations
3.13.3e Confuse and Mislead Adversaries

PCI DSS 4.0 · 2 controls

6.2.1 6.2.1 Secure development of bespoke and custom software
6.2.4 6.2.4 Engineering techniques against common software attacks

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

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

APRA CPS 234 · 1 control

CPS234-21 Implementation of Information Security Controls

C5 (Germany) · 1 control

C5-DEV-01 Policies for the development/procurement of information systems

CMMC 2.0 · 1 control

SC.L2-3.13.2 Security Engineering

NIS2 Directive · 1 control

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

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

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-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.16.01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

If you hold PCI DSS 4.071.1% covered · 28 gaps If you hold C5 (Germany)68% covered · 31 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.164.9% covered · 34 gaps If you hold ISO 27001:202262.9% covered · 36 gaps If you hold CIS Controls v853.6% covered · 45 gaps If you hold NIST SP 800-161 Rev 152.6% covered · 46 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 PCI DSS 4.0 pair alone.

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