NIST 800-171 3.4.2 (CM.L2-3.4.2): Security Settings
Establish and enforce security configuration settings for information technology products employed in organizational systems.
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; 32 CFR 170.21, Plan of Action and Milestones requirements.
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
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.
Meet the requirement once. Keep the evidence current.
- Published
- Last updated
- Unchanged since publication