United States

NIST SP 800-172

35 controls. 20 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

35 controls 20 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

NIST SP 800-172 Enhanced CUI Protection Evidence & Implementation Kit

35 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
3.1.1eDual Authorization for Sensitive System Operations17
3.1.2eRestrict Access to Organization-Owned, Provisioned, or Issued Information Resources16
3.1.3eEmploy Secure Information Transfer Solutions18
3.11.1eThreat-Aware Risk Assessment19
3.11.2eThreat Hunting15
3.11.3eAdvanced Automation and Analytics Capabilities16
3.11.4eSecurity Solution Rationale Document15
3.11.5eAssess Effectiveness of Security Solutions20
3.11.6eSupply Chain Risk Assessment, Response, and Monitoring17
3.11.7eSupply Chain Risk Management Plan16
3.12.1ePenetration Testing by Independent Agents19
3.13.1eCreate Diversity in System Components to Limit Malicious Code Propagation15
3.13.2eIntroduce Unpredictability into System Operations19
3.13.3eConfuse and Mislead Adversaries8
3.13.4ePhysical and Logical Isolation Techniques7
3.13.5eDistribute and Relocate System Functions or Resources3
3.14.1eVerify Integrity of Security Critical Software and Firmware17
3.14.2eMonitor Organizational Systems with Specialized Capabilities18
3.14.3eInclude Systems in Scope of Enhanced Requirements or Segregate into Purpose-Specific Networks17
3.14.4eRefresh Systems and Components from a Trusted Baseline16
3.14.5eReview Persistent Storage and Remove CUI No Longer Needed17
3.14.6eUse Threat Indicator Information for Detection16
3.14.7eVerify Correctness of Security Functions17
3.2.1eProvide Awareness Training on Advanced Persistent Threat19
3.2.2ePractical Exercises in Awareness Training16
3.4.1eAuthoritative Source for Software and Firmware16
3.4.2eAutomated Detection and Remediation of Unauthorized Software19
3.4.3eAutomated Inventory of System Components16
3.5.1eIdentification of Systems, Components, and Devices18
3.5.2ePassword Manager Use17
3.5.3eProhibit Connection of Unknown or Unverified System Components18
3.6.1eEstablish Security Operations Center (SOC)17
3.6.2eEstablish and Maintain a Cyber Incident Response Team19
3.9.1eEnhanced Personnel Screening15
3.9.2eInsider Threat Program13

Tell me when NIST SP 800-172 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • APT-specific training curriculum
  • training completion records
  • phishing simulation results
  • supply chain attack scenarios used in training
  • Wolfsberg questionnaires
  • Respondent AML programme reviews
  • asset discovery scan logs
  • CMDB sync reports
  • reconciliation reports between discovery and CMDB
  • agent coverage metrics

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for NIST SP 800-172, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition