Automate Google Security Command Center

What Google Security Command Center is

Security Command Center API provides access to temporal views of assets and findings within an organization.

API host: securitycenter.googleapis.com

What HumDay can do in Google Security Command Center

1 documented operations change something in Google Security Command Center.

• PATCHUpdate the ContainerThreatDetectionSettings resource./v1beta2/{name}

What HumDay can read from Google Security Command Center

These are the operations a schedule or a trigger can watch.

• GETGet the ContainerThreatDetectionSettings resource./v1beta2/{name}
• GETCalculates the effective WebSecurityScannerSettings based on its level in the resource hierarchy and its settings./v1beta2/{name}:calculate

How automating Google Security Command Center works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Google Security Command Center account.
4. Grant access, then go live. You approve the specific Google Security Command Center operations it may use — and only those.

Automate Google Security Command Center with these

• Gmail79 operations
• Google+9 operations
• Google Abusive Experience Report2 operations
• Google Accelerated Mobile Pages (AMP) URL1 operations
• Google Access Approval7 operations
• Google Access Context Manager9 operations
• Google ACME DNS2 operations
• Google Ad Exchange Buyer38 operations
• Google Ad Exchange Buyer II50 operations
• Google Ad Experience Report2 operations
• Google Admin SDK122 operations
• Google AdMob7 operations

Categories

• Analytics
• Media

Questions about Google Security Command Center automation

Can HumDay connect to Google Security Command Center?

Yes. HumDay reads Google Security Command Center's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 3 operations are documented.

Do I need to write code to automate Google Security Command Center?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Security Command Center account.

What can HumDay do in Google Security Command Center?

1 of the 3 documented operations change something in Google Security Command Center, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Security Command Center account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Security Command Center is held behind that approval.

Where this came from

The operations above are read from a published API description for Google Security Command Center at securitycenter.googleapis.com/$discovery/rest?version=v1beta2. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.