Cis Bind9 V301 5 1
DevOps & Securitycis-bind9-v301-5-1Cis Bind9 V301 5 1 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Securely Authenticate Zone Transfers (Scored)
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Server_Software/Bind/CIS_ISC_BIND_DNS_Server_9.9_Benchmark_v3.0.1/cis-bind9-v301-5-1/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-bind9-v301-5-1, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
CIS 5.1 — Securely Authenticate Zone Transfers
Profile Applicability
- Level 1 - Authoritative Name Server
Description
A zone transfer is a mechanism commonly used by DNS deployments to replicate zone information from master/primary servers to slave/secondary servers. Each pair of name servers participating in zone transfers should authenticate the requests and ensure the integrity of the responses by using a unique shared secret TSIG key. BIND can be configured to respond only to authenticated transfer requests by using the allow-transfer statement with a key statement, that restricts the transfers to servers that provide a MAC using the named key.
Rationale
A zone transfer is a popular information disclosure attack as it provides the entire list of resource records for a zone. There should be very few systems such as the slave name servers that should be authorized to perform a zone transfer for your domains. Authentication of transfer requests should not be made using only an IP address, since IP addresses can be spoofed, but rather by using TSIG keys.
Impact
None noted.
Audit Procedure
Perform the following:
- Search all of the included configuration files and zone files for the
allow-transferoption.
grep -C 1 allow-transfer $CONFIG_FILES $ZONE_FILES
-
If there are no
allow-transferstatements found, then the configuration allows zone transfers, and is not compliant. -
If the only value in the address match list of all the
allow-transferstatements is the valuenone, either with or without quotes, then the configuration is compliant. Examples output is shown below.
allow-transfer { none; };
allow-transfer {"none";};
- If all of the address list values of the
allow-transferstatements have the keywordkeyfollowed by a name, then the configuration is compliant.
allow-transfer { key ns1-ns2.cisecurity.org.; key ns2-ns3.cisecurity.org.; };
- If the predefined address value of
anyappears in theallow-transferstatement, then the configuration is not compliant. If any of the address list values contains ACL names, IP addresses or network ranges, then the configuration is also not compliant.
allow-transfer { any; }
allow-transfer { key ns1-ns2.cisecurity.org.; 10.10.42.56; }
- Additionally, it is possible to confirm if a transfer is allowed to an IP address without a key, by performing the following command on the system with the suspected allowed IP address. An error of
Transfer failedis the expected result. If a list of resource records is returned, then the transfer was allowed without a key, and the configuration is non-compliant.
$ dig @ns1.cisecurity.org cisecurity.org axfr
; <<>> DiG 9.9 . . .
; (1 server found)
;; global options: +cmd
; Transfer failed.
Remediation
Generate TSIG keys 256 bits in length, unique for each host-to-host communication. Securely Transfer the keys and configure the keys to be required in all allow-transfer statements.
Default Value
If the allow-transfer statement is missing, then transfers are allowed to any host.
References
None listed.
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v6 | 9.1 - Limit Open Ports, Protocols, and Services | Y | Y | Y |
MITRE ATT&CK Mappings
| Tactic | Technique |
|---|---|
| Reconnaissance | T1590 - Gather Victim Network Information |
| Reconnaissance | T1590.002 - DNS |
Profile
- Level 1 - Authoritative Name Server