Verify Group Who Owns /etc/cron.allow file
Description
If /etc/cron.allow exists, it must be group-owned by root.
To properly set the group owner of /etc/cron.allow, run the command:
$ sudo chgrp root /etc/cron.allow
Rationale
If the owner of the cron.allow file is not set to root, the possibility exists for an
unauthorized user to view or edit sensitive information.
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
chgrp 0 /etc/cron.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/cron.allow
stat:
path: /etc/cron.allow
register: file\_exists
when: ansible\_virtualization\_type not in ["docker", "lxc", "openvz", "podman", "container"]
tags:
- NIST-800-53-AC-6(1)
- NIST-800-53-CM-6(a)
- PCI-DSSv4-2.2.6
- configure\_strategy
- file\_groupowner\_cron\_allow
- low\_complexity
- low\_disruption
- medium\_severity
- no\_reboot\_needed
- name: Ensure group owner 0 on /etc/cron.allow
file:
path: /etc/cron.allow
group: '0'
when:
- ansible\_virtualization\_type not in ["docker", "lxc", "openvz", "podman", "container"]
- file\_exists.stat is defined and file\_exists.stat.exists
tags:
- NIST-800-53-AC-6(1)
- NIST-800-53-CM-6(a)
- PCI-DSSv4-2.2.6
- configure\_strategy
- file\_groupowner\_cron\_allow
- low\_complexity
- low\_disruption
- medium\_severity
- no\_reboot\_needed
