Include Cryptographic Key Files

Cara pemeriksaan

Metode audit: Perintah shell

bad=''
for f in /etc/named.conf /etc/bind/named.conf /var/named/chroot/etc/named.conf; do [ -f "$f" ] || continue; grep -Eq '^[^#/]*secret[[:space:]]+"' "$f" && bad="$bad $f"; done
[ -z "$bad" ] && echo compliant || echo "secret keys embedded in:$bad"

Output yang diharapkan

compliant

Cara perbaikan

Metode perbaikan: Panduan atau patch infrastruktur

Move each key definition statement from the named.conf file into its own key file. It is recommended to name both the key and the key file after the two hosts that will be sharing the secret key, in order to avoid confusion. Then include the key files with include statements in the named.conf. An example is shown below with the key definition statement moved to a separate key file, however it is also accepted for only the secret statement to be moved to another file. # grep -C 1 include /etc/named.conf // Include the key file used for the host1 and host2 TSIG comms include "/etc/private/host1-host2.cisecurity.org.key"

Periksa host ini

Jalankan ini pada mesin yang diizinkan untuk Anda audit. Pemindaian bersifat hanya baca.

tmaegis scan --target bind