- Name the individuals authorized to publish publicly and give them the review step: content checked for CUI before posting, with the check recorded.
- Sweep existing public content on a cadence — website, social accounts, published case studies — and record the sweep even when it finds nothing.
3.1.22OFFICIAL STATEMENT BELOWDERIVED REQUIREMENTPENDING NIST SME REVIEW
3.1.22 — Publicly accessible content control
3.1 Access Control · NIST SP 800-171 Rev. 2 · The heading label is this site's navigational shorthand; the official language is the statement below.
Official requirement statement (verbatim)
Control CUI posted or processed on publicly accessible systems.
NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A — Assessing Security Requirements for CUI ↗Independent interpretation
What this requirement is after
Nothing controlled reaches your public website, social media, or marketing material. A small set of named people are authorized to post publicly, someone checks content for CUI before it goes out, and the already-public footprint gets swept periodically — because the photo of the shop floor with a drawing on the bench is how this actually fails.
Mapped practices
Brilliant at the Basics practices that support this requirement
No practice maps to this requirement — deliberately.
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Doing the work
Implementation considerations and evidence
- The list of personnel authorized to post public content
- Pre-publication review records and periodic sweep records with dates and outcomes
Artifacts
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
The other revision
Where this lands in Rev. 3
Provenance
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |