OPS-11 Logging and Monitoring - Metadata Management Concept
Set documented rules for handling usage metadata that confine collection to billing, incident and security incident purposes, require anonymised data for operating and improving the service, forbid commercial use, fix a
4
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
- Metadata handling policy stating each permitted purpose and its retention clock · Policy repository / GRC workspace
- Data inventory classifying which usage attributes count as metadata · Policy repository / GRC workspace
- Anonymisation or aggregation specification applied before service improvement analytics · Policy repository / GRC workspace
- Contract clause governing provision of metadata to the cloud customer · 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
- Usage data reused for product analytics or marketing beyond the permitted purposes
- Anonymisation claimed while tenant or user identifiers remain in the data set
- No deletion trigger, so metadata accumulates for as long as storage allows
- Metadata shared with affiliated companies without a contractual basis
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 sheetOPS-10 Logging and Monitoring - Concept · OPS-12 Logging and Monitoring - Access, Storage and Deletion