NIST SP 800-53 Rev. 5·Control AC-2(12)·high·Component: Access Control

What this control requires

Organizations must monitor system accounts for atypical usage, such as access at unusual times or from unexpected locations. Atypical usage could indicate rogue behavior or an ongoing attack. Any identified atypical usage should be reported to designated personnel. Organizations should assess and document privacy risks associated with monitoring and ensure alignment with privacy program plans. This control supports the Governance capability within the Access Control family.
— NIST SP 800-53 Rev. 5, Control AC-2(12)

In plain English

Organizations must monitor system accounts for atypical usage, such as access at unusual times or from unexpected locations. In practice, this means you can prove you policy 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-2(12)) and look for objective evidence on the latest two assessment cycles.

How to implement

Logging Monitoring

AWS. Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation.

Azure. Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR.

GCP. Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM.

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

  • Policy. Document the trigger, the owner and the cadence.
  • Account. Document the trigger, the owner and the cadence.
  • Usage. Document the trigger, the owner and the cadence.
  • Access. Document the trigger, the owner and the cadence.
  • Access Control. Document the trigger, the owner and the cadence.
  • Scope: management, accounts, atypical usage, access at unusual times, access control, privacy, system, personnel.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Account Monitoring For Atypical Usage.

Common pitfalls

  • Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days.
  • 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.

Related controls in NIST SP 800-53 Rev. 5

References

Topics: governance riskcontinuous monitoringlogging monitoringpolicy managementprivacy management