用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-ubuntu1804-v220-1-5-1命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-ubuntu1804-v220-1-5-1 |
| description | Ensure ptrace_scope is restricted |
| category | cis-storage |
| version | 2.2.0 |
| author | cyberstrike-official |
| tags | ["cis","ubuntu","linux","ubuntu-18.04","ptrace","process-hardening","kernel"] |
| cis_id | 1.5.1 |
| cis_benchmark | CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0 |
| tech_stack | ["ubuntu","linux"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
The ptrace() system call provides a means by which one process (the "tracer") may observe and control the execution of another process (the "tracee"), and examine and change the tracee's memory and registers.
If one application is compromised, it would be possible for an attacker to attach to other running processes (e.g. Bash, Firefox, SSH sessions, GPG agent, etc) to extract additional credentials and continue to expand the scope of their attack.
Enabling restricted mode will limit the ability of a compromised process to PTRACE_ATTACH on other processes running under the same user. With restricted mode, ptrace will continue to work with root user.
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:
kernel.yama.ptrace_scope is set to 1Note: kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that "correct" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.
#!/usr/bin/env bash
{
l_output="" l_output2=""
a_parlist=("kernel.yama.ptrace_scope=1")
l_ufwscf="$([ -f /etc/default/ufw ] && awk -F= '/^\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)"
a_searchpath=("/run/sysctl.d/" "/etc/sysctl.d/" "/usr/local/lib/sysctl.d/" "/usr/lib/sysctl.d/" "/lib/sysctl.d/")
unset A_files
declare -A A_files # Array of "valid" files
A_files+=(["sysctl.conf"]="/etc/sysctl.conf")
for l_searchpath ;
[ -d ];
IFS= -r -d $ l_filename;
[ -f ];
l_basename=
[ -z ];
A_files+=([]=)
< <(find - f -name -print0)
a_sorted=()
IFS= -rd l_key;
a_sorted+=( )
< <( | -rz)
()
{
l_var= l_var2=
l_krp=
[ = ];
l_output=
l_output2=
}
IFS= -r l_kpname l_kpvalue;
l_kpname=; l_kpvalue=
! grep -Pqs /sys/module/ipv6/parameters/disable && grep -q <<< ;
l_output=
kernel_parameter_chk
< <( )
A_files; a_sorted
[ -z ];
-e
-e
[ -n ] && -e
}
- Audit Result:
** PASS **
- "kernel.yama.ptrace_scope" is correctly set to "1" in the running configuration
Set the following parameter in /etc/sysctl.conf or a file in /etc/sysctl.d/ ending in .conf:
kernel.yama.ptrace_scope = 1Example:
printf '%s\n' "kernel.yama.ptrace_scope = 1" >> /etc/sysctl.d/60-kernel_sysctl.conf
Run the following command to set the active kernel parameter:
sysctl -w kernel.yama.ptrace_scope=1
Note: If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten.
kernel.yama.ptrace_scope=1
Ptrace is very rarely used by regular applications and is mostly used by debuggers such as gdb and strace.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software | X | X | |
| v7 | 9.2 Ensure Only Approved Ports, Protocols and Services Are Running | X | X |
| Techniques / Sub-techniques | Tactics | Mitigations |
|---|---|---|
| T1055.008 |