# Ensure At Is Restricted to Authorized Users

- Source: https://support.icompaas.com/support/solutions/articles/62000235405-ensure-at-is-restricted-to-authorized-users
- 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:**  
 The at command schedules one-time tasks to run at a specified time. Restricting access to the at command ensures only authorized users can schedule such jobs, preventing unauthorized or malicious tasks that could compromise system security.

**Rationale:** Unrestricted use of at can lead to unauthorized task execution, privilege escalation, or system disruption. Limiting at usage to authorized users helps maintain system integrity and control over scheduled tasks.

**Impact:** Pros:

-   Prevents unauthorized scheduling of one-time tasks.  
    
-   Helps maintain system stability and security.  
    
-   Supports compliance with security policies and standards.  
    

Cons:

-   Restricting access may limit legitimate user flexibility for scheduling tasks.  
    

**Default Value:** By default, access to the at command may be unrestricted or controlled via /etc/at.allow and /etc/at.deny files.

**Pre-requisites:** Root or sudo privileges to configure at access controls.

**Remediation:**

**Test Plan:  
 Using Linux command line:**

1.  Check for the presence of /etc/at.allow and /etc/at.deny files:
    

ls -l /etc/at.allow /etc/at.deny

2.  Verify which users are permitted or denied access based on these files.  
    

**Implementation Plan:  
 Using Linux command line:**

1.  To restrict at access, create or edit /etc/at.allow and list authorized users (one username per line). For example:
    

echo "root" > /etc/at.allow
echo "adminuser" >> /etc/at.allow

2.  Remove or restrict /etc/at.deny if it conflicts with /etc/at.allow.  
    
3.  Set correct ownership and permissions on these files:  
    

chown root:root /etc/at.allow /etc/at.deny
chmod 600 /etc/at.allow /etc/at.deny

4.  Verify changes:  
    

cat /etc/at.allow
cat /etc/at.deny

**Backout Plan:  
 Using Linux command line:**

1.  If needed, remove /etc/at.allow to revert to default behavior.
    
2.  Restore previous content of /etc/at.deny if applicable.
    
3.  Set previous ownership and permissions on these files.  
    

**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0 — https://www.cisecurity.org/benchmark/amazon\_linux/  
    
-   Linux at Manual — https://man7.org/linux/man-pages/man1/at.1.html  
    
-   NIST SP 800-53 Revision 5 - CM-5 Configuration Management — [https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final)

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