# NIST SP 800-171 Rev. 3 3.4.2 — Configuration Settings - Source: https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-4-2-configuration-settings - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-171 Rev. 3 Requirements](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3) › Configuration Management — §3.4 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-171 Rev. 3**·Requirement `3.4.2`·high·Component: **Configuration Management** ## What this control requires > This control requires the establishment, documentation, and implementation of configuration settings that reflect the most restrictive mode consistent with operational requirements. It also mandates the identification, documentation, and approval of any deviations from established configuration settings. These settings encompass security parameters such as account, file, directory permissions, and configurations for network components, operating systems, and applications. This control supports the Configuration Management System capability within the Configuration Management (3.4) family. > > — NIST SP 800-171 Rev. 3, Requirement 3.4.2 ### In plain English This control requires the establishment, documentation, and implementation of configuration settings that reflect the most restrictive mode consistent with operational requirements. In practice, this means you can prove you account management-level controls on a defined cadence. ## Why it matters DoD contractors and their subcontractors must implement all 100 SP 800-171 requirements to keep CUI handling contracts. Gaps are scored against the SPRS scoring methodology; below a 110-point starting score, each unmet requirement deducts points and a below-threshold score can disqualify a bid. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A C3PAO conducting a CMMC Level 2 assessment uses NIST SP 800-171A objectives. They expect a System Security Plan (SSP), Plan of Action & Milestones (POA&M) for any gaps, and objective evidence (configurations, ticket records, training records) for every requirement. Within **Configuration Management**, the assessor will trace your implementation back to the catalogue reference (Requirement 3.4.2) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Configuration Management **Policy-as-code.** Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises. **IaC.** Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production. **Drift.** Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register. ### Operational checklist - **Account.** Document the trigger, the owner and the cadence. - **Access.** Document the trigger, the owner and the cadence. - **Configuration.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Risk.** Document the trigger, the owner and the cadence. - **Scope:** management, configuration, settings, account, file, directory permissions, applications, security. ## Evidence to collect - **Identity Scan.** IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Configuration Settings. ## Common pitfalls - Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-53 Rev. 5 CM-3(6)** — Cryptography Management](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-3-6-cryptography-management) - [**ISO/IEC 27001:2022 A.5.16** — Identity management](https://support.icompaas.com/compliance/iso-27001-2022/a-5-16-identity-management) - [**CIS Controls v8 5.6** — Centralize Account Management](https://support.icompaas.com/compliance/cis-controls-v8/5-6-centralize-account-management) - [**SOC 2 (2017 TSC) CC1.5** — Accountability for Internal Control Responsibilities](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc1-5-accountability-for-internal-control-responsibilities) - [**BSI C5:2020 IDM-02** — Granting and change of user accounts and access rights](https://support.icompaas.com/compliance/bsi-c5-2020/idm-02-granting-and-change-of-user-accounts-and-access-rights) ## Related controls in NIST SP 800-171 Rev. 3 - [**Requirement 3.4.10** — System Component Inventory](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-4-10-system-component-inventory) - [**Requirement 3.3.1** — Event Logging](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-1-event-logging) - [**Requirement 3.8.5** — Media Transport](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-8-5-media-transport) - [**Requirement 3.9.1** — Personnel Screening](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-9-1-personnel-screening) - [**Requirement 3.1.12** — Remote Access](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-12-remote-access) - [**Requirement 3.1.6** — Least Privilege - Privileged Accounts](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-6-least-privilege-privileged-accounts) ## References - [NIST Computer Security Resource Center — NIST SP 800-171 Rev. 3](https://csrc.nist.gov/pubs/sp/800/171/r3/final) - Catalogue identifier: `Requirement 3.4.2` Topics: governance riskidentity accessidentity managementaccess reviewprivileged accessconfiguration management ## Related compliance guidance - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): Start with the full NIST SP 800-171 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): The catalogue 800-171 is tailored from, and the basis of the FedRAMP Moderate baseline your cloud providers must meet for CUI. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): If commercial customers ask for a certificate as well, most 800-171 controls can be evidenced once and mapped to Annex A.