Google Cloud Security Command Center
by Google
Google Cloud's security and risk management service; the API returns findings, assets, sources and security marks.
- Category
- IT, Security & Monitoring
- Type
- Cloud security
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0, Service account key
02Data
What you can sync.
- Findings
- Assets
- Sources
- Security marks
- Notification configs
Keep Google Cloud Security Command Center findings in your own Lake, on your servers, and report on it with the rest of IT.
Need more? Name any other Google Cloud Security Command Center data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
- A service account key
Google Cloud Security Command Center uses OAuth 2.0 (client ID, client secret, refresh token) or a service account key. You add the credentials once, when the AI asks for them, and it tells you where to create them in Google if you need help.
04How it works
How it works in DataMind.
-
Pick Google Cloud Security Command Center.
Open Lake, pick Google Cloud Security Command Center in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Google Cloud Security Command Center API docs.
-
Answer a few questions.
The AI reads the Google Cloud Security Command Center documentation, then asks which credentials you will use, which data to sync (for example findings and assets), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Google Cloud Security Command Center data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
05Related
