Join our Newsletter — 33% off our NHI Course
Home› Guides› DISA STIG Guide: How to Read, Apply and…
Guide Endpoint Security

DISA STIG Guide: How to Read, Apply and Evidence STIG Compliance

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Security Technical Implementation Guides (STIGs) are mandatory for US Department of Defense systems and are reused far beyond defence, but teams often apply them as a scanner output to be cleared rather than as a configuration standard with an evidence trail. STIGs are produced by the Defense Information Systems Agency (DISA) and set out product-specific configuration requirements, each with a severity category, check procedure and fix text. This guide explains how STIGs relate to Security Requirements Guides (SRGs), how to read a STIG rule, how to apply STIGs with automation without breaking systems, how to assess them with SCAP and manual checks, and how to build checklist and exception evidence an authorising official will accept. It is for platform engineers, compliance leads and security architects at defence suppliers, government contractors and organisations that adopt STIGs voluntarily.

Key takeaways

  • STIGs implement SRGs. An SRG states technology-level requirements; a STIG translates them into concrete settings for one product and version.
  • Severity drives priority. CAT I findings are the most severe and are fixed first; CAT II and CAT III follow, and exceptions at any level need approval by the authorising official in DoD environments.
  • Automated scans cover only part of a STIG. SCAP benchmarks check the automatable rules; the rest need manual review recorded in a checklist.
  • Version and release matter. STIGs are updated on a quarterly cycle, and your evidence must name the exact version and release you assessed against.
  • Many rules are identity rules. Account lockout, privileged group membership, smart card or PKI authentication, service account rights and SSH settings make up a large share of OS and application STIGs.

What STIGs are and who must use them

DoD Instruction 8500.01 (Cybersecurity, as issued in 2014) assigns DISA responsibility for developing and maintaining SRGs and STIGs, with support from NSA/CSS. The same instruction requires DoD Component heads to ensure that all DoD IT under their purview complies with applicable STIGs, security configuration guides and SRGs, with exceptions documented and approved by the responsible authorising official (AO). DoD applies the Risk Management Framework through NIST SP 800-37 as implemented by DoDI 8510.01, and STIG results are part of the evidence for an authorisation decision.

  • Mandatory: DoD systems and systems operated on behalf of DoD where the contract or authorisation requires STIG compliance. Check the contract language: it decides which STIGs and which release apply.
  • Common by choice: other government bodies, regulated industries and product vendors use STIGs as a strict baseline, and CIS publishes STIG-aligned benchmark profiles (CIS describes its STIG profile as replacing the former Level 3). See the CIS Benchmarks Guide.
  • Not the same as CMMC: NIST SP 800-171 Rev. 3 requires baseline configurations and configuration settings (03.04.01 and 03.04.02) but does not name STIGs. Many defence suppliers use STIGs to meet those requirements; whether that is required depends on the contract. See the NIST SP 800-171 and CMMC 2.0 Guide.

The official STIG library is published on DISA's cyber.mil site. At the time of writing that site did not serve content to our automated checks, so download STIGs, SCAP benchmarks and STIG Viewer directly from DISA and verify file checksums.

SRGs, STIGs and how a rule is built

ArtefactWhat it containsExampleWho uses it
Security Requirements Guide (SRG)Technology-class requirements traced to NIST SP 800-53 controls, independent of productGeneral Purpose Operating System SRG, Application Server SRG, Network Device SRGVendors writing a new STIG; systems with no product STIG
STIGProduct and version specific rules with check and fix proceduresWindows 11, Red Hat Enterprise Linux 9, a database or web server STIGSystem administrators and assessors
SCAP benchmarkMachine-readable (XCCDF and OVAL) content for the automatable rules of a STIGWindows 11 STIG SCAP BenchmarkScanners such as SCAP Compliance Checker
ChecklistA STIG instance for one asset, recording status, finding details and comments per ruleSTIG Viewer checklist files (.ckl, and .cklb for newer STIG Viewer releases)Evidence for assessors and authorisation packages

Reading a STIG rule

  • Identifiers: each rule carries a Group or Vulnerability ID (V- number), a Rule ID (SV- number with a revision suffix) and a product STIG ID (for example a WN11- prefix for Windows 11). Use the Vulnerability ID as the stable key in your exception register; Rule ID revisions change between releases.
  • Severity: CAT I, II or III (see below).
  • Discussion: why the rule exists.
  • Check text: exactly how to verify, often a registry path, Group Policy setting, file content or command output.
  • Fix text: how to remediate.
  • CCI references: Control Correlation Identifiers link the rule to NIST SP 800-53 controls, which is how STIG results feed RMF control assessments.
  • Version and release: STIGs are numbered as Version and Release (for example V2R9). A new version usually means substantial restructuring; a new release is an incremental update.

Severity categories

CategoryDefinition (as reproduced in AWS STIG documentation)Practical handling
CAT I (High)The most severe risk; any vulnerability that can result in loss of confidentiality, availability or integrityFix before production or obtain explicit AO acceptance; track daily
CAT II (Medium)Any vulnerability that can result in loss of confidentiality, availability or integrity, but the risks can be mitigatedMajority of rules; fix through the baseline, document mitigations where not applied
CAT III (Low)Any vulnerability that degrades measures to protect against loss of confidentiality, availability or integrityApply through the baseline; lower priority for exceptions

Where identity fits

STIGs are dense with authentication and authorisation requirements, and these are the rules most likely to break automation.

  • PKI and smart card authentication: DoD STIGs expect multifactor authentication using DoD PKI for privileged and often non-privileged access. Plan how break-glass accounts and automation authenticate before enforcing.
  • Account policy: lockout, password complexity and inactivity disablement rules hit service accounts with static passwords. Use managed service accounts on Windows. See the Windows Services and Service Account Security Guide.
  • Privileged groups and user rights: Windows STIGs restrict membership of Administrators and rights such as "Log on as a service" and "Debug programs". Every non-standard entry needs a documented owner and reason.
  • Linux access: RHEL and other Linux STIGs constrain SSH (root login, ciphers, MACs), sudo, PAM faillock and session timeouts. Deployment accounts with passwordless sudo are a common finding. See the Linux Server Hardening Guide.
  • FIPS mode and cryptography: Red Hat notes its STIG profile requires a system installed in FIPS mode, which affects which algorithms keys, certificates and tokens can use (NIST SP 800-53 SC-13).
  • Scanner and automation identities: credentialed SCAP scans and configuration management tools need privileged access to every target. Use dedicated accounts, vault their credentials and restrict their logon rights.

Applying STIGs: a phased approach

  1. Identify applicable STIGs per system: operating system, each installed product with a STIG (browsers, Office, databases, web servers, Java, antivirus), and role-specific STIGs (domain controller, DNS server). Where no STIG exists, use the relevant SRG.
  2. Fix the release: record the STIG version and release in the system's configuration baseline. Red Hat, for example, maps each RHEL minor release to a specific STIG release and advises using the profile shipped for that minor release.
  3. Scan before change: run SCAP and complete manual checks on a reference system to see the gap.
  4. Decide per rule: apply, not applicable (with reason), or exception with mitigation. Exceptions go to the AO in DoD environments.
  5. Automate the build: apply STIG settings at image build time rather than by hand. Options include DISA-supplied Group Policy objects for Windows, the SCAP Security Guide STIG profile with generated Ansible or Bash remediation for Linux, PowerSTIG Desired State Configuration resources, the Intune STIG audit baseline for evidence in GCC High tenants, and cloud image pipelines such as AWS EC2 Image Builder STIG components.
  6. Test in rings: STIGs are strict, so test on non-production systems with application owners. Pay particular attention to TLS and cipher restrictions, FIPS mode, smart card enforcement, audit settings and service account rights.
  7. Roll out with rollback: for Windows, separate GPOs per STIG so a problem can be isolated by unlinking one object; for Linux, keep remediation in version-controlled configuration management and snapshot before applying.
  8. Update each quarter: review the release notes of new STIG releases, compare checklists, and update automation and exceptions.

Choosing an automation route

RouteStrengthWatch out for
DISA GPO packages (Windows)Closest to the published STIG; simple to importMust be merged with your own GPOs and tailored; some rules need manual action
SCAP Security Guide STIG profile (Linux)Scan and remediation from one profile; Ansible and Bash outputCommunity content tracks the DISA STIG but is not the DISA artefact; confirm against the official STIG for evidence
PowerSTIG (DSC)Supports overrides, organisational values within allowed ranges, de-duplication across STIGs and documented exceptionsCommunity supported; Azure Automation State Configuration retires on 30 September 2027, so plan for Azure Machine Configuration or another DSC host
Cloud image pipelinesHardened images at build, levels applied cumulatively (Low, Medium, High)Skipped rules are logged, not fixed; you still need a checklist
Hardened images from CIS (STIG profile)Fast start in public cloudCIS STIG profile is not the DISA STIG; accept only if your contract allows

Small contractors with a handful of systems can work directly in STIG Viewer with DISA GPOs and SCC. Larger estates need configuration management, pipeline-built images and a central store of checklists, otherwise quarterly releases become unmanageable.

Products without a STIG

  • Use the SRG: assess the product against the relevant technology SRG (operating system, application server, database, network device) and record how each requirement is met.
  • Ask the vendor: some vendors publish their own SRG-based guidance or are working with DISA on a STIG; ask for it during procurement rather than after deployment.
  • Document the gap: where neither exists, write a local hardening standard from vendor documentation and record it as the configuration baseline the AO accepts.

Assessing and evidencing compliance

  • SCAP Compliance Checker (SCC): developed at NIWC Atlantic and distributed through DISA, SCC is a SCAP-validated authenticated configuration scanner supporting SCAP 1.0 to 1.4. It scans Windows and Linux or Solaris systems locally and remotely and supports Cisco IOS and IOS XE. Use the DISA SCAP benchmark matching the STIG release.
  • OpenSCAP: scans with the SCAP Security Guide STIG profile on Linux. See the OpenSCAP and Linux Compliance Scanning Guide.
  • Manual checks: rules without automated content are reviewed by an administrator following the check text, with the result and finding details recorded in the checklist.
  • STIG Viewer checklists: import SCAP results into a checklist per asset and STIG, then complete manual rules. Each rule ends as Open, Not a Finding, Not Applicable or Not Reviewed, with comments.
  • Authorisation package: in DoD, checklists and scan results support the RMF control assessment; open findings that cannot be fixed go on the Plan of Action and Milestones (NIST SP 800-53 CA-5) with mitigations and dates.

Evidence an assessor expects

Evidence itemWhat good looks like
Applicable STIG list per systemEvery product with a STIG identified, with version and release
Completed checklistsNo Not Reviewed rules; finding details and comments filled in for every Open and Not Applicable rule
SCAP resultsRecent scan output using the matching benchmark release, imported into the checklist
Exception and mitigation recordsKeyed by Vulnerability ID, with mitigation, approver, expiry and POA&M reference
Change and build recordsEvidence that the hardened image or configuration code implements the STIG release claimed

Metrics

  • Open CAT I findings: target zero, with any accepted risk named and dated.
  • Checklist completeness: percentage of rules with a final status (target 100 percent, no Not Reviewed).
  • Release currency: share of systems assessed against the current quarterly release.
  • Exception age: exceptions past expiry or without a POA&M entry (target zero).
  • Drift: new Open findings between scheduled scans on systems that previously passed.

Framework mapping

FrameworkReferenceLink to STIG work
NIST SP 800-53 Rev. 5CM-2 Baseline Configuration; CM-6 Configuration SettingsSTIGs are the configuration settings source; CCIs trace each rule to controls
NIST SP 800-53 Rev. 5RA-5 Vulnerability Monitoring and Scanning; CA-5 Plan of Action and MilestonesSCAP scanning; open findings tracked to closure
NIST SP 800-171 Rev. 303.04.01 Baseline Configuration; 03.04.02 Configuration SettingsSTIGs are a common way to define and enforce settings for CUI systems
NIST CSF 2.0PR.PS-01 Configuration management practices are established and appliedOutcome level mapping
CIS Controls v8.1Control 4 Secure Configuration of Enterprise Assets and SoftwareSTIG as the configuration standard
ISO/IEC 27001:2022Annex A 8.9 Configuration managementDocumented and monitored secure configuration

Common failure patterns

  • Treating the SCAP score as the result: automated content covers only part of a STIG, so systems with high scan scores still have unreviewed manual rules, and assessors reject the checklist.
  • Assessing against the wrong release: scans use an old SCAP benchmark, or the checklist claims a release the build pipeline never implemented.
  • Applying everything at once in production: FIPS mode, TLS restrictions and smart card enforcement break applications and remote management, and the whole baseline is rolled back.
  • Exceptions keyed to Rule IDs: Rule ID revisions change between releases, so exceptions silently stop matching and old findings reappear or disappear.
  • Service accounts left as exceptions forever: accounts with static passwords, broad rights or passwordless sudo are marked as accepted risk at go-live and never revisited.
  • Substituting a lookalike: a CIS STIG profile or community profile is used where the contract requires the DISA STIG itself.

Practitioner checklist

  • List every applicable STIG (and SRG where no STIG exists) per system, with the version and release you commit to.
  • Download STIGs, SCAP benchmarks, STIG Viewer and SCC from DISA and verify checksums.
  • Build STIG settings into images and configuration code, not by hand on running systems.
  • Test in a non-production ring with application owners, focusing on FIPS, TLS, smart card and service account rules.
  • Combine SCAP results with manual reviews in one checklist per asset and STIG, leaving no rule Not Reviewed.
  • Key exceptions by Vulnerability ID, record mitigation, approver and expiry, and link open items to the POA&M.
  • Give service, scanner and automation accounts dedicated, vaulted credentials and review their rights against STIG user rights rules.
  • Review each quarterly release, update automation and checklists, and report open CAT I findings, checklist completeness and release currency.

Standards and references

Related NHI Mgmt Group resources: Linux Server Hardening Guide · Windows Server Hardening Guide · SCAP and Security Content Automation Guide · FedRAMP Guide · CIS Benchmarks Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.