← AC-2
AC-2(11) AC · Access Control

Usage Conditions

LOW MODERATE ✓ HIGH
1 Overlay 0 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Enforce [circumstances and/or usage conditions] for [system accounts].

Discussion (NIST Supplemental Guidance)

Specifying and enforcing usage conditions helps to enforce the principle of least privilege, increase user accountability, and enable effective account monitoring. Account monitoring includes alerts generated if the account is used in violation of organizational parameters. Organizations can describe specific conditions or circumstances under which system accounts can be used, such as by restricting usage to certain days of the week, time of day, or specific durations of time.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for AC-2(11) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. circumstances and/or usage conditions to be enforced for system accounts are defined;
  2. system accounts subject to enforcement of circumstances and/or usage conditions are defined;
  3. <AC-02(11)_ODP[01] circumstances and/or usage conditions> for <AC-02(11)_ODP[02] system accounts> are enforced.

Examine

[SELECT FROM: Access control policy; procedures addressing account management; system design documentation; system configuration settings and associated documentation; system-generated list of system accounts and associated assignments of usage circumstances and/or usage conditions; system audit records; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with account management responsibilities; system/network administrators; organizational personnel with information security responsibilities; system developers].

Test

[SELECT FROM: Mechanisms implementing account management functions].

Overlays

Showing the OT/ICS overlay for the parent control AC-2 — see the AC-2(11) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (3) (4) (5) (13)
  • Added: (11) (12)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (3) (4) (5) (13)
  • Excluded: (11) (12)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for AC-2(11). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • Access control policy
  • system security plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation

Testing

  • Mechanisms implementing account management functions

Other Records

  • procedures addressing account management
  • system-generated list of system accounts and associated assignments of usage circumstances and/or usage conditions
  • system audit records
  • other relevant documents or records