3.1.6
AC.L2-3.1.6 · Level 2
Use non-privileged accounts or roles when accessing nonsecurity functions.
NIST SP 800-171 Rev 2 · §3.1.6
Use non-privileged accounts or roles when accessing nonsecurity functions.
Assessment objectives
From NIST SP 800-171A · 2 objectives must be met to satisfy this control
Examine
[SELECT FROM: Access control policy; procedures addressing least privilege; security plan; list of system-generated security functions assigned to system accounts or roles; system configuration settings and associated documentation; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: Personnel with responsibilities for defining least privileges necessary to accomplish specified organizational tasks; personnel with information security responsibilities; system or network administrators].
Test
[SELECT FROM: Mechanisms implementing least privilege functions].
Examine
[SELECT FROM: Access control policy; procedures addressing least privilege; security plan; list of system-generated security functions assigned to system accounts or roles; system configuration settings and associated documentation; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: Personnel with responsibilities for defining least privileges necessary to accomplish specified organizational tasks; personnel with information security responsibilities; system or network administrators].
Test
[SELECT FROM: Mechanisms implementing least privilege functions].
What we look for in practice
The following are placeholder notes that should be refined based on practice experience.
What assessors look for in practice. Documented evidence that this control is implemented across all CUI-handling systems within scope. Specific artifacts vary, but expect requests for written procedures, system configurations, and operational records demonstrating the control is active.
Common failure patterns. Typical issues include incomplete documentation, inconsistent implementation across systems, and missing periodic review records. Refine this section as your practice accumulates direct assessment experience.
Strong evidence looks like. Formal policy referencing this control, technical configurations demonstrating enforcement, periodic review logs with sign-off, and procedures for handling exceptions.
Scoring and POA&M context. 1-point control under the DoD Assessment Methodology. Lower scoring impact, but still required for full compliance. POA&M-eligible — deferral up to 180 days is allowed under conditional certification per 32 CFR 170.21.