3.1.22Review what goes on public sites in Rev. 3

Reworded: 03.01.22 Publicly Accessible Content.

Status as of 2026-09-08

Rev. 2 is what a contract requires today. DFARS 252.204-7012 and the CMMC rule at 32 CFR 170 point at NIST SP 800-171 Rev. 2, and a standing DoD class deviation keeps it there. NIST has published Rev. 3, but publishing a revision does not change an obligation. A move to Rev. 3 would arrive through the Department's reform process and formal rulemaking, a change to that deviation or an amendment to the rule, not through publication. The Department has published its organization-defined parameter values for Rev. 3 in preparation; that is groundwork, not adoption.

Side by side

Rev. 2 · in force 3.1.22 Control Public Information

Control CUI posted or processed on publicly accessible systems.

Assessment objectives · 800-171A

[a] individuals authorized to post or process information on publicly accessible systems are identified
[b] procedures to ensure CUI is not posted or processed on publicly accessible systems are identified
[c] a review process is in place prior to posting of any content to publicly accessible systems
[d] content on publicly accessible systems is reviewed to ensure that it does not include CUI

Rev. 3 · not adopted 03.01.22 Publicly Accessible Content

a. Train authorized individuals to ensure that publicly accessible information does not contain CUI.

b. Review the content on publicly accessible systems for CUI and remove such information, if discovered.

Determination statements · 800-171A Rev. 3

03.01.22.a authorized individuals are trained to ensure that publicly accessible information does not contain CUI.
03.01.22.b[01] the content on publicly accessible systems is reviewed for CUI.
03.01.22.b[02] CUI is removed from publicly accessible systems, if discovered.

Draws on Rev. 2 3.1.22.

Left: NIST SP 800-171 Rev. 2 and 800-171A, verbatim. Right: NIST SP 800-171 Rev. 3 and 800-171A Rev. 3, verbatim, with organization-defined blanks highlighted.

Word by word

The Rev. 2 requirement compared with its Rev. 3 successor. A mechanical comparison of the two verbatim texts, not an interpretation.

~~removed in Rev. 3~~ added in Rev. 3

Rev. 2 3.1.22 → Rev. 3 03.01.22 Publicly Accessible Content

~~Control~~ Train authorized individuals to ensure that publicly accessible information does not contain CUI. ~~posted or processed~~ Review the content on publicly accessible systems for CUI and remove such information, if discovered.

5 words kept, 4 removed, 23 added. Rev. 3 statement labels omitted for the comparison.

What NIST says changed

New security requirement title
Aligned with SP 800-53, Rev 5 to provide more comprehensive detail on and foundational tasks to manage publicly accessible content

NIST, SP 800-171 Rev. 2 to Rev. 3 change analysis, class “Significant change”. At adoption, Bedrock files this under “Rework”.

NIST's Rev. 3 discussion for 03.01.22

In accordance with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidelines, the public is not authorized to have access to nonpublic information, including CUI.

What this means for you now

Nothing changes in what you are assessed against until a class deviation or a published rule adopts Rev. 3. Keep meeting 3.1.22 as written in Rev. 2.

Bedrock CMMC shows this same comparison against your own package, with your current status on the Rev. 2 side, so the day adoption lands the migration is a review, not a rewrite.

Back to the Rev. 2 vs Rev. 3 overview

Where this page's facts come from

Rev. 2 text and objectives: bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.basicRequirement@rev2; bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2
Mapping and change class: bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/r2_r3_transition_map.json#r2_to_r3
Rev. 3 03.01.22: bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]