# Ensure No Duplicate Group Names Exist on the System

- Source: https://support.icompaas.com/support/solutions/articles/62000235392-ensure-no-duplicate-group-names-exist-on-the-system
- 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:  
 Duplicate group names can cause inconsistencies and unexpected behavior in user permissions and access control. Ensuring unique group names maintains the integrity of group-based security policies.

Rationale:  
 Preventing duplicate group names avoids confusion in group membership management and reduces the risk of privilege escalation or access control misconfigurations.

Impact:  
 Pros:

-   Ensures consistent and predictable group permissions.
    
-   Simplifies user and group management.
    

Cons:

-   Removal or renaming of duplicate groups may affect existing user permissions if not carefully managed.
    

Default Value:  
 Duplicate group names may exist due to manual misconfiguration or system inconsistencies.

Pre-requisites:

-   Root or sudo privileges to review and modify group configurations.  
      
    

Remediation:

### Test Plan:

Using Linux command line:

1.  List all group names and identify duplicates:
    
    cut -d: -f1 /etc/group | sort | uniq -d
    
2.  Verify that the output is empty, indicating no duplicates.  
      
    

### Implementation Plan:

Using Linux command line:

1.  For each duplicate group name found, rename or remove duplicates carefully:
    
    groupmod -n <new\_group\_name> <old\_group\_name>  
    groupdel <duplicate\_group\_name>
    
      
    
2.  Ensure user memberships are preserved or reassigned as necessary.  
      
    

Backout Plan:

Using Linux command line:

1.  Restore original group names from backups if needed.
    
2.  Reassign users to groups if any memberships were lost.  
      
    

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.
