---
title: "NIST 800-171 3.1.22 (AC.L2-3.1.22): Public Information"
description: "NIST SP 800-171 3.1.22 Public Information: 1 SPRS point, never on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/access-control/3.1.22
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.22
records: 7
digest: sha3:f48578e487c974a69103a127128e17f9fdffb3212a2e99decd06383c3f774a22
---

# NIST 800-171 3.1.22 (AC.L2-3.1.22): Public Information

NIST 800-171 / Access Control / 3.1.22

"Control CUI posted or processed on publicly accessible systems." ([NIST SP 800-171 Rev. 2, requirement 3.1.22](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.22.

## What 3.1.22 means in practice

Websites, social media and public repositories must never carry CUI. Name the people allowed to publish, review content before it goes out, check what is already public, and keep a way to pull anything that slips through.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: AC.L2-3.1.22
- **SPRS points**: 1 point. When it is not met, the DoD Assessment Methodology subtracts 1 from the score of 110.
- **CMMC POA&M**: Never. 32 CFR 170.21(a)(2)(iii) names 3.1.22 among the 6 requirements a CMMC POA&M may never include, whatever their point value.

Sources: [NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## What an assessor checks for 3.1.22

NIST SP 800-171A gives 5 determination statements for 3.1.22, each found satisfied or other than satisfied. Determine if:

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

[NIST SP 800-171A (June 2018), assessment objectives for 3.1.22](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.1.22 is met

- A list of the people authorized to post to public systems.
- The review procedure for content before publication, and records of those reviews.
- Periodic reviews of public content for CUI.
- The procedure for removing CUI that was posted by mistake.

## How PolicyCortex gathers the evidence

No PolicyCortex collector reads the evidence for 3.1.22. Your team provides the evidence listed above.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.22 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-AC)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 22 Access Control requirements (3.1).](https://policycortex.com/nist-800-171/access-control)
- **Previous**: [3.1.21: Portable Storage Use](https://policycortex.com/nist-800-171/access-control/3.1.21)
- **Next**: [3.2.1: Security Awareness](https://policycortex.com/nist-800-171/awareness-and-training/3.2.1)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | 091991d0fe08 | be076da9fb86 |
| REC 0001 | MEANING | ed4d456fba85 | 091991d0fe08 |
| REC 0002 | POINTS AND POA&M | f0df83d6c924 | ed4d456fba85 |
| REC 0003 | ASSESSMENT OBJECTIVES | 74cd33ef8046 | f0df83d6c924 |
| REC 0004 | EVIDENCE | 85df51abc6dc | 74cd33ef8046 |
| REC 0005 | COLLECTORS | 548f889e03b1 | 85df51abc6dc |
| REC 0006 | RELATED | f48578e487c9 | 548f889e03b1 |

Head sha3:f48578e487c974a69103a127128e17f9fdffb3212a2e99decd06383c3f774a22. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.