Control types for @turbot/gcp-bigquery

• GCP > BigQuery > API Enabled
• GCP > BigQuery > CMDB
• GCP > BigQuery > Dataset > Active
• GCP > BigQuery > Dataset > Approved
• GCP > BigQuery > Dataset > CMDB
• GCP > BigQuery > Dataset > Discovery
• GCP > BigQuery > Dataset > Labels
• GCP > BigQuery > Dataset > Publicly Accessible
• GCP > BigQuery > Dataset > Usage
• GCP > BigQuery > Discovery
• GCP > BigQuery > Table > Active
• GCP > BigQuery > Table > Approved
• GCP > BigQuery > Table > CMDB
• GCP > BigQuery > Table > Discovery
• GCP > BigQuery > Table > Labels
• GCP > BigQuery > Table > Policy
• GCP > BigQuery > Table > Policy > Trusted Access
• GCP > BigQuery > Table > Usage

GCP > BigQuery > API Enabled

Configure whether the GCP BigQuery API is enabled.

GCP > BigQuery > CMDB

Record and synchronize details for the GCP BigQuery 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.

GCP > BigQuery > Dataset > Active

Take an action when an GCP BigQuery dataset is not active based on the GCP > BigQuery > Dataset > 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 > BigQuery > Dataset > 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.

GCP > BigQuery > Dataset > Approved

Take an action when a GCP BigQuery dataset is not approved based on GCP > BigQuery > Dataset > 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.

GCP > BigQuery > Dataset > CMDB

Record and synchronize details for the GCP BigQuery dataset 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.

GCP > BigQuery > Dataset > Discovery

Discover GCP BigQuery dataset 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.

GCP > BigQuery > Dataset > Labels

Take an action when an GCP BigQuery dataset labels is not updated based on the GCP > BigQuery > Dataset > Labels > * policies.

If the resource is not updated with the labels defined in GCP > BigQuery > Dataset > Labels > Template, this control raises an alarm and takes the defined enforcement action.

See Labels for more information.

GCP > BigQuery > Dataset > Publicly Accessible

Ensure the BigQuery dataset is not publicly accessible.

GCP > BigQuery > Dataset > Usage

The Usage control determines whether the number of GCP BigQuery dataset resources exceeds the configured usage limit for this project.

You can configure the behavior of this control with the GCP > BigQuery > Dataset > Usage policy, and set the limit with the GCP > BigQuery > Dataset > Usage > Limit policy.

GCP > BigQuery > Discovery

Discover GCP BigQuery 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.

GCP > BigQuery > Table > Active

Take an action when an GCP BigQuery table is not active based on the GCP > BigQuery > Table > 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 > BigQuery > Table > 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.

GCP > BigQuery > Table > Approved

Take an action when a GCP BigQuery table is not approved based on GCP > BigQuery > Table > 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.

GCP > BigQuery > Table > CMDB

Record and synchronize details for the GCP BigQuery table 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.

GCP > BigQuery > Table > Discovery

Discover GCP BigQuery table 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.

GCP > BigQuery > Table > Labels

Take an action when an GCP BigQuery table labels is not updated based on the GCP > BigQuery > Table > Labels > * policies.

If the resource is not updated with the labels defined in GCP > BigQuery > Table > Labels > Template, this control raises an alarm and takes the defined enforcement action.

See Labels for more information.

GCP > BigQuery > Table > Policy

GCP > BigQuery > Table > Policy > Trusted Access

Take an action when GCP BigQuery Table policy is not trusted based on the GCP > BigQuery > Table > Trusted Access > * policies.

The Trusted Access control evaluates the IAM policy against the list of allowed members in each of the Trusted Access sub-policies (Trusted Access > Domains, Trusted Access > Groups, etc)., this control raises an alarm and takes the defined enforcement action.

If set to "Enforce: Trusted Access > *", access to non-trusted members will be removed.

GCP > BigQuery > Table > Usage

The Usage control determines whether the number of GCP BigQuery table resources exceeds the configured usage limit for this project.

You can configure the behavior of this control with the GCP > BigQuery > Table > Usage policy, and set the limit with the GCP > BigQuery > Table > Usage > Limit policy.