用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-ubuntu2004-v300-1-5-3命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-ubuntu2004-v300-1-5-3 |
| description | Ensure core dumps are restricted |
| category | cis-storage |
| version | 3.0.0 |
| author | cyberstrike-official |
| tags | ["cis","ubuntu","linux","ubuntu-20.04","core-dumps","hardening","sysctl"] |
| cis_id | 1.5.3 |
| cis_benchmark | CIS Ubuntu Linux 20.04 LTS Benchmark v3.0.0 |
| tech_stack | ["ubuntu","linux"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
A core dump is the memory of an executable program. It is generally used to determine why a program aborted. It can also be used to glean confidential information from a core file. The system provides the ability to set a soft limit for core dumps, but this can be overridden by the user.
Setting a hard limit on core dumps prevents users from overriding the soft variable. If core dumps are required, consider setting limits for user groups (see limits.conf(5)). In addition, setting the fs.suid_dumpable variable to 0 will prevent setuid programs from dumping core.
Run the following command and verify output matches:
# grep -Ps -- '^\h*\*\h+hard\h+core\h+0\b' /etc/security/limits.conf /etc/security/limits.d/*
* hard core 0
Run the following script to verify fs.suid_dumpable = 0:
Run the following script to verify the following kernel parameter is set in the running configuration and correctly loaded from a kernel parameter configuration file:
fs.suid_dumpable is set to 0Run the following command to check if systemd-coredump is installed:
# systemctl list-unit-files | grep coredump
If anything is returned systemd-coredump is installed.
systemd-coredump is installed, then run the following command and verify output matches:# grep -Psi -- '^\s*Storage\s*=\s*none\s*$' /etc/systemd/coredump.conf
Storage=none
# grep -Psi -- '^\s*ProcessSizeMax\s*=\s*0' /etc/systemd/coredump.conf
ProcessSizeMax=0
* hard core 0 should be set in limits.conffs.suid_dumpable should be set to 0Storage=none and should be setProcessSizeMax=0Add the following line to /etc/security/limits.conf or a /etc/security/limits.d/* file:
* hard core 0
Set the following parameter in /etc/sysctl.conf or a file in /etc/sysctl.d/ ending in .conf:
fs.suid_dumpable = 0Example:
# printf "\n%s" "fs.suid_dumpable = 0" >> /etc/sysctl.d/60-fs_sysctl.conf
Run the following command to set the active kernel parameter:
# sysctl -w fs.suid_dumpable=0
Note: If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten.
systemd-coredump is installed: edit /etc/systemd/coredump.conf and add/modify the following lines:Storage=none
ProcessSizeMax=0
Run the command:
systemctl daemon-reload
MITRE ATT&CK Mappings: T1005, T1005.000 | TA0007 | M1057