NIST SP 800-53 Rev. 5 AC-12 — Session Termination

What this control requires

Automatically terminate user sessions after organization-defined conditions or trigger events, such as inactivity periods, specific incidents, or time-of-day restrictions. This control supports the Session Management System capability within the Access Control family.

In plain English

Automatically terminate user sessions after organization-defined conditions or trigger events, such as inactivity periods, specific incidents, or time-of-day restrictions. In practice, this means you can prove you inactivity 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.

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-12) and look for objective evidence on the latest two assessment cycles.

How to implement

Incident Response

Runbook. Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification.

Tabletop. Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook.

Operational checklist

• Inactivity. Document the trigger, the owner and the cadence.
• Restrictions. Document the trigger, the owner and the cadence.
• Access. Document the trigger, the owner and the cadence.
• Session. Document the trigger, the owner and the cadence.
• Termination. Document the trigger, the owner and the cadence.
• Scope: management, conditions, access control, organization, system, termination, inactivity periods, incidents.

Evidence to collect

• Ticketing Workflow. ticketing_workflow evidence

Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Session Termination.

Common pitfalls

• Runbooks that name a role but no person, or list a paging channel that no longer exists.

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.11 — Session Termination
• SOC 2 (2017 TSC) CC7.4 — Incident Response

Related controls in NIST SP 800-53 Rev. 5

• Control IR-4(11) — Integrated Incident Response Team
• Control IR-4(15) — Public Relations And Reputation Repair
• Control IR-6(2) — Vulnerabilities Related To Incidents
• Control AU-2 — Event Logging
• Control AC-12(3) — Timeout Warning Message
• Control AT-2(1) — Practical Exercises

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control AC-12

Topics: incident responsechange management