CMMC AC.2.007 - Employ Least Privilege

CMMC AC.2.007 - Employ Least Privilege

Requirement textAC.2.007: Employ the principle of least privilege, including for specific security
functions and privileged accounts.

DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2
Organizations employ the principle of least privilege for specific duties and authorized
accesses for users and processes. The principle of least privilege is applied with the goal of
authorized privileges no higher than necessary to accomplish required organizational
missions or business functions. Organizations consider the creation of additional processes,
roles, and system accounts as necessary, to achieve least privilege. Organizations also apply
least privilege to the development, implementation, and operation of organizational systems.
Security functions include establishing system accounts, setting events to be logged, setting
intrusion detection parameters, and configuring access authorizations (i.e., permissions,
privileges).

Privileged accounts, including super user accounts, are typically described as system
administrator for various types of commercial off-the-shelf operating systems. Restricting
privileged accounts to specific personnel or roles prevents day-to-day users from having
access to privileged information or functions. Organizations may differentiate in the
application of this requirement between allowed privileges for local accounts and for domain
accounts provided organizations retain the ability to control system configurations for key
security parameters and as otherwise necessary to sufficiently mitigate risk.

CMMC CLARIFICATION
You should apply the principle of least privilege to all users and processes on all systems.
This means you assign the fewest permissions necessary for the user or process to
accomplish their business function. Also, you:
      • restrict user access to only the machines and information needed to fulfill job
      responsibilities; and
      • limit what system configuration settings users can change, only allowing individuals
      with a business need to change them.

Example
As the IT administrator for your organization, you create accounts. You apply the fewest
privileges necessary for the user or process to complete their task. This means you assign
everyone a basic user role. This prevents a user from modifying system configurations. You
also assign privileged access only to users and processes that need it, such as IT staff.

REFERENCES
​• NIST SP 800-171 Rev 1 3.1.5
• CIS Controls v7.1 14.6
• NIST CSF v1.1 PR.AC-4
• CERT RMM v1.2 KIM:SG4.SP1
• NIST SP 800-53 Rev 4 AC-6, AC-6(1), AC-6(5)
• UK NCSC Cyber Essentials




    • Related Articles

    • CMMC CM.2.062 - Employ Least Functionality

      Requirement text: CM.2.062: Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2 Systems can provide a wide variety of functions and ...
    • Access Control: SP 800-171 Security Family 3.1

      Access is the ability to make use of any system resource. Access control is the process of granting or denying requests to:       • use information,       • use information processing services, and       • enter company facilities.  System-based ...
    • CMMC AC.3.018 - Limit Privilege Functions

      Requirement text: AC.3.018: Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.  DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2 Privileged functions include establishing system ...
    • CMMC AC.2.008 - Use Non-Privilege Accounts

      Requirement text: AC.2.008: Use non-privileged accounts or roles when accessing non-security functions. DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2  This requirement limits exposure when operating from within privileged accounts or roles. The ...
    • CMMC AC.4.025 - Review CUI Access

      Requirement text: AC.4.025: Periodically review and update CUI program access permissions. DISCUSSION FROM SOURCE: CMMC Organizations must maintain the authorizations for access to CUI information on a regular basis, considering whether existing ...