Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-ubuntu1204-v110-8-2-4The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
Based on SOC occupation classification
Showing SKILL.md
| name | cis-ubuntu1204-v110-8-2-4 |
| description | Create and Set Permissions on rsyslog Log Files |
| category | cis-os-hardening |
| version | 1.1.0 |
| author | cyberstrike-official |
| tags | ["cis","ubuntu",12.04,"linux","logging","rsyslog","permissions","log-files"] |
| cis_id | 8.2.4 |
| cis_benchmark | CIS Ubuntu 12.04 LTS Server Benchmark v1.1.0 |
| tech_stack | ["ubuntu","linux"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
A log file must already exist for rsyslog to be able to write to it.
It is important to ensure that log files exist and have the correct permissions to ensure that sensitive rsyslog data is archived and protected.
For each <logfile> listed in the /etc/rsyslog.conf file, perform the following command and verify that the <owner>:<group> is root:root and the permissions are 0600 (for sites that have not implemented a secure group) and root:securegrp with permissions of 0640 (for sites that have implemented a secure group):
ls -l <logfile>
Log files should be owned by root:root with permissions 0600 or root:securegrp with permissions 0640.
For sites that have not implemented a secure admin group:
Create the /var/log/ directory and for each <logfile> listed in the /etc/rsyslog.conf or /etc/rsyslog.d/* files, perform the following commands:
touch <logfile>
chown root:root <logfile>
chmod og-rwx <logfile>
For sites that have implemented a secure admin group:
Create the /var/log/ directory and for each <logfile> listed in the /etc/rsyslog.conf file, perform the following commands (where securegrp is the name of the security group):
touch <logfile>
chown root:<securegrp> <logfile>
chmod g-wx,o-rwx <logfile>
By default, log files may have varying permissions depending on the installation.
Level 1 - Scored