The TSIG keys used with the BIND 9.x implementation must be owned by a privileged account.

Incorrect ownership of a TSIG key file could allow an adversary to modify the file, thus defeating the security objective.

With the assistance of the DNS administrator, identify all of the TSIG keys used by the BIND 9.x implementation.

Identify the account that the "named" process is running as:

# ps -ef | grep named named 3015 1 0 12:59 ? 00:00:00 /usr/sbin/named -u named -t /var/named/chroot

With the assistance of the DNS administrator, determine the location of the TSIG keys used by the BIND 9.x implementation.

# ls -al <TSIG_Key_Location> -rw-r-----. 1 named named 76 May 10 20:35 tsig-example.key

If any of the TSIG keys are not owned by the named account, this is a finding.

Change the ownership of the TSIG keys to the named process it is running as.

# chown <named_proccess_owner> <TSIG_key_file>.