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.
3
artefacts
0
held by a system
3
at each review
hard
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Review and approval process for content published publicly · Identity provider / directory
- Designated reviewer authorizations and review records · Identity provider / directory
- Evidence of periodic scanning of public sites for CUI · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
none for this control
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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