03.04.11 Information Location
Identify and document the location of CUI and the system components on which it is processed and stored.
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- CUI data flow diagrams · Policy repository / GRC workspace
- Data classification inventory · Policy repository / GRC workspace
- System boundary diagrams · Document repository
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 sprawled to shadow IT
- no recent mapping
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 sheet03.04.10 System Component Inventory · 03.04.12 System and Component Configuration for High-Risk Areas