Cis Bind9 V301 8 3

DevOps & Security

cis-bind9-v301-8-3

Cis Bind9 V301 8 3 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.

Configure a Logging Syslog Channel (Scored)

View on GitHub ↗

QUICK START

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.

Prompt to paste

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-8-3/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-bind9-v301-8-3, 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 8.3 — Configure a Logging Syslog Channel

Profile Applicability

Level 1 - Authoritative Name Server
Level 1 - Caching Only Name Server

Description

The syslog option of the logging configuration allows specification of the syslog facility to send log events. A syslog channel should be configured with the value of daemon or other appropriate syslog facility. The default and general categories should be included and the severity level should be info or lower.

Rationale

Configuring a syslog channel allows BIND to log important information via the standard system syslog facility. It is important that the BIND logs be included with the system monitoring and response that is performed on other system logs, and the syslog facility is helpful to ensure that the important log information isn't lost, or ignored.

Impact

None noted.

Audit Procedure

Search the configuration file for a syslog logging channel, as shown below.

# grep -C 3 channel /etc/named.conf | egrep '^\s+syslog\s+'
            syslog daemon;        # send to syslog's daemon facility

Usage of the syslog facility daemon is common practice, but other facilities may be configured.

Remediation

Configure a syslog channel to capture at least the default and general categories of log events. For external authoritative name servers, the category lame-servers may be redirect to null, so that it is not logged. Using lame name servers is common for the domains used for SPAM and may overload the log with information that is not very useful.

logging {
. . .
      // Syslog
      channel default_syslog {
              syslog daemon;        # send to syslog's daemon facility
              severity info;        # only send priority info and higher
      };

      category default { default_syslog; };
      category general { default_syslog; };
      // Too many lame servers, especially from SPAM
      category lame-servers { null; };

Default Value

There is no syslog channel by default.

References

None listed.

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v6	6.6 - Deploy A SIEM OR Log Analysis Tools for Aggregation and Correlation/Analysis	N	Y	Y

MITRE ATT&CK Mappings

Tactic	Technique
Defense Evasion	T1070 - Indicator Removal
Defense Evasion	T1562 - Impair Defenses

Profile

Level 1 - Authoritative Name Server
Level 1 - Caching Only Name Server