# Ensure Users Must Provide Password for Privilege Escalation

- Source: https://support.icompaas.com/support/solutions/articles/62000235542-ensure-users-must-provide-password-for-privilege-escalation
- 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:  
 Requiring users to enter their password when using privilege escalation tools such as sudo ensures accountability and prevents unauthorized or accidental use of elevated privileges.

Rationale:  
 Enforcing password prompts for privilege escalation helps maintain security by verifying user identity before granting higher-level access.

Impact:  
 Pros:

-   Enhances security by requiring authentication for privilege escalation.  
      
    
-   Supports auditability and accountability.  
      
    

Cons:

-   May cause minor inconvenience for users needing frequent escalations.  
      
    

Default Value:  
 By default, sudo prompts for a password unless configured otherwise.

Pre-requisites:

-   Root or sudo privileges to modify sudoers configuration.  
      
    

Remediation:

### Test Plan:

Using Linux command line:

Check sudoers configuration for NOPASSWD usage:

sudo grep -E 'NOPASSWD' /etc/sudoers /etc/sudoers.d/\*

  

1.  Verify that users or groups do not have the NOPASSWD tag allowing passwordless escalation.
    

### Implementation Plan:

Using Linux command line:

Edit sudoers configuration safely using visudo:  
  
visudo

Remove or comment out any NOPASSWD entries to ensure password is required for escalation. For example, change:

user ALL=(ALL) NOPASSWD: ALL
user ALL=(ALL) ALL

1.  Save and exit.  
      
    

### Backout Plan:

Using Linux command line:

1.  Re-add NOPASSWD entries if necessary.
    
2.  Test sudo functionality and user experience.  
      
    

References:

-   [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.
