NIST SP 800-171 Rev. 3·Requirement 3.1.12·critical·Component: Access Control

What this control requires

This control establishes requirements for remote access to systems, including usage restrictions, configuration, and connection requirements. It mandates authorization prior to remote access and ensures that connections are routed through authorized access control points. Additionally, it restricts the remote execution of privileged commands and access to security-relevant information to minimize vulnerabilities from external networks. This control supports the Remote Access Management System capability within the Access Control (3.1) family.
— NIST SP 800-171 Rev. 3, Requirement 3.1.12

In plain English

This control establishes requirements for remote access to systems, including usage restrictions, configuration, and connection requirements. 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 critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

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.12) 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

  • 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.
  • Configuration. Document the trigger, the owner and the cadence.
  • Scope: management, remote, usage restrictions, configuration, connection requirements, security, access control, authorization.

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.
  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Remote Access.

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.

Related controls in NIST SP 800-171 Rev. 3

References

Topics: identity accessprivileged accessidentity managementaccess reviewconfiguration management