Cis Bind V100 2 4
DevOps & Securitycis-bind-v100-2-4Cis Bind V100 2 4 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.
Set root Ownership of BIND Directories (Automated)
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.11_Benchmark_v1.0.0/cis-bind-v100-2-4/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-bind-v100-2-4, 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 2.4 — Set root Ownership of BIND Directories
Profile Applicability
- Authoritative Name Server Level 1
- Caching Only Name Server Level 1
Description
All of the directories under which ISC BIND runs should be owned by root. Of course, any files created at run time by BIND will still be owned by named, and the run time files will need to be in a directory writable by the named group.
Rationale
Restricting ownership of the directories provides defense in depth and will reduce the probability of unauthorized modifications to those resources. If there was a BIND vulnerability that allowed code execution as the named user, then the code would not be able to modify permissions on the BIND directories owned by root.
Impact
Not specified.
Audit Procedure
Ensure that the variable $BIND_HOME is set to the directory under which BIND runs, typically the directory /var/named/. In the case of a chroot'ed configuration, the daemon will likely run under /var/named/chroot/, however the upper level directory of /var/named/ should still be used as it is specific to the BIND service, and will include the chroot directory. Also, the variable $RUNDIR should be set to the directory which is used to create run-time files such as the pid file and session-key. Perform the following to ensure the directory ownership:
# find $BIND_HOME $RUNDIR -type d \! -user root -ls
There should be NO directories listed in the output from the find command.
Remediation
To correct the directory ownership, perform the following:
find $BIND_HOME $RUNDIR -type d \! -user root | xargs chown root
Note: it is important to remember that the run time files will need to be in a directory writable by the named group. Changing the directory ownership to root might cause permissions issues, if the group permissions are not writable.
Default Value
The following directories are owned by named in the default package install:
- /var/named/dynamic
- /var/named/slaves
- /var/named/data
- /run/named
References
None listed.
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v6 | 14.4 Protect Information With Access Control Lists | N | Y | Y |
| v7 | 14.6 Protect Information through Access Control Lists | Y | Y | Y |
MITRE ATT&CK Mappings
| Tactic | Technique |
|---|---|
| Privilege Escalation | T1574 Hijack Execution Flow |
| Defense Evasion | T1222 File and Directory Permissions Modification |
Profile
- Level 1 - Authoritative Name Server
- Level 1 - Caching Only Name Server