Getting Started with Cloud Security Command Center
How to use Cloud Security Scanner - 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 1 of 5
In this collection Browse 5 summaries 1 of 5
Web Security Scanner tests a running application for common vulnerabilities by following links and exercising inputs. This 2019 walkthrough shows how to schedule a scan and investigate its results in Security Command Center (SCC).
Key Points Covered
- Create a scan configuration before running it: The presenter selects an application URL, saves a weekly schedule, and opens the configuration page, where scan history and run, edit, and delete controls were available 00:50(opens in a new tab).
- Execution can be slow and scope-dependent: A configured scan enters a queue, then explores links and exercises inputs and event handlers; application complexity, links, JavaScript, actionable elements, and service load can extend runtime 00:50–01:49(opens in a new tab).
- Scanner results and SCC findings are distinct views: After execution, the scanner shows its own results page. Separately, enabled scanner data appeared as Security Command Center findings on the scanner card and organization findings view 01:49–02:41(opens in a new tab).
- Use finding details to reproduce the problem: The example opens a cross-site-scripting finding with information for locating and reproducing the issue. The scanner also shows a result page for an application with no detected vulnerabilities; that is not proof the application is vulnerability-free 01:49–03:21(opens in a new tab).
Full video: https://www.youtube.com/watch?v=goJ_G2ygdSA(opens in a new tab)