Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
A BIND 9.x server implementation must be running in a chroot(ed) directory structure.
Description
Discussion Text
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.
BIND must be configured to run in a padded cell or chroot(ed) directory structure.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.