AC.L2-3.1.22 Control Public Information
Control CUI that is posted to or processed on publicly accessible systems so CUI is not released to the public.
Source: CMMC 2.0, AC.L2-3.1.22. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Evidence of periodic scanning of public sites for CUI · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Designated reviewer authorizations and review records · Identity provider / directory
governing documentDocuments that govern the control
- Review and approval process for content published publicly · Policy repository / GRC workspace
First move
Common gaps auditors find
- Publication approval informal or undocumented
- No periodic check of already published content
- Public facing systems not identified as in scope
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetAC.L2-3.1.21 Portable Storage Use · AT.L2-3.2.1 Role-Based Risk Awareness