Protect CUI and achieve NIST 800-171 compliance faster
Evidr automates control mapping, SPRS score calculation, and System Security Plan generation for defense contractors. Meet DFARS requirements and prepare for CMMC with AI-powered compliance automation.
- 110
- Security controls
- 14
- Control families
- 8-12
- Weeks to compliance
- SPRS
- Score tracking
Inside the product
NIST 800-171 in the console, control by control.

NIST 800-171
Fourteen control families
110 requirements for protecting Controlled Unclassified Information.
- 3.1Access Control22
- 3.2Awareness and Training3
- 3.3Audit and Accountability9
- 3.4Configuration Management9
- 3.5Identification and Authentication11
- 3.6Incident Response3
- 3.7Maintenance6
- 3.8Media Protection9
- 3.9Personnel Security2
- 3.10Physical Protection6
- 3.11Risk Assessment3
- 3.12Security Assessment4
- 3.13System and Communications Protection16
- 3.14System and Information Integrity7
NIST 800-171
How the SPRS score works
A 110-point scale, with points deducted per unmet requirement by weight.
- 22 pointsAccess Control
Authentication, authorization, and session controls
- 16 pointsSystem Protection
Network security, encryption, and boundary protection
- 11 pointsIdentification
User identification and multi-factor authentication
- 61 pointsOther Families
Remaining 10 control families
What Evidr does
Everything NIST 800-171 asks for, handled.
- 110 Control MappingEvidr automatically maps your existing security controls to all 110 NIST 800-171 requirements across 14 control families. See exactly where you stand.
- SPRS Score CalculatorReal-time SPRS score calculation based on your implemented controls. Track your score as you remediate gaps and prepare for DoD submission.
- CUI Boundary DocumentationDocument your Controlled Unclassified Information boundary, data flows, and system interconnections. Essential for compliance scoping.
- System Security Plan GenerationGenerate NIST 800-171 compliant SSP documentation with AI assistance. Control implementation descriptions, policies, and procedures.
- POA&M TrackingManage Plans of Action and Milestones for controls not yet fully implemented. Track remediation progress and milestone deadlines.
- CMMC 2.0 ReadinessNIST 800-171 forms the foundation of CMMC Level 2. Compliance positions you for future CMMC certification requirements.
The path
NIST 800-171 readiness, step by step.
- Step 1 of 5Week 1-2CUI Scoping & Boundary Definition
Identify where CUI is stored, processed, and transmitted. Document your system boundary and data flows. This scoping determines which controls apply.
- Step 2 of 5Week 2-4Gap Assessment
Evidr maps your existing controls to NIST 800-171 requirements. Generate initial SPRS score and identify control gaps across all 14 families.
- Step 3 of 5Week 4-10Control Implementation
Address control gaps with guided remediation workflows. Implement technical controls, generate policies, and document procedures.
- Step 4 of 5Week 10-12SSP & POA&M Documentation
Generate System Security Plan documenting all control implementations. Create POA&Ms for any controls not fully implemented with remediation timelines.
- Step 5 of 5Week 14SPRS Submission
Calculate final SPRS score based on implemented controls. Submit assessment results to SPRS database. Prepare for potential DCMA audits.
NIST 800-171 FAQ
NIST 800-171, answered.
Anything we have not answered here, ask us directly.
Contact usWhat is NIST 800-171?
NIST Special Publication 800-171 "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations" defines security requirements for contractors and other organizations that handle Controlled Unclassified Information (CUI). It contains 110 security controls organized into 14 families, derived from NIST 800-53 but tailored for non-federal systems.
Who needs to comply with NIST 800-171?
Any organization that handles Controlled Unclassified Information (CUI) as part of a federal contract must comply with NIST 800-171. This primarily affects defense contractors, subcontractors, and suppliers in the Defense Industrial Base (DIB) subject to DFARS clause 252.204-7012. The requirement flows down to all tiers of the supply chain that handle CUI.
What is Controlled Unclassified Information (CUI)?
CUI is information that requires safeguarding or dissemination controls pursuant to federal law, regulations, or government-wide policies, but is not classified. In defense contracting, CUI often includes technical data, engineering drawings, manufacturing specifications, and other sensitive but unclassified information marked as CUI or with legacy markings like FOUO, SBU, or LES.
What is SPRS and how does it work?
SPRS (Supplier Performance Risk System) is the DoD database where contractors must submit their NIST 800-171 self-assessment scores. Contractors calculate their score by starting with 110 points (full compliance) and subtracting weighted values for each unimplemented control. Scores must be submitted before contract award and updated when compliance status changes.
How is the SPRS score calculated?
SPRS scores start at 110 (fully compliant) and subtract points for each unimplemented control. Controls are weighted by risk: 5 points (highest risk), 3 points (medium), or 1 point (lower risk). For example, not implementing multi-factor authentication (5 points) has greater impact than missing a training procedure (1 point). The minimum possible score is -203.
What is the difference between NIST 800-171 and CMMC?
NIST 800-171 is a set of security requirements that contractors self-attest to meeting. CMMC (Cybersecurity Maturity Model Certification) adds third-party assessment and certification. CMMC Level 2 is directly based on NIST 800-171's 110 controls. Organizations compliant with 800-171 are positioned for CMMC Level 2 when certification becomes required.
What is a System Security Plan (SSP)?
The SSP is a required document that describes your system boundary, how CUI is protected, and how each NIST 800-171 control is implemented. It serves as the primary documentation for compliance. Evidr generates SSPs automatically based on your control implementations, including boundary diagrams, control descriptions, and interconnection details.
What is a POA&M?
A Plan of Action and Milestones (POA&M) documents security weaknesses (controls not yet fully implemented), planned remediation activities, and target completion dates. POA&Ms are required when you cannot fully implement all 110 controls. They must include specific milestones, resources, and completion dates for each identified gap.
Related