Primary references
Use the original standards below to check terminology and requirements. These references explain the standards; they do not endorse CISGuard or independently verify its product coverage.
NIST 800-171 Compliance Automation
Use continuous CIS configuration evidence to support a NIST 800-171 assessment. Establish the applicable revision and your CUI boundary before selecting controls or calculating an assessment score.
Overview
NIST SP 800-171 addresses the protection of Controlled Unclassified Information in nonfederal systems and organizations. Revision 2 contains 110 requirements across 14 families. Revision 3 is a separate publication, issued in May 2024, with 17 families and revised requirements and organization-defined parameters. Official CMMC Level 2 guidance references Revision 2. Verify the edition and assessment obligations in your contract and current agency guidance; the latest NIST publication does not automatically replace a contractual baseline.
CISGuard collects configuration findings and scan history that can support technical requirements such as baseline management, access configuration and audit settings. Review the relationship between each finding and the applicable requirement with your assessor. Policies, training, personnel processes, system security plans and other evidence remain part of the wider assessment. Request a release-specific coverage demonstration rather than assuming that a benchmark scan covers every NIST 800-171 requirement.
Configuration evidence supports an assessment; it does not by itself establish certification, authorization or full compliance. Review coverage boundaries and evaluation evidence.
Control mapping
Each CIS control is tagged with its framework reference. One scan produces the per-framework coverage report, with satisfied, partially satisfied and not-met status for every control.
| Control area | Controls | Mapped by |
|---|---|---|
| 3.1 (Access Control) | 22 requirements (least privilege, separation of duties, MFA) | CIS Account + Identity benchmarks across AD, Entra, Linux |
| 3.3 (Audit and Accountability) | 9 requirements (audit log generation, retention, review) | CIS Audit Policy benchmarks + SIEM forwarding |
| 3.4 (Configuration Management) | 9 requirements (baseline configuration, change control) | Continuous CIS benchmark scanning + drift detection |
| 3.11 (Risk Assessment) | 3 requirements (vulnerability scanning, risk monitoring) | CIS Update / Patch benchmarks + drift detection |
| 3.13 (System and Communications Protection) | 16 requirements (boundary, cryptography, transmission) | CIS Cryptography + TLS + Firewall benchmarks |
| 3.14 (System and Information Integrity) | 7 requirements (flaw remediation, malware detection, monitoring) | CIS Endpoint hardening + integrity controls |
Auditor evidence
Auditor-grade outputs in PDF, HTML, JSON, CSV and SARIF. No spreadsheets, no screenshots, no manual cross-referencing.
Frequently asked
Official CMMC Level 2 guidance references the 110 requirements in Revision 2. Revision 3 is a separate NIST publication. Confirm the applicable baseline, current implementation guidance and your contract before planning an assessment.
No. A scan provides configuration evidence for a defined technical scope. An assessment also requires other evidence, including policies, procedures and people-related controls. The assessor determines whether the applicable requirements are satisfied.
Scan results can inform the review of technical requirements, but a scan result is not an SPRS score. Use the applicable official assessment methodology and assess all requirements in scope before submitting a score.
Confirm supported platforms, scan permissions, the release-specific mapping, evidence timestamps and limitations. Bring the applicable baseline and assessment scope so the engineer can show how the evidence relates to your environment.
On-premises and air-gapped deployment are supported. Confirm update procedures and the scan scope during deployment planning. Cloud-account assessments still require connectivity to the relevant provider APIs.
Use the original standards below to check terminology and requirements. These references explain the standards; they do not endorse CISGuard or independently verify its product coverage.
Our compliance engineers have helped organizations achieve regulatory readiness through a seamless, fully managed deployment.