Getting Started with Cloud Security Command Center
How to use Cloud DLP - Getting Started with Cloud Security Command Center
Five historical walkthroughs of scanning, detection, data protection, and security posture
Five 2019 walkthroughs show how vulnerability scans, anomalous activity, sensitive-data findings, and configuration checks lead to investigation and remediation. A finding signals something to investigate, not proof of a breach.
Google Cloud Tech 4 of 5
In this collection Browse 5 summaries 4 of 5
Cloud Data Loss Prevention (DLP) scans stored data for sensitive information such as credit-card numbers. This 2019 walkthrough sends those results to Security Command Center (SCC), where a finding links back to the storage resource for investigation.
Key Points Covered
- Choose what sensitive data to look for: An information type, or “info type,” is a category such as a name, email address, or credit-card number. DLP uses these categories to define what a scan looks for 02:39–03:27(opens in a new tab).
- The SCC integration required separate setup: The demo enables the DLP API and named IAM roles for a repository project in the same organization, then enables DLP Data Discovery as an SCC security source 00:55–02:39(opens in a new tab).
- Trace a match to the affected data: Once the integration is enabled, DLP findings appear on the SCC dashboard. The presenter follows a credit-card finding to its bucket and source link, then proposes further BigQuery analysis or contacting the owner to remediate it. A match identifies potentially sensitive data, not by itself a policy violation 02:39–04:02(opens in a new tab).
Full video: https://www.youtube.com/watch?v=ra_hnxqBzOc(opens in a new tab)