First, what this is and is not. It is not a decision, an announcement, a memorandum or a rule. It is the task force’s own written summary of what industry told it, together with options grouped by feasibility, produced in early September and obtained by a news organization. The Department declined to comment on fifteen questions put to it about the contents. Nothing on the list has been adopted, and the public recommendations still have no release date. Read it the way you would read a draft board paper that leaked: not as policy, but as the clearest available picture of which way policy is being pushed.
The structure is the useful part. The summary separates the options into three groups by authority. The first group is what the Chief Information Officer could do without any rulemaking at all: reduce the ambiguity created by assessors, prime contractors and program offices interpreting the same requirements differently; move the program to Revision 3 of NIST SP 800-171, a transition that has been on hold since the current Chief Information Officer took office in December; and improve the consistency of CUI marking. The second group is slower, costlier, or needs rulemaking: extend plan-of-action-and-milestones deadlines, publish templates and configuration settings so that testing is easier, and deal with the overlap between these requirements and other regimes such as ISO 27001. The third group is outside the Department’s gift entirely — grants, subsidies and tax credits, which it could advocate for but cannot create.
- Within 90 daysRestart Phase 2 with a narrower population while longer-term work goes through rulemaking. Work with the accreditation body and the training arm on more consistent guidance for assessors and consultants. Publish assessor availability statistics.
- 6 to 12 monthsIssue explicit guidance on crediting comparable ISO 27001 requirements. Reduce the volume of CUI the government sends to primes and subcontractors in the first place.
- A year or morePublish approved configurations and templates on the model of the Department’s hardening guides. Develop machine-readable evidence criteria using OSCAL. Offer free tools, subject to funding.
- Through rulemakingExpand plan-of-action-and-milestones eligibility to 270 days, described in the summary as part of an amendment already in process.
Now the phrase that will be quoted out of context for the next six months. On the forthcoming FAR rule for controlled unclassified information, the summary says the existing draft “has the potential to drastically reduce the burden on industry” by “narrowing the population that must comply with NIST 800-171,” and that improving the clarity of CUI marking has “the greatest potential to narrow the DIB population subject to NIST 800-171 implementation.”
Read the mechanism rather than the adjective. The lever being described is marking — the government being more precise about what it hands you and what it calls controlled. A company leaves that population when the government stops designating its data as CUI, which is the fix industry has asked for since the program began and which this brief has covered as the single most-cited friction in the response record. It is not a lever that reduces what you owe if you do hold controlled information. And two items on the list move in the other direction: taking the Revision 3 transition off hold raises the baseline, and machine-readable evidence criteria raise what counts as having demonstrated it.
The response data does not say what the pause said it said. Asked what costs the most, industry named the system security plan.
Part one of the same investigation, published October 26, works through the response data itself. The Department reviewed 997 responses. Just over half — 509 — came from defense industrial base companies; the rest came from vendors, consultants and others. The suspension in July was announced on two grounds: a shortage of third-party assessors, and compliance costs that were structurally incompatible with small business. The responses speak to both grounds, and not in the direction the announcement implied.
| The stated reason | What the response data shows | What it means for you |
|---|---|---|
| Assessor capacity was the binding constraint | Around 47% of respondents cited assessor cost — fifth among cost drivers, not first. Capacity was reportedly never more than half used during Phase 1, and 2,433 companies held Level 2 certificates by September, roughly five times the Department’s own first-year projection. Average assessment: about $47,000. | Treat the queue as available, not full. Capacity is not what will stop you, and the much larger cost figures in circulation do not come from this data set. |
| Certification cost is what is crushing small business | The top cost driver named was implementing and maintaining the NIST SP 800-171 controls themselves — not the certification wrapped around them. Licensing, enclaves and inconsistent CUI marking followed. On overhead, respondents ranked system security plans highest and FIPS-validated encryption second. | Your cost problem is the controls and the documentation. Neither a pause on verification nor a restart touches either one. |
| A 75-day review would settle it | Sixty days for feedback plus fifteen to write the report, now past a hundred days. Roughly twenty people worked through more than 1,100 comments in three days, largely by hand. The 2024 rulemaking took about eight months for roughly 1,400 comments. | The delay is a throughput problem, not a signal that the obligation is being withdrawn. Do not read slowness as softening. |
On whether the self-assessment regime does any good, the data is genuinely mixed and should be quoted carefully: 58% of those who answered said self-assessments improved their cybersecurity, and 43% called them a check-the-box exercise — but fewer than a fifth of respondents answered that question at all, so both figures are a minority view rather than a referendum. What respondents did not say, anywhere in the summary, is that the program’s burden was too high.
Eric Crusius of Hunton made the point that organizes all of this: the cost complaints are aimed at the certification program when what they actually describe is the underlying NIST requirements, which the certification program does not change. The reporting also notes that the current Chief Information Officer had met the program office for roughly twenty minutes since her confirmation in December, and that the program office was not consulted before the suspension — which is relevant here only for what it says about durability. An arrangement built without the people who run the thing is not the arrangement most likely to last.
NIST spent an hour last Thursday on how a requirement is scored. One rule in the slides explains how a self-scored 110 becomes a negative number.
On October 29, Victoria Pillitteri, a co-author of NIST SP 800-171, and Daniel Eliot, who leads NIST’s small business engagement, spent an hour walking through the assessment side of the standard. This brief covered the publication of their small-business primer in September; the webinar is where the mechanics got explained, and the slides are now public. They are worth an afternoon, because they describe the arithmetic that decides whether you are compliant, and it is not the arithmetic most self-assessors use.
A requirement is not scored as a requirement. It decomposes into assessment objectives — evaluation statements that break the requirement into separately testable parts. Each objective is examined, asked about, or tested, and not every method applies to every objective. Each one comes back either satisfied or other than satisfied. Then comes the rule that does all the work, stated plainly in the deck: every objective is binary, and if any single objective is not met, the entire requirement is Not Met. There is no partial credit at the requirement level.
That is why a requirement you are confident you meet in substance can fail on one line — the log retention period nobody set, the shared account nobody disabled, the procedure that exists but was never approved. And Revision 3 adds a second trap. It introduced organization-defined parameters, and the slides show, using device lock as the worked example, that the parameters are themselves assessment objectives. The organization has to have selected its own values — how long a device sits idle before it locks — before the remaining objectives can be assessed at all. A company that never wrote the number down has not implemented the requirement loosely. It has failed an objective, and the whole requirement with it.
The rest of the deck is process, and one line in it is aimed at owners rather than engineers. The four phases are prepare — scope the assessment and gather the artifacts: plan of action, system security plan, network diagrams, policies — then develop the assessment plan, conduct it, and document and report. An external assessor normally writes that plan, and the slides tell business leaders to read it before it runs, for scope and for business disruption. Afterwards: one plan-of-action entry per Not Met requirement with corrective actions, resources and target dates; update the system security plan to the system as implemented; report the score; monitor continuously.
What to do this week
Every option on the reform list assumes you already hold these.
- Read your system security plan against the system you actually run. It has to describe the environment as implemented.
- Decompose your five highest-value requirements into assessment objectives, and give every organization-defined parameter a written value. One objective other than satisfied fails the whole requirement.
- Read Revision 3 now. Taking the transition off hold needs no rulemaking.
Quick hits
- Late Oct 2026The assessment queue turned back up while the program requiring it is still suspended.A practitioner recap of the October accreditation-body town hall reports final Level 2 certificates up 8% since September and 184 Level 2 assessments in progress; the body has not published its own October figures, so treat these as indicative. The number worth noticing is 184. The in-progress queue stood at 151 at the end of September and had been falling for months, which read as a backlog draining. It is now rising — companies are booking third-party assessments they are not currently required to hold, during a suspension, with no restart date announced.
- OngoingThere is a no-cost federal platform that builds the two documents this issue is about.Project Spectrum has been run by the Department’s Office of Small Business Programs since December 2019, and under Section 1807 of the FY2026 defense authorization act maintaining it is now a statutory obligation rather than a discretionary program. Registered small and medium businesses get cyber readiness checks, risk and vulnerability assessment, continuous threat monitoring, system security plan development and plan-of-action tooling. A current Department contract is not required — firms pursuing contracts, subcontracts or grants qualify, and 21,535 companies were participating as of the most recent published count. It lowers the cost of producing the artifacts; it does not sign your affirmation.
Not sure where your organization stands?
CUI Vault gives you a live, always-audit-ready picture of your CUI environment and NIST 800-171 posture — so headlines like today’s are a footnote, not a fire drill. Reach out to your NtelSec team to talk through your current gaps.

