How do I install the Cis Bind V100 2 4 skill?

Run npx skillmds@latest add cyberstrikeus/cis-bind-v100-2-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cis Bind V100 2 4 skill do?

Set root Ownership of BIND Directories (Automated) It is listed under Coding & Dev Tools on SkillMD.

Is Cis Bind V100 2 4 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cis Bind V100 2 4?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cis Bind V100 2 4 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cis Bind V100 2 4?

cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cis Bind V100 2 4 by cyberstrikeus — Agent Skill

Name: Cis Bind V100 2 4
Author: cyberstrikeus

File contents

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

---name: cis-bind-v100-2-4description: Set root Ownership of BIND Directories (Automated)---# CIS 2.4 — Set root Ownership of BIND Directories## Profile Applicability- Authoritative Name Server Level 1- Caching Only Name Server Level 1## DescriptionAll 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.## RationaleRestricting 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.## ImpactNot specified.## Audit ProcedureEnsure 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:```bash# find $BIND_HOME $RUNDIR -type d \! -user root -ls```There should be NO directories listed in the output from the find command.## RemediationTo correct the directory ownership, perform the following:```bashfind $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 ValueThe following directories are owned by `named` in the default package install:- /var/named/dynamic- /var/named/slaves- /var/named/data- /run/named## ReferencesNone 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

Frequently asked questions

Cis Bind V100 2 4