NIST 800-171 3.13.2 (SC.L2-3.13.2): Security Engineering

What 3.13.2 means in practice

Security is designed in rather than added later: layered defenses, least privilege in the architecture, secure coding practices and security reviews in the development process. Assessors look for the principles you follow and for evidence that they shaped real designs.

SPRS points and the CMMC POA&M

What an assessor checks for 3.13.2

NIST SP 800-171A gives 6 determination statements for 3.13.2, each found satisfied or other than satisfied. Determine if:

1. 3.13.2[a] architectural designs that promote effective information security are identified.
2. 3.13.2[b] software development techniques that promote effective information security are identified.
3. 3.13.2[c] systems engineering principles that promote effective information security are identified.
4. 3.13.2[d] identified architectural designs that promote effective information security are employed.
5. 3.13.2[e] identified software development techniques that promote effective information security are employed.
6. 3.13.2[f] identified systems engineering principles that promote effective information security are employed.

NIST SP 800-171A (June 2018), assessment objectives for 3.13.2

Evidence that shows 3.13.2 is met

• The security architecture or design principles document.
• Secure development practices, such as code review and security testing, with their records.
• Design review records for recent significant changes.

How PolicyCortex gathers the evidence

No PolicyCortex collector reads the evidence for 3.13.2. Your team provides the evidence listed above.