AC.L2-3.1.3 Control CUI Flow
Enforce approved authorization rules on the movement of CUI between systems, components and destinations, so CUI flows only where policy permits.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Records of blocked or exception-approved transfers · Identity provider / directory
governing documentDocuments that govern the control
- Documented CUI flow authorizations and approved flow paths · Policy repository / GRC workspace
- Firewall, proxy, DLP or gateway rules enforcing those flows · Policy repository / GRC workspace
- Data flow diagrams identifying CUI sources, stores and destinations · Policy repository / GRC workspace
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
- CUI flows documented but not technically enforced
- Egress to cloud and email paths unmonitored for CUI
- No defined authorization for flows to external partners
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.2 Transaction & Function Control · AC.L2-3.1.4 Separation of Duties