CM-12 Information Location. Identify and document the location of [organization-defined] and the specific system components on which the information is processed and stored; Identify and document the users who have access to the system and
Information Location. Identify and document the location of [organization-defined] and the specific system components on which the information is processed and stored; Identify and document the users who have access to t.
5
artefacts
1
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
- Change records showing the location documentation was updated when components changed · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence the documented location was verified against the live estate rather than asserted · Cloud console / configuration management
governing documentDocuments that govern the control
- Documented location of the defined information, naming the specific system components that process and store it · Policy repository / GRC workspace
- List of users with access to each component holding that information · Policy repository / GRC workspace
- Data mapping or inventory documentation, including personally identifiable information where held · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Primary store documented while backups, caches, log stores and analytics copies are not
- Inventory built once at accreditation and never reconciled after migration or scaling
- User access list maintained per application rather than per component, so component level access is unknown
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 sheetCM-11 User-installed software · CM-13 Data Action Mapping. Develop and document a map of system data actions