---
title: "NIST 800-171 3.13.2 (SC.L2-3.13.2): Security Engineering"
description: "NIST SP 800-171 3.13.2 Security Engineering: 5 SPRS points, not allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.2
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/system-and-communications-protection/3.13.2
records: 7
digest: sha3:7df983e3ec3ef530dd061f17224fa87b1bc7873c51b9547faffe6b7a54a52156
---

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

NIST 800-171 / System and Communications Protection / 3.13.2

"Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems." ([NIST SP 800-171 Rev. 2, requirement 3.13.2](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice SC.L2-3.13.2.

## 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

- **CMMC Level 2 practice**: SC.L2-3.13.2
- **SPRS points**: 5 points. When it is not met, the DoD Assessment Methodology subtracts 5 from the score of 110.
- **CMMC POA&M**: Not allowed. It is worth 5 points, and 32 CFR 170.21(a)(2)(ii) admits only requirements worth 1 point, with one exception: 3.13.11 when encryption is used but not FIPS validated.

Sources: [NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## 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:

- 3.13.2[a] architectural designs that promote effective information security are identified.
- 3.13.2[b] software development techniques that promote effective information security are identified.
- 3.13.2[c] systems engineering principles that promote effective information security are identified.
- 3.13.2[d] identified architectural designs that promote effective information security are employed.
- 3.13.2[e] identified software development techniques that promote effective information security are employed.
- 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](https://doi.org/10.6028/NIST.SP.800-171A)

## 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.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.13.2 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-SC)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 16 System and Communications Protection requirements (3.13).](https://policycortex.com/nist-800-171/system-and-communications-protection)
- **Previous**: [3.13.1: Boundary Protection](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.1)
- **Next**: [3.13.3: Management Separation](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.3)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | 5b266bdad927 | 27e14727d4a3 |
| REC 0001 | MEANING | 5bf74c672260 | 5b266bdad927 |
| REC 0002 | POINTS AND POA&M | fb3f66f393a7 | 5bf74c672260 |
| REC 0003 | ASSESSMENT OBJECTIVES | 38785198a8b1 | fb3f66f393a7 |
| REC 0004 | EVIDENCE | 92b92da5e4a5 | 38785198a8b1 |
| REC 0005 | COLLECTORS | b78df8d42079 | 92b92da5e4a5 |
| REC 0006 | RELATED | 7df983e3ec3e | b78df8d42079 |

Head sha3:7df983e3ec3ef530dd061f17224fa87b1bc7873c51b9547faffe6b7a54a52156. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.