Security Command Center API
Security Command Center API provides access to temporal views of assets and findings within an organization.
Identity & security#openapi#analytics#media
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Security Command Center API provides access to temporal views of assets and findings within an organization.
Endpoints 34
projects.assets
- POSTsecuritycenter.projects.assets.group
/v1/:parent/assets:group - GETsecuritycenter.projects.assets.list
/v1/:parent/assets?compareDuration=string&fieldMask=string&filter=string&orderBy=string&pageSize=0&pageToken=string&readTime=string
projects.securityHealthAnalyticsSettings.effectiveCustomModules
- GETsecuritycenter.projects.securityHealthAnalyticsSettings.effectiveCustomModules.get
/v1/:name - GETsecuritycenter.projects.securityHealthAnalyticsSettings.effectiveCustomModules.list
/v1/:parent/effectiveCustomModules?pageSize=0&pageToken=string
projects.securityHealthAnalyticsSettings.customModules
- DELETEsecuritycenter.projects.securityHealthAnalyticsSettings.customModules.delete
/v1/:name - GETsecuritycenter.projects.securityHealthAnalyticsSettings.customModules.list
/v1/:parent/customModules?pageSize=0&pageToken=string - POSTsecuritycenter.projects.securityHealthAnalyticsSettings.customModules.create
/v1/:parent/customModules - GETsecuritycenter.projects.securityHealthAnalyticsSettings.customModules.listDescendant
/v1/:parent/customModules:listDescendant?pageSize=0&pageToken=string - POSTsecuritycenter.projects.securityHealthAnalyticsSettings.customModules.simulate
/v1/:parent/customModules:simulate
projects.sources.findings.externalSystems
- PATCHsecuritycenter.projects.sources.findings.externalSystems.patch
/v1/:name?updateMask=string
projects.bigQueryExports
- GETsecuritycenter.projects.bigQueryExports.list
/v1/:parent/bigQueryExports?pageSize=0&pageToken=string - POSTsecuritycenter.projects.bigQueryExports.create
/v1/:parent/bigQueryExports?bigQueryExportId=string
projects.eventThreatDetectionSettings
- POSTsecuritycenter.projects.eventThreatDetectionSettings.validateCustomModule
/v1/:parent:validateCustomModule
projects.findings
- POSTsecuritycenter.projects.findings.bulkMute
/v1/:parent/findings:bulkMute
projects.muteConfigs
- GETsecuritycenter.projects.muteConfigs.list
/v1/:parent/muteConfigs?pageSize=0&pageToken=string - POSTsecuritycenter.projects.muteConfigs.create
/v1/:parent/muteConfigs?muteConfigId=string
projects.notificationConfigs
- GETsecuritycenter.projects.notificationConfigs.list
/v1/:parent/notificationConfigs?pageSize=0&pageToken=string - POSTsecuritycenter.projects.notificationConfigs.create
/v1/:parent/notificationConfigs?configId=string
projects.sources
- GETsecuritycenter.projects.sources.list
/v1/:parent/sources?pageSize=0&pageToken=string
organizations.sources
- POSTsecuritycenter.organizations.sources.create
/v1/:parent/sources - POSTsecuritycenter.organizations.sources.getIamPolicy
/v1/:resource:getIamPolicy - POSTsecuritycenter.organizations.sources.setIamPolicy
/v1/:resource:setIamPolicy - POSTsecuritycenter.organizations.sources.testIamPermissions
/v1/:resource:testIamPermissions
projects.sources.findings
- POSTsecuritycenter.projects.sources.findings.group
/v1/:parent/findings:group - GETsecuritycenter.projects.sources.findings.list
/v1/:parent/findings?compareDuration=string&fieldMask=string&filter=string&orderBy=string&pageSize=0&pageToken=string&readTime=string - POSTsecuritycenter.projects.sources.findings.setMute
/v1/:name:setMute - POSTsecuritycenter.projects.sources.findings.setState
/v1/:name:setState
organizations.sources.findings
- POSTsecuritycenter.organizations.sources.findings.create
/v1/:parent/findings?findingId=string
organizations.assets
- POSTsecuritycenter.organizations.assets.runDiscovery
/v1/:parent/assets:runDiscovery
organizations.simulations.valuedResources.attackPaths
- GETsecuritycenter.organizations.simulations.valuedResources.attackPaths.list
/v1/:parent/attackPaths?filter=string&pageSize=0&pageToken=string
organizations.operations
- POSTsecuritycenter.organizations.operations.cancel
/v1/:name:cancel
organizations.resourceValueConfigs
- POSTsecuritycenter.organizations.resourceValueConfigs.batchCreate
/v1/:parent/resourceValueConfigs:batchCreate - GETsecuritycenter.organizations.resourceValueConfigs.list
/v1/:parent/resourceValueConfigs?pageSize=0&pageToken=string
organizations.valuedResources
- GETsecuritycenter.organizations.valuedResources.list
/v1/:parent/valuedResources?filter=string&orderBy=string&pageSize=0&pageToken=string
API details
- Base URL
https://securitycenter.googleapis.com- Authentication
- OAuth 2.0 (authorization code flow) with 2 scopes
An API key in the key query parameter - Operations
- 34 operations on 26 pathsPOST 19GET 13PATCH 1DELETE 1
- Main resources
- projects.securityHealthAnalyticsSettings.customModules 5organizations.sources 4projects.sources.findings 4organizations.resourceValueConfigs 2projects.assets 2projects.bigQueryExports 2projects.muteConfigs 2projects.notificationConfigs 2projects.securityHealthAnalyticsSettings.effectiveCustomMod… 2organizations.assets 1
- Response formats
application/json- Description format
- Google API Discovery, API version
v1 - Links
- Documentation · OpenAPI document
- Listed from
- Google API Discovery document (googleapis/discovery-artifact-manager) (Apache-2.0)
How to test the Security Command Center API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Security Command Center API collection, without the publisher's secrets.
- Add your credentialsThis API uses OAuth 2.0 (authorization code flow) with 2 scopes. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “securitycenter.projects.assets.group” (POST /v1/:parent/assets:group), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Security Command Center API?
Security Command Center API provides access to temporal views of assets and findings within an organization. It is listed under Identity & security and has 34 endpoints.
Who publishes the Security Command Center API?
It is listed from Google's public API description (an OpenAPI document), not published by Google on Swastik Codes. Anyone who controls googleapis.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Security Command Center API?
Requests go to https://securitycenter.googleapis.com. Endpoint paths are added to this base URL.
How do I authenticate with the Security Command Center API?
It accepts 2 methods: OAuth 2.0 (authorization code flow) with 2 scopes; an API key in the key query parameter.
How many endpoints does the Security Command Center API have?
34 operations on 26 paths (19 POST, 13 GET, 1 PATCH, 1 DELETE). The largest groups are projects.securityHealthAnalyticsSettings.customModules, organizations.sources, projects.sources.findings, organizations.resourceValueConfigs.
Is forking the Security Command Center API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.