Make sure CUI only moves to places it's allowed to go.
What it actually means
Information-flow control means CUI moves only along approved paths. In practice that means restricting where CUI can be sent or copied — blocking it from personal email, unapproved cloud storage, or USB — and enforcing those rules with boundary controls, DLP, or tenant restrictions. The point is that the movement of CUI is governed by policy, not left to chance.
Pass or fail — an assessor needs a "yes" to each
- Are there rules defining where CUI may and may not flow (email, cloud, removable media)?
- Are those rules enforced technically, not just written on paper?
What to have ready
- Information-flow / DLP policy
- Configuration enforcing flow restrictions (tenant rules, DLP, firewall)
Where teams trip up
- CUI freely copyable to personal email or consumer cloud
- Flow rules written down but never enforced
See where this control puts your score
Run all 110 requirements free in about 10 minutes — or draft your SSP language for this control. No signup.
Calculate your SPRS score →Draft your SSP language →Connected requirements
More in Access Control (3.1)
3.1.1 — Limit who (and what) can get in3.1.2 — Limit what users can do3.1.4 — Separate duties3.1.5 — Least privilege (especially for admins)3.1.6 — Use non-privileged accounts for routine work3.1.7 — Restrict and log privileged functions3.1.8 — Limit failed logons3.1.9 — Show privacy and security notices3.1.10 — Lock idle screens3.1.11 — End sessions automatically3.1.12 — Monitor and control remote access3.1.13 — Encrypt remote access sessions3.1.14 — Funnel remote access through managed points3.1.15 — Authorize privileged remote actions3.1.16 — Authorize wireless access first3.1.17 — Protect wireless with authentication + encryption3.1.18 — Control mobile device connections3.1.19 — Encrypt CUI on mobile devices3.1.20 — Control connections to external systems3.1.21 — Limit portable storage on external systems3.1.22 — Control what goes on public systems