How do I install the CIS Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured skill?

Run npx skillmds@latest add cyberstrikeus/cis-ubuntu-14-04-lts-4-2-1-2-ensure-logging-is-configured 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.

Is CIS Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured 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 Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured?

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 Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured free to use?

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

Who published CIS Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured?

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

CIS Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured by cyberstrikeus

Name: CIS Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured
Author: cyberstrikeus

File contents

4.2.1.2 Ensure logging is configured (Not Scored)

Profile Applicability

Level 1 - Server
Level 1 - Workstation

Description

The /etc/rsyslog.conf and /etc/rsyslog.d/*.conf files specifies rules for logging and which files are to be used to log certain classes of messages.

Rationale

A great deal of important security-related information is sent via rsyslog (e.g., successful and failed su attempts, failed login attempts, root login attempts, etc.).

Audit Procedure

Review the contents of the /etc/rsyslog.conf and /etc/rsyslog.d/*.conf files to ensure appropriate logging is set. In addition, run the following command and verify that the log files are logging information:

ls -l /var/log/

Expected Result

Log files should exist and contain recent entries for all configured facilities.

Remediation

Edit the following lines in the /etc/rsyslog.conf and /etc/rsyslog.d/*.conf files as appropriate for your environment:

*.emerg                                 :omusrmsg:*
mail.*                                  -/var/log/mail
mail.info                               -/var/log/mail.info
mail.warning                            -/var/log/mail.warn
mail.err                                 /var/log/mail.err
news.crit                               -/var/log/news/news.crit
news.err                                -/var/log/news/news.err
news.notice                             -/var/log/news/news.notice
*.=warning;*.=err                       -/var/log/warn
*.crit                                   /var/log/warn
*.*;mail.none;news.none                 -/var/log/messages
local0,local1.*                         -/var/log/localmessages
local2,local3.*                         -/var/log/localmessages
local4,local5.*                         -/var/log/localmessages
local6,local7.*                         -/var/log/localmessages

Run the following command to reload the rsyslogd configuration:

pkill -HUP rsyslogd

Default Value

Basic logging is configured by default.

References

See the rsyslog.conf(5) man page for more information.

Profile

Level 1 - Server
Level 1 - Workstation

---name: cis-ubuntu-14-04-lts-4-2-1-2-ensure-logging-is-configureddescription: Configure rsyslog to capture appropriate logging for all facilities---# 4.2.1.2 Ensure logging is configured (Not Scored)## Profile Applicability- Level 1 - Server- Level 1 - Workstation## DescriptionThe `/etc/rsyslog.conf` and `/etc/rsyslog.d/*.conf` files specifies rules for logging and which files are to be used to log certain classes of messages.## RationaleA great deal of important security-related information is sent via `rsyslog` (e.g., successful and failed su attempts, failed login attempts, root login attempts, etc.).## Audit ProcedureReview the contents of the `/etc/rsyslog.conf` and `/etc/rsyslog.d/*.conf` files to ensure appropriate logging is set. In addition, run the following command and verify that the log files are logging information:```bashls -l /var/log/```## Expected ResultLog files should exist and contain recent entries for all configured facilities.## RemediationEdit the following lines in the `/etc/rsyslog.conf` and `/etc/rsyslog.d/*.conf` files as appropriate for your environment:```*.emerg :omusrmsg:*mail.* -/var/log/mailmail.info -/var/log/mail.infomail.warning -/var/log/mail.warnmail.err /var/log/mail.errnews.crit -/var/log/news/news.critnews.err -/var/log/news/news.errnews.notice -/var/log/news/news.notice*.=warning;*.=err -/var/log/warn*.crit /var/log/warn*.*;mail.none;news.none -/var/log/messageslocal0,local1.* -/var/log/localmessageslocal2,local3.* -/var/log/localmessageslocal4,local5.* -/var/log/localmessageslocal6,local7.* -/var/log/localmessages```Run the following command to reload the `rsyslogd` configuration:```bashpkill -HUP rsyslogd```## Default ValueBasic logging is configured by default.## References1. See the rsyslog.conf(5) man page for more information.## Profile- Level 1 - Server- Level 1 - Workstation

Frequently asked questions

CIS Ubuntu 14.04 LTS - 4.2.1.2 Ensure logging is configured