---
title: "NIST 800-171 3.4.2 (CM.L2-3.4.2): Security Settings"
description: "NIST SP 800-171 3.4.2 Security Settings: 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/configuration-management/3.4.2
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/configuration-management/3.4.2
records: 7
digest: sha3:739b4d347655b5aea4fe634e7ddad8c7bb3477c34043bce6380a0dc8d61e8100
---

# NIST 800-171 3.4.2 (CM.L2-3.4.2): Security Settings

NIST 800-171 / Configuration Management / 3.4.2

"Establish and enforce security configuration settings for information technology products employed in organizational systems." ([NIST SP 800-171 Rev. 2, requirement 3.4.2](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice CM.L2-3.4.2.

## What 3.4.2 means in practice

Each product in the system, from servers to firewalls to cloud services, runs with defined security settings, usually based on a published benchmark such as a CIS Benchmark or a DISA STIG. The settings are part of the baseline and are enforced, not just written down.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: CM.L2-3.4.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.4.2

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

- 3.4.2[a] security configuration settings for information technology products employed in the system are established and included in the baseline configuration.
- 3.4.2[b] security configuration settings for information technology products employed in the system are enforced.

[NIST SP 800-171A (June 2018), assessment objectives for 3.4.2](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.4.2 is met

- The security configuration standard chosen for each product, with any approved deviations.
- Enforcement through Group Policy, device management or cloud policy.
- Scan results showing systems conform to the settings.

## How PolicyCortex gathers the evidence

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

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.4.2 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-CM)
- **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 9 Configuration Management requirements (3.4).](https://policycortex.com/nist-800-171/configuration-management)
- **Previous**: [3.4.1: Baseline and Inventory](https://policycortex.com/nist-800-171/configuration-management/3.4.1)
- **Next**: [3.4.3: Change Control](https://policycortex.com/nist-800-171/configuration-management/3.4.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 | f309023d08a7 | 4dd45ac05266 |
| REC 0001 | MEANING | 187ca568b4ae | f309023d08a7 |
| REC 0002 | POINTS AND POA&M | 0ef430c50ec8 | 187ca568b4ae |
| REC 0003 | ASSESSMENT OBJECTIVES | 464a1d4c5c26 | 0ef430c50ec8 |
| REC 0004 | EVIDENCE | a4e9c3db99d5 | 464a1d4c5c26 |
| REC 0005 | COLLECTORS | 840460efe84c | a4e9c3db99d5 |
| REC 0006 | RELATED | 739b4d347655 | 840460efe84c |

Head sha3:739b4d347655b5aea4fe634e7ddad8c7bb3477c34043bce6380a0dc8d61e8100. 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.