Verify Ownership of /etc/hosts.deny

An XCCDF Rule

Description

To properly set the owner of /etc/hosts.deny, run the command:

$ sudo chown root /etc/hosts.deny

Rationale

The /etc/hosts.deny file is used to control access of clients to daemons in the server. Insecure groupownership of this file could allow users to grant clients unrestricted access or no access at all to services in the server.

ID: xccdf_org.ssgproject.content_rule_file_owner_etc_hosts_deny
Severity: Medium
Updated: about 1 year ago

- name: Test for existence /etc/hosts.deny
  stat:
    path: /etc/hosts.deny
  register: file_exists
  when: ansible_virtualization_type not in ["docker", "lxc", "openvz", "podman", "container"]
  tags:  - configure_strategy
  - file_owner_etc_hosts_deny
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

- name: Ensure owner 0 on /etc/hosts.deny
  file:
    path: /etc/hosts.deny
    owner: '0'
  when:
  - ansible_virtualization_type not in ["docker", "lxc", "openvz", "podman", "container"]
  - file_exists.stat is defined and file_exists.stat.exists
  tags:
  - configure_strategy
  - file_owner_etc_hosts_deny
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed

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

chown 0 /etc/hosts.deny

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

Verify Ownership of /etc/hosts.deny

Description

Rationale

Remediation - Ansible

Remediation - Shell Script