Cis Bind9 V301 2 6

CIS 2.6 — Set Group named or root for BIND Directories and Files

Profile Applicability

• Level 1 - Authoritative Name Server
• Level 1 - Caching Only Name Server

Description

All the BIND directories and files should have a group of either named or root.

Rationale

In general, the BIND directories and files default to a group of named, however some system files may have a group of root. Examples of system files include chroot'ed system device files. Either group root or named is accepted, as the intent is to prevent unexpected group ids, from getting inappropriate access to BIND files. Run time directories to which BIND will need write access should have a group of named, so that write access may be granted via the group permissions.

Impact

Not Applicable

Audit Procedure

Ensure that the BIND benchmark variables used below are set as described in the benchmark overview. Run the command below to ensure that all BIND directories and files have a group of either named or root.

# find $BIND_HOME $RUNDIR \! \( -group root -o -group named \) -ls

There should be no files listed in the output from the find command.

Remediation

Run the command below to change all BIND directories and files to the group named.

chgrp -R named $BIND_HOME $RUNDIR

Default Value

The default rpm install has all directories and files in the BIND home and the run time directory with a group of named.

References

Not Applicable

CIS Controls

MITRE ATT&CK Mappings

Profile

• Level 1 - Authoritative Name Server
• Level 1 - Caching Only Name Server