Home/Refreshers/Notice data walking out the door: refresher
Notice data walking out the door
Alerts on the moves someone makes on the way out with data: sharing it outside, reading far more than usual, changing who can decrypt it, and quieting the logs.
Remember
- Someone with access acts: shares, reads, grants, or turns logging down.
- The audit log records it: admin actions always, object reads where turned on.
- A filter or rule matches: per action, or per person for bulk reads.
- An alert names what happened: and a saved query shows the rest.
| Platform | Uses | The part that catches people |
|---|---|---|
| AWS | CloudWatch metric filters on the audit trail, and Contributor Insights on object reads | The management trail does not record object reads, so bulk downloads are invisible without data events. |
| Google Cloud | An organisation log sink, log-based metrics, and per-principal alerting on Data Access logs | Log-based metrics only count entries in their own project. |
| Azure | The subscription's activity log in Log Analytics, with scheduled query alerts and per-caller bulk-read alerting on blob logs | A storage key or a SAS made from it works for whoever has it, with no identity behind it, and nothing short of rotating the key revokes it. |
| Oracle Cloud | The Audit service counted into metrics by caller, with alarms, and Object Storage read logs for bulk reads | Audit event names are the API operations' own names, and the connectors match them exactly. |
Run the quick start
| Download providers | terraform init |
| Preview | terraform plan |
| Apply | terraform apply |
Watch out
- Alerts start an inquiry.
- Tune before you trust.
- The data perimeter template refuses copies to outside accounts.
Check it worked
In a test account or project, share a test bucket outside and then undo it. The sharing alert reaches the security inbox within minutes.