NIST SP 800-53 Rev. 5 AC-6(3) — Network Access To Privileged Commands

What this control requires

Authorize network access to privileged commands only for compelling operational needs, documenting the rationale in the system's security plan to limit risks from remote access. This control supports the Network Access Control System capability within the Access Control family.

In plain English

Authorize network access to privileged commands only for compelling operational needs, documenting the rationale in the system's security plan to limit risks from remote access. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

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 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Access Control, the assessor will trace your implementation back to the catalogue reference (Control AC-6(3)) 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.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Authorize. Document the trigger, the owner and the cadence.
• Network. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Scope: management, access control, system, only, identity, review, capability, 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: Network Access To Privileged Commands.

Common pitfalls

• Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth.

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-171 Rev. 3 3.1.6 — Least Privilege - Privileged Accounts
• CIS Controls v8 6.8 — Define and Maintain Role-Based Access Control
• ISO/IEC 27001:2022 A.8.2 — Privileged access rights
• BSI C5:2020 IDM-01 — Policy for user accounts and access rights
• SOC 2 (2017 TSC) CC6.2 — Access Provisioning

Related controls in NIST SP 800-53 Rev. 5

• Control AC-6(6) — Privileged Access By Non-Organizational Users
• Control AC-6(2) — Non-Privileged Access For Nonsecurity Functions
• Control AC-14 — Permitted Actions Without Identification Or Authentication
• Control AC-16(10) — Attribute Configuration By Authorized Individuals
• Control AC-10 — Concurrent Session Control
• Control AC-5 — Separation Of Duties

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control AC-6(3)

Topics: governance riskidentity accessprivileged accessidentity managementaccess reviewnetwork security