Control types for @turbot/gcp-run
- GCP > Cloud Run > API Enabled
- GCP > Cloud Run > CMDB
- GCP > Cloud Run > Discovery
- GCP > Cloud Run > Service > Active
- GCP > Cloud Run > Service > Approved
- GCP > Cloud Run > Service > CMDB
- GCP > Cloud Run > Service > Discovery
- GCP > Cloud Run > Service > Encryption at Rest
GCP > Cloud Run > API Enabled
Check whether GCP Cloud Run API is enabled.
API Enabled refers specifically to the API state of a service in a cloud project. This control determines whether the API state is set as per desired level.
The GCP > Cloud Run > API Enabled
control compares
the API state against the API Enabled policies,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/gcp-run#/control/types/runApiEnabled
GCP > Cloud Run > CMDB
Record and synchronize details for the GCP Cloud Run into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added to the CMDB, and no controls that target it will run.
tmod:@turbot/gcp-run#/control/types/runCmdb
GCP > Cloud Run > Discovery
Discover GCP Cloud Run resources and add them to the CMDB.
The Discovery control is tasked with identifying instances for a particular resource. The Discovery control will periodically search for new target resources and save them to the Turbot CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.
tmod:@turbot/gcp-run#/control/types/runDiscovery
GCP > Cloud Run > Service > Active
Take an action when an GCP Cloud Run service is not active based on the
GCP > Cloud Run > Service > Active > *
policies.
The Active control determines whether the resource is in active use, and if not, has the ability to delete / cleanup the resource. When running an automated compliance environment, it's common to end up with a wide range of alarms that are difficult and time consuming to clear. The Active control brings automated, well-defined control to this process.
The Active control checks the status of all defined Active policies for the
resource (GCP > Cloud Run > Service > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/gcp-run#/control/types/serviceActive
GCP > Cloud Run > Service > Approved
Take an action when a GCP Cloud Run service is not approved based on GCP > Cloud Run > Service > Approved > *
policies.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/gcp-run#/control/types/serviceApproved
GCP > Cloud Run > Service > CMDB
Record and synchronize details for the GCP Cloud Run service into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added to the CMDB, and no controls that target it will run.
CMDB controls also use the Regions policy associated with the resource. If
region is not in GCP > Cloud Run > Service > Regions
policy, the CMDB control will delete the
resource from the CMDB.
tmod:@turbot/gcp-run#/control/types/serviceCmdb
GCP > Cloud Run > Service > Discovery
Discover GCP Cloud Run service resources and add them to the CMDB.
The Discovery control is tasked with identifying instances for a particular resource. The Discovery control will periodically search for new target resources and save them to the Turbot CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.
Note that Discovery and CMDB controls also use the Regions policy
associated with the resource. If the region is not in GCP > Cloud Run > Service > Regions
policy, the CMDB
control will delete the resource from the CMDB.
tmod:@turbot/gcp-run#/control/types/serviceDiscovery
GCP > Cloud Run > Service > Encryption at Rest
Define the minimum level of encryption required for GCP Cloud Run service.
tmod:@turbot/gcp-run#/control/types/serviceEncryptionAtRest