Google Security Posture
Defines, assesses, and monitors the overall status of your security in Google Cloud (Google OAuth2).
OCNORA ships 11 typed Google Security Posture operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Security Posture
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Security Posture
Operations, grouped by what they do to your data.
Create and send 2
Delete and cancel 2
Other operations 1
A sample Google Security Posture workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Security Posture trigger is needed.
- 2Get Posturesecurity_posture.get_postureGets a single revision of a Posture.
- 3Create Posturesecurity_posture.create_postureCreates a new Posture.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 11
- Create PostureCreates a new Posture.security_posture.create_posture
- Create Posture DeploymentCreates a new PostureDeployment in a given project and location.security_posture.create_posture_deployment
- Delete PostureDeletes all revisions of a Posture.security_posture.delete_posture
- Delete Posture DeploymentDeletes a PostureDeployment.security_posture.delete_posture_deployment
- Extract PostureExtracts existing policies from an organization, folder, or project, and applies them to another organization, folder, or project as a Posture.security_posture.extract_posture
- Get PostureGets a single revision of a Posture.security_posture.get_posture
- Get Posture DeploymentGets details for a PostureDeployment.security_posture.get_posture_deployment
- List Posture DeploymentsLists every PostureDeployment in a project and location.security_posture.list_posture_deployments
- List PosturesLists the most recent revisions of all Posture resources in a specified organization and location.security_posture.list_postures
- Update PostureUpdates a revision of an existing Posture.security_posture.update_posture
- Update Posture DeploymentUpdates an existing PostureDeployment.security_posture.update_posture_deployment
Google Security Posture questions
- How does OCNORA authenticate with Google Security Posture?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Security Posture?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Security Posture operation I need is not listed?
- Where Google Security Posture has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Security Posture?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Security Posture calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Security Posture workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.