usap-skills / system-security
CLAUDE.md4 starsChanged 2 months agoApache-2.0View on GitHub
The System Security domain contains skills for assessing and hardening operating system and host configurations against recognized security baselines. Skills in this domain evaluate Linux, Windows, and macOS systems against CIS Benchmarks, DISA STIGs, and NSA hardening guides, classify configuration gaps by severity and MITRE ATT&CK technique, and produce prioritized, evidence-backed remediation. System security skills are read-only assessors — they parse scanner output, score findings, and recommend exact remediation commands, but never execute changes. Every mutating remediation step is flagged…
In this repository100 other files it gives its agents.
- agents/CLAUDE.mdCLAUDE.md
- appsec-devsecops/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- cloud-infra/CLAUDE.mdCLAUDE.md
- detection/CLAUDE.mdCLAUDE.md
- governance/CLAUDE.mdCLAUDE.md
- identity-access/CLAUDE.mdCLAUDE.md
- pentest/CLAUDE.mdCLAUDE.md
- platform-ai/CLAUDE.mdCLAUDE.md
- red-team/CLAUDE.mdCLAUDE.md
- response/CLAUDE.mdCLAUDE.md
- risk-compliance/CLAUDE.mdCLAUDE.md
- webapp-security/CLAUDE.mdCLAUDE.md
- agent-integrity-monitorSkill
- ai-agent-securitySkill
- ai-ethics-governanceSkill
- ai-red-teamingSkill
- api-security-postureSkill
- appsec-code-reviewSkill
- appsec-customizeSkill
- attack-path-analysisSkill
- attack-surface-managementSkill
- behavioral-analyticsSkill
- build-integritySkill
- ciso-brief-generatorSkill
- cloud-security-postureSkill
- cloud-workload-protectionSkill
- compliance-mappingSkill
- container-image-scanSkill
- containment-advisorSkill
- continuous-pentestingSkill
- credential-attacksSkill
- cryptography-key-managementSkill
- cyber-insuranceSkill
- data-security-classificationSkill
- deception-honeypotSkill
- detection-engineeringSkill
- devsecops-pipelineSkill
- endpoint-os-securitySkill
- enterprise-risk-assessmentSkill
- findings-trackerSkill
- finding-triageSkill
- forensicsSkill
- guardrailSkill
- iac-securitySkill
- identity-access-riskSkill
- incident-classificationSkill
- incident-commanderSkill
- insider-physical-riskSkill
- internal-audit-assuranceSkill
- knowledge-managementSkill
- metrics-reportingSkill
- network-exposureSkill
- orchestratorSkill
- os-hardeningSkill
- ot-iot-device-securitySkill
- owasp-top10-classifierSkill
- patch-candidateSkill
- pentest-reportingSkill
- persona-coverage-auditSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
All skill paths are relative from the repository root as system-security/<slug>/.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
System Security Domain — CLAUDE.md
Purpose
The System Security domain contains skills for assessing and hardening operating system and host configurations against recognized security baselines. Skills in this domain evaluate Linux, Windows, and macOS systems against CIS Benchmarks, DISA STIGs, and NSA hardening guides, classify configuration gaps by severity and MITRE ATT&CK technique, and produce prioritized, evidence-backed remediation.
System security skills are read-only assessors — they parse scanner output, score findings, and recommend exact remediation commands, but never execute changes. Every mutating remediation step is flagged for a human approval gate. All outputs are structured payloads consumable by downstream vulnerability-management, detection-engineering, and governance skills.
Subdomains covered by this domain:
- OS configuration hardening (CIS / STIG / NSA baselines)
- Host audit logging and integrity assessment
- Privilege-escalation surface review (SUID/SGID, sudo, cron)
- Kernel and mandatory-access-control hardening (ASLR, NX, Seccomp, SELinux, AppArmor)
Skills Catalog
| Skill | Slug | Primary Tool | MITRE Coverage |
| os-hardening | system-security/os-hardening | os-hardening_tool.py | T1222, T1068, T1021.004, T1548.001, T1562.002 |
All skill paths are relative from the repository root as system-security/<slug>/.
Python Tools Reference
| Tool | Path | Purpose | Key Args |
| os-hardening_tool.py | system-security/os-hardening/scripts/os-hardening_tool.py | Emits the skill status payload for orchestration | --input, --output |
python system-security/os-hardening/scripts/os-hardening_tool.py --output jsonDomain Best Practices
- Map every finding to a named baseline control. A hardening finding without a CIS/STIG/NSA control ID is not actionable evidence. Tag each finding with the exact control reference (e.g. CIS Ubuntu 22.04 v1.0 — 5.2.7).
- Prioritize by exploitability × impact, not raw count. A single unpatched local privilege-escalation CVE outranks a dozen cosmetic policy deviations. Order remediation by exploitability, blast radius, and ease of fix.
- Flag every mutating remediation for a human gate. Remediation commands (disabling services, changing SSH config, enabling SELinux enforcing) are recommendations only. Set
human_approval_requiredon any output whose action would change a running system. - Confirm the system role before selecting a baseline profile. CIS Level 1 vs Level 2 and STIG categories depend on whether the host is internet-facing, a workstation, or a hardened bastion. Selecting the wrong profile produces false findings.
- Route findings onward. CVE-bearing findings go to
vulnerability-management; audit-logging and detection gaps go todetection-engineering; compliance evidence goes tocompliance-mapping.
Related Domains
detection/— audit-logging gaps found here become detection-engineering rule candidatesrisk-compliance/— hardening evidence maps to compliance-mapping control requirementscloud-infra/— host hardening complements endpoint-os-security and cloud-workload-protection
Path Reference
system-security/<slug>/
README.md -- skill overview and quick commands
SKILL.md -- full skill specification and methodology
scripts/ -- executable Python tools
references/ -- supporting documentation
expected_outputs/ -- representative tool outputs for validation
assets/ -- supporting data filesDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

