The Center for Internet Security (CIS) publishes benchmarks for every major OS, and DISA releases Security Technical Implementation Guides (STIGs) for US DoD systems. These frameworks provide thousands of configuration recommendations. This lesson shows you how to navigate the CIS PDF and STIG XML, prioritize Level 1 settings, and map them to your existing GPOs and automation—so you're not just compliant but actually secure.
A CIS Benchmark is organized by control area (e.g., Account Policies, Network Configuration). Each recommendation has a profile (Level 1 – basic security, Level 2 – defense-in-depth), a description, rationale, audit, and remediation steps. Level 1 should be implemented everywhere without breaking functionality. Level 2 may impact performance or compatibility. Use the CIS-CAT tool to assess compliance against a benchmark.
The download includes ready-to-import GPO backups that apply the Level 1 settings. Always review the PDF to understand the security impact.
STIGs are far more prescriptive and stringent than CIS. They are delivered as XML (xccdf) files and can be ingested by SCAP scanners. Each STIG rule has a severity (CAT I, II, III), a vulnerability discussion, and a fix text. STIGs enforce settings like FIPS 140-2 cryptography, strict audit policies, and removal of GUI on servers. Even if you're not a DoD contractor, STIGs provide an excellent high-security baseline.
# Use OpenSCAP to scan a system against a STIG profile
sudo oscap xccdf eval --profile stig --report report.html /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml💡 STIG Viewer is a Java tool to visualize STIG checklists and track compliance. It's essential for DoD accreditation packages.
| Aspect | CIS Benchmarks | DISA STIGs |
|---|---|---|
| Audience | Industry best practice | US Department of Defense |
| Format | PDF, GPO backups, build kit | XCCDF/OVAL XML, SCAP content |
| Severity | Level 1 (basic) / Level 2 (advanced) | CAT I (high) / CAT II (medium) / CAT III (low) |
| Customization | Highly customizable | Less flexible, must meet exact criteria |
Don't blindly apply all settings. Map CIS/STIG controls to your organization's risk assessment. Focus on settings that mitigate the most likely threats: account lockout, audit logging, service minimization. For each setting you choose not to implement, document the risk acceptance and compensating control. Use a compliance tracking spreadsheet or GRC tool to manage this.
⚠️ Applying STIGs can break many applications (e.g., FIPS mode, strict service disabling). Always test in a non-production environment before deploying to production.
Verify exercises to earn ★ 160 XP and unlock next lab level.