pentest-stig
Skill8 starsChanged 3 months agoMITView on GitHub
DISA STIG (Security Technical Implementation Guide) audit + GPO remediation + keep-open justification advisory. Triggers on STIG, DISA, SCAP, OpenSCAP, Compliance Master, GPO, group policy hardening, keep-open justification, CKL.
In this repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-automationSkill
- consultingSkill
- contentSkill
- customer-successSkill
- data-analyticsSkill
- designSkill
- design-tokensSkill
- developmentSkill
- devopsSkill
- ecommerceSkill
- emailSkill
- expo-app-configSkill
- expo-config-pluginSkill
- expo-dev-clientSkill
- expo-eas-buildSkill
- expo-eas-submitSkill
- expo-eas-updateSkill
- expo-modulesSkill
- expo-notificationsSkill
- expo-orchestratorSkill
- expo-prebuildSkill
- expo-routerSkill
- expo-troubleshootingSkill
- financeSkill
- frontend-tasteSkill
- marketingSkill
- market-researchSkill
- mobileSkill
- pentest-adSkill
- pentest-apiSkill
- pentest-bizlogicSkill
- pentest-bugbountySkill
- pentest-cicdSkill
- pentest-cloudSkill
- pentest-credentialsSkill
- pentest-ctfSkill
- pentest-detectionSkill
- pentest-engagementSkill
- pentest-exploit-chainSkill
- pentest-forensicsSkill
- pentest-llmSkill
- pentest-malwareSkill
- pentest-mobileSkill
- pentest-opsec-evidenceSkill
- pentest-orchestratorSkill
- pentest-privescSkill
- pentest-reconSkill
- pentest-reportSkill
- pentest-socialSkill
- pentest-threat-modelSkill
- pentest-webSkill
- pentest-wirelessSkill
- productivitySkill
- productSkill
- salesSkill
- security-checkSkill
- securitySkill
- seo-crawl-budgetSkill
- seoSkill
- The first 60 shown.
The file
Files
pentest-stig
DISA STIG audit + remediation advisory. Standard in government, finance, and critical-infrastructure engagements.
Triggers
- "STIG audit"
- "SCAP / OpenSCAP scan"
- "GPO hardening"
- "keep-open justification"
- "CKL file analysis"
- "compliance baseline"
What STIG Is
A security configuration baseline published by the US Department of Defense Defense Information Systems Agency (DISA). Specific rules for Linux, Windows, web servers, network devices, databases, and applications.
Format:
- STIG ID (Group_ID + Rule_ID): maps to GENERIC-NIST-800-53
- Severity: CAT I (critical), CAT II (high), CAT III (medium)
- Vulnerability discussion: why it matters
- Check Text: how it is checked
- Fix Text: how it is fixed
SCAP Scan
# OpenSCAP (Linux audit)
oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_stig \
--results scan-results.xml \
--report scan-report.html \
--datastream-id ds-rhel8.xml \
ssg-rhel8-ds.xml
# Windows: SCC Tool (DISA) or the OpenSCAP Windows port
# Web: scap-security-guide / OpenSCAP web UICKL (Checklist) Format
An XML format opened with the DISA STIG Viewer. Per STIG ID:
- NotAFinding — compliant
- Open — a finding exists
- Not_Applicable — out of scope
- Not_Reviewed — not yet reviewed
Common STIG Categories (Linux RHEL 8)
| ID | Title | CAT |
| RHEL-08-010020 | Crypto Policy = FIPS | I |
| RHEL-08-010049 | Banner login warn message | III |
| RHEL-08-010130 | SSH PermitRootLogin no | II |
| RHEL-08-010140 | Disable USB mass storage | II |
| RHEL-08-010210 | /tmp nosuid mount | II |
| RHEL-08-010370 | sudo logging | II |
| RHEL-08-010460 | password complexity (pwquality) | II |
| RHEL-08-010620 | session timeout 15min | III |
| RHEL-08-020220 | account lockout 3 try | II |
| RHEL-08-040340 | firewalld enabled | II |
Common STIG Categories (Windows Server 2022)
| ID | Title | CAT |
| WN22-00-000010 | Inactive accounts disable | III |
| WN22-AC-000010 | Lockout duration | II |
| WN22-AC-000020 | Lockout threshold | II |
| WN22-AU-000010 | Audit Account Logon | II |
| WN22-SO-000020 | Anonymous SID lookup | I |
| WN22-SO-000080 | LM hash storage off | I |
| WN22-SO-000100 | LMCompat Level 5 | I |
Keep-Open Justification
Some STIG rules are not applied for business-specific reasons. Writing a justification:
## STIG ID: RHEL-08-010130 (SSH PermitRootLogin)
### Status: Open (Mitigated)
### Justification
- **Risk**: Direct root SSH allows offline brute force, lateral movement
- **Compensating Control 1**: SSH bind only to management VLAN (192.168.99.0/24)
- **Compensating Control 2**: PubkeyAuth only (PasswordAuth off)
- **Compensating Control 3**: All sudo + root commands logged to remote syslog
- **Compensating Control 4**: 2FA via FreeIPA (TOTP)
- **Compensating Control 5**: Bastion host required (jump server with session record)
- **Business Need**: Legacy application requires root for service init
- **Remediation Roadmap**: Application refactor to sudo-only by Q4 2026
- **Approval**: Security Manager <name>, <date>
- **Review Frequency**: Every 6 monthsGPO Remediation Mapping
# STIG WN22-SO-000080 (LM hash storage off)
# Manual GPO path:
# Computer Config -> Policies -> Windows Settings -> Security Settings
# -> Local Policies -> Security Options
# -> "Network security: Do not store LAN Manager hash value on next password change"
# Enable
# Via command (LGPO.exe or ADMX):
ntfrsutl ds # is there AD connectivity
# Add into the Group Policy Object:
# HKLM\SYSTEM\CurrentControlSet\Control\Lsa\NoLMHash = 1STIG Audit Automation
# STIG check across the whole system (cron / Ansible)
oscap xccdf eval --profile stig \
--results-arf /var/log/stig-arf.xml \
--report /var/log/stig-report.html \
ssg-rhel8-ds.xml
# Ansible STIG playbook
ansible-playbook -i inventory stig-rhel8-playbook.yml --check
# Result -> convert to CKL
sscap-to-checklist --input stig-arf.xml --output system.cklOutput Template
## STIG Audit — <system>
### Compliance Score
- Total: 250 STIG rules
- NotAFinding: 195 (78%)
- Open: 38 (15.2%)
- Not_Applicable: 12 (4.8%)
- Not_Reviewed: 5 (2%)
### CAT I Open (Critical — 5)
1. RHEL-08-010210 /tmp nosuid missing (remediation: 1-line mount opt)
2. WN22-SO-000080 LM hash storage on (GPO update)
3. ... (3 more)
### Keep-Open Justified (Mitigated)
1. RHEL-08-010130 SSH root login (5 compensating control)
2. ...
### Remediation Plan
| Priority | Count | Effort | Timeline |
|----------|-------|--------|----------|
| CAT I | 5 | 8h | 1 week |
| CAT II | 28 | 32h | 1 month |
| CAT III | 5 | 8h | 3 months |Out-of-Scope
- Applying production hardening (the client sysadmin does that)
- Writing STIGs (DISA official)
- Non-DISA frameworks (CIS Benchmark, NIST 800-53 — separate skill)
Does 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.

