Detections
Analytics
BIND-9X-001720 - A BIND 9.x server implementation must be running in a chroot(ed) directory structure.
Information
With any network service, there is the potential that an attacker can exploit a vulnerability within the program that allows the attacker to gain control of the process and even run system commands with that control. One possible defense against this attack is to limit the software to particular quarantined areas of the file system, memory, or both. This effectively restricts the service so that it will not have access to the full file system. If such a defense were in place, even if an attacker gained control of the process, the attacker would be unable to reach other commands or files on the system. This approach often is referred to as a padded cell, jail, or sandbox. All of these terms allude to the fact that the software is contained in an area where it cannot harm itself or others. A more technical term is a chroot(ed) directory structure.BIND must be configured to run in a padded cell or chroot(ed) directory structure.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
Configure the BIND 9.x server to operate in a chroot(ed) directory structure.See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_BIND_9-x_V3R2_STIG.zip
Item Details
Audit Name: DISA BIND 9.x STIG v3r2
Category: SYSTEM AND COMMUNICATIONS PROTECTION
References: 800-53|SC-4, CAT|II, CCI|CCI-001090, Rule-ID|SV-272422r1137672_rule, STIG-ID|BIND-9X-001720, Vuln-ID|V-272422
Plugin: Unix
Control ID: 9ccb08024279a0250b52cf7c9328d43654fb34b213785884ff3fc969c2f52b64