Title

The permissions assigned to the core BIND 9.x server files must be set to use the least privilege possible. (Cat II impact)

Discussion

Discretionary Access Control (DAC) is based on the premise that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired because of creating the object or via specified ownership assignment. In a DNS implementation, DAC should be granted to a minimal number of individuals and objects because DNS does not interact directly with users and users do not store and share data with the DNS application directly.

Check Content

With the assistance of the DNS administrator, identify the following files: named.conf : rw-r----- root hints : rw-r----- Primary zone file(s): rw-r----- Secondary zone file(s): rw-rw---- Note: The name of the root hints file is defined in named.conf. Common names for the file are root.hints, named.cache, or db.cache. Verify that the permissions for the core BIND 9.x server files are at least as restrictive as listed above. If the identified files are not as least as restrictive as listed above, this is a finding.

Fix Text

Configure the permissions of each file to the following: named.conf : rw-r----- root hints : rw-r----- Primary zone file(s): rw-r----- Secondary zone file(s): rw-rw----

Additional Identifiers

Rule ID: SV-272415r1068084_rule

Vulnerability ID: V-272415

Group Title: SRG-APP-000516-DNS-000099

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.