Verify Permissions on /etc/at.allow file

Classification:

compliance

Framework:

Control:

Description

If /etc/at.allow exists, it must have permissions 0640 or more restrictive.

To properly set the permissions of /etc/at.allow, run the command:

$ sudo chmod 0640 /etc/at.allow

Rationale

If the permissions of the at.allow file are not set to 0640 or more restrictive, the possibility exists for an unauthorized user to view or edit sensitive information.

Remediation

Shell script

The following script can be run on the host to remediate the issue.

# Remediation is applicable only in certain platforms
if [ ! -f /.dockerenv ] && [ ! -f /run/.containerenv ]; then

chmod u-xs,g-xws,o-xwrt /etc/at.allow

else
 >&2 echo 'Remediation is not applicable, nothing was done'
fi

Ansible playbook

The following playbook can be run with Ansible to remediate the issue.

- name: Test for existence /etc/at.allow
 stat:
 path: /etc/at.allow
 register: file\_exists
 when: ansible\_virtualization\_type not in ["docker", "lxc", "openvz", "podman", "container"]
 tags:
 - PCI-DSSv4-2.2.6
 - configure\_strategy
 - file\_permissions\_at\_allow
 - low\_complexity
 - low\_disruption
 - medium\_severity
 - no\_reboot\_needed

- name: Ensure permission u-xs,g-xws,o-xwrt on /etc/at.allow
 file:
 path: /etc/at.allow
 mode: u-xs,g-xws,o-xwrt
 when:
 - ansible\_virtualization\_type not in ["docker", "lxc", "openvz", "podman", "container"]
 - file\_exists.stat is defined and file\_exists.stat.exists
 tags:
 - PCI-DSSv4-2.2.6
 - configure\_strategy
 - file\_permissions\_at\_allow
 - low\_complexity
 - low\_disruption
 - medium\_severity
 - no\_reboot\_needed