# NIST SP 800-171 Rev. 3 3.1.2 — Access Enforcement - Source: https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-2-access-enforcement - 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) › Access Control — §3.1 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-171 Rev. 3**·Requirement `3.1.2`·high·Component: **Access Control** ## What this control requires > This control ensures that approved authorizations are enforced for logical access to Controlled Unclassified Information (CUI) and system resources, as per access control policies. It applies to both user and system process access, including remote and external network access, and can extend to applications and services to enhance the protection of CUI. This control supports the Access Enforcement Mechanism capability within the Access Control (3.1) family. > > — NIST SP 800-171 Rev. 3, Requirement 3.1.2 ### In plain English This control ensures that approved authorizations are enforced for logical access to Controlled Unclassified Information (CUI) and system resources, as per access control policies. In practice, this means you can prove you access 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 **Access Control**, the assessor will trace your implementation back to the catalogue reference (Requirement 3.1.2) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Network Security **AWS.** VPC Flow Logs to S3, default-deny security groups, AWS Network Firewall for north-south, and Transit Gateway for hub-and-spoke segmentation. **Azure.** NSGs with deny-by-default, Azure Firewall Premium with TLS inspection, Private Endpoints for PaaS, and Microsoft Defender for Cloud's secure score for drift. **GCP.** VPC Service Controls perimeters around sensitive APIs, Cloud NGFW Enterprise for L7 inspection, Private Service Connect for managed services. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Access.** Document the trigger, the owner and the cadence. - **Information.** Document the trigger, the owner and the cadence. - **Remote.** Document the trigger, the owner and the cadence. - **Access Control.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Scope:** management, enforcement, remote, external network access, cui, applications, security, access control. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: Access Enforcement. ## Common pitfalls - Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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 AC-20** — Use Of External Systems](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-20-use-of-external-systems) - [**HIPAA (45 CFR Part 164) 164.310(a)(2)(iii)** — Facility Access Controls - Access Control and Validation Procedures](https://support.icompaas.com/compliance/hipaa/164-310-a-2-iii-facility-access-controls-access-control-and-validation-procedures) - [**BSI C5:2020 COS-08** — Policies for data transmission](https://support.icompaas.com/compliance/bsi-c5-2020/cos-08-policies-for-data-transmission) ## Related controls in NIST SP 800-171 Rev. 3 - [**Requirement 3.1.20** — Use of External Systems](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-20-use-of-external-systems) - [**Requirement 3.1.5** — Least Privilege](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-5-least-privilege) - [**Requirement 3.10.7** — Physical Access Control](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-10-7-physical-access-control) - [**Requirement 3.1.9** — System Use Notification](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-9-system-use-notification) - [**Requirement 3.1.10** — Device Lock](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-10-device-lock) - [**Requirement 3.1.11** — Session Termination](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-11-session-termination) ## 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.1.2` Topics: governance riskidentity accessnetwork securitypolicy 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.