# Ensure Root is the Only Account with UID 0

- Source: https://support.icompaas.com/support/solutions/articles/62000235390-ensure-root-is-the-only-account-with-uid-0
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS Amazon Linux 2 Benchmark v3.0.0](https://support.icompaas.com/support/solutions/62000112696) › [CIS Amazon Linux 2 Benchmarks](https://support.icompaas.com/support/solutions/folders/62000169265)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Profile Applicability:  
Level 1

Description:  
 In Unix and Linux systems, the user with User ID (UID) 0 has unrestricted administrative privileges. Having multiple accounts with UID 0 increases the risk of unauthorized access and privilege escalation.

Rationale:  
 Ensuring that only the root account has UID 0 limits administrative access to a single trusted account, reducing the attack surface and enhancing system security.

**Impact:  
** **Pros:**

-   Limits privileged access to a single account.  
    
-   Simplifies auditing and accountability of administrative actions.  
    

**Cons:**

-   Removing additional UID 0 accounts may disrupt legitimate administrative workflows if not properly managed.  
    

Default Value:  
Multiple UID 0 accounts may exist if created by administrators or system misconfiguration.

Pre-requisites:

-   Root or sudo privileges to review and modify user accounts.  
    

Remediation:

### Test Plan:

Using Linux command line:

1\. List all accounts with UID 0:

 awk -F: '($3 == 0) {print $1}' /etc/passwd

2\. Verify that only root is listed.

  

Implementation Plan:

Using Linux command line:

1\. For each non-root account with UID 0, change the UID to a non-privileged value or disable the account:

usermod -u <new\_uid> <username>
passwd -l <username>  # To lock the account if needed

2\. Verify changes:  

awk -F: '($3 == 0) {print $1}' /etc/passwd

Backout Plan:

Using Linux command line:

1.  Restore previous UID values and unlock accounts if needed.  
    
2.  Communicate changes to affected users or administrators.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   [NIST SP 800-53 Revision 5 - AC-6  
      
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#ac-6)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
