Getting Started with Cloud Security Command Center
Getting Started with Security Health Analytics
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 5 of 5
In this collection Browse 5 summaries 5 of 5
Security Health Analytics looks for risky cloud configuration, such as publicly accessible storage or missing security logging. This 2019 walkthrough shows how a finding identifies the affected resource and recommends a change, using a Cloud SQL database without a root-user password as the example.
Key Points Covered
- The scanner looked for configuration weaknesses: Examples included publicly accessible buckets, open firewall ports, public IP addresses, stale keys, and disabled security logging across compute, container, network, storage, and IAM resources 00:04–01:09(opens in a new tab).
- Findings supported filtering and triage: The dashboard exposed finding and source filters plus the affected asset, severity, first and latest observation times, source URI, and recommendation 01:09–02:13(opens in a new tab).
- The finding points to a fix; it does not apply it: The presenter opens the no-root-password recommendation, follows its link to the Cloud SQL instance, and adds a root-user password there. The demonstrated change happens on the resource, not automatically in the findings dashboard 02:13–02:49(opens in a new tab).
Full video: https://www.youtube.com/watch?v=L5nR0KPtn-Y(opens in a new tab)