NIST SP 800-171 for a small defense subcontractor: what it asks and where to start
If you build parts, write software or provide services for a company that works on U.S. Department of Defense contracts, sooner or later someone will ask: "Are you NIST 800-171 compliant?" For a small business that question can feel enormous. It is large, but it is also well defined. This article explains what is being asked, why, and a practical order to start in. It is general information, not legal advice: your contract's clauses decide what applies to you.
What it is
NIST Special Publication 800-171 is a set of security requirements for protecting Controlled Unclassified Information (CUI) on systems that are not run by the government. CUI is information the government creates or owns that needs protection but is not classified: technical drawings, specifications, some contract details and similar material.
Defense contracts bring these requirements in through clauses in the Defense Federal Acquisition Regulation Supplement (DFARS). DFARS 252.204-7012 requires contractors that handle covered defense information to protect it with NIST SP 800-171 and to report cyber incidents. The Cybersecurity Maturity Model Certification (CMMC) program adds checks that a company really does what it says; its Level 2 is built on the same 110 requirements of NIST SP 800-171 Revision 2.
NIST published Revision 3 in 2024. As of this writing, defense contracts and the CMMC rule still point to Revision 2, so that is the version most subcontractors are measured against today. The CMMC rollout schedule has also changed during 2026, so check the current dates on the Department of Defense CIO's CMMC page before you plan around them.
The first question: do you actually handle CUI?
Everything depends on this. If you never receive, store or send CUI, many of these requirements may not apply to your systems at all. If you do, the requirements apply to every system that touches it.
Ask your prime contractor which documents they will send you are CUI, and how they will be marked. Then follow where those files go: which laptops, which email accounts, which file shares, which backups.
Shrink the boundary first
The cheapest way to comply is to keep CUI in as few places as possible. Many small companies set up one separate, locked-down environment (an "enclave") just for CUI work, instead of trying to bring the whole office up to the standard. Fewer systems means fewer requirements to prove and less to maintain.
The 14 families, in plain words
The 110 requirements in Revision 2 are grouped into 14 families:
- Access control: only the right people reach CUI, and only what they need.
- Awareness and training: people know the risks and their duties.
- Audit and accountability: systems keep logs, and someone reviews them.
- Configuration management: systems are set up the same, approved way, and changes are controlled.
- Identification and authentication: every user is identified; multi-factor sign-in where required.
- Incident response: a written plan for what to do and whom to tell when something goes wrong.
- Maintenance: repairs and remote maintenance are controlled.
- Media protection: USB drives, paper and backups holding CUI are protected and properly destroyed.
- Personnel security: people are screened, and access ends when they leave.
- Physical protection: the hardware is physically secured.
- Risk assessment: you look for weaknesses on a schedule and fix them.
- Security assessment: you check that your controls work, and track what is not done yet.
- System and communications protection: network boundaries, encryption, separation.
- System and information integrity: patches, malware protection, watching for attacks.
A practical order to start
- Find your CUI and draw the boundary (above).
- Write the System Security Plan (SSP). It describes the systems in scope and how each requirement is met. An honest SSP that says "not yet" is better than a polished one that is not true.
- Turn on the high-value basics: multi-factor sign-in, encryption of devices and backups, automatic updates, and logs that are kept and read.
- Score yourself. The Defense Department uses a self-assessment scoring method for these 110 requirements, and many contracts require the score to be posted in the Supplier Performance Risk System (SPRS).
- Keep a Plan of Action and Milestones (POA&M) for everything that is not done yet, with dates and owners.
- Repeat on a schedule. Compliance is a habit, not a one-time project.
Mistakes we see most
- Claiming a score the systems do not support. A posted score is a statement to the government; it has to be true.
- Treating the whole company as in scope when a small enclave would do.
- Buying tools before writing down which requirement each tool meets.
- Leaving CUI in personal email or consumer file-sharing accounts.
The short version
Find out whether you handle CUI, keep it in the smallest possible space, write down honestly how you protect it, fix the basics first, and track the rest with dates. The requirements are long, but they are a known list, and a small company can work through them one family at a time.