Control types for @turbot/gcp-dataproc

• GCP > Dataproc > API Enabled
• GCP > Dataproc > CMDB
• GCP > Dataproc > Cluster > Active
• GCP > Dataproc > Cluster > Approved
• GCP > Dataproc > Cluster > CMDB
• GCP > Dataproc > Cluster > Discovery
• GCP > Dataproc > Cluster > Labels
• GCP > Dataproc > Cluster > Policy
• GCP > Dataproc > Cluster > Policy > Trusted Access
• GCP > Dataproc > Cluster > Usage
• GCP > Dataproc > Discovery
• GCP > Dataproc > Job > Active
• GCP > Dataproc > Job > Approved
• GCP > Dataproc > Job > CMDB
• GCP > Dataproc > Job > Discovery
• GCP > Dataproc > Job > Labels
• GCP > Dataproc > Job > Policy
• GCP > Dataproc > Job > Policy > Trusted Access
• GCP > Dataproc > Job > Usage
• GCP > Dataproc > Workflow Template > Active
• GCP > Dataproc > Workflow Template > Approved
• GCP > Dataproc > Workflow Template > CMDB
• GCP > Dataproc > Workflow Template > Discovery
• GCP > Dataproc > Workflow Template > Labels
• GCP > Dataproc > Workflow Template > Policy
• GCP > Dataproc > Workflow Template > Policy > Trusted Access
• GCP > Dataproc > Workflow Template > Usage

GCP > Dataproc > API Enabled

Check whether GCP Dataproc 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 > Dataproc > API Enabled control compares
the API state against the API Enabled policies,
raises an alarm, and takes the defined enforcement action.

GCP > Dataproc > CMDB

Record and synchronize details for the GCP Dataproc into the CMDB.

The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails 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 > Dataproc > Cluster > Active

Take an action when an GCP Dataproc cluster is not active based on the
GCP > Dataproc > Cluster > 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 > Dataproc > Cluster > 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 > Dataproc > Cluster > Approved

Take an action when a GCP Dataproc cluster is not approved based on GCP > Dataproc > Cluster > 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 > Dataproc > Cluster > CMDB

Record and synchronize details for the GCP Dataproc cluster into the CMDB.

The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails 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 > Dataproc > Cluster > Regions policy, the CMDB control will delete the
resource from the CMDB.

GCP > Dataproc > Cluster > Discovery

Discover GCP Dataproc cluster 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 Guardrails 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 > Dataproc > Cluster > Regions policy, the CMDB
control will delete the resource from the CMDB.

GCP > Dataproc > Cluster > Labels

Take an action when an GCP Dataproc cluster labels is not updated based on the GCP > Dataproc > Cluster > Labels > * policies.

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

See Labels for more information.

GCP > Dataproc > Cluster > Policy

GCP > Dataproc > Cluster > Policy > Trusted Access

Take an action when GCP Dataproc Cluster policy is not trusted based on the
GCP > Dataproc > Cluster > 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 > Dataproc > Cluster > Usage

The Usage control determines whether the number of GCP Dataproc cluster resources exceeds the configured usage limit for this region.

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

GCP > Dataproc > Discovery

Discover GCP Dataproc 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 Guardrails CMDB. Once discovered, resources are then
responsible for tracking changes to themselves through the
CMDB control.

GCP > Dataproc > Job > Active

Take an action when an GCP Dataproc job is not active based on the
GCP > Dataproc > Job > 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 > Dataproc > Job > 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 > Dataproc > Job > Approved

Take an action when a GCP Dataproc job is not approved based on GCP > Dataproc > Job > 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 > Dataproc > Job > CMDB

Record and synchronize details for the GCP Dataproc job into the CMDB.

The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails 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 > Dataproc > Job > Regions policy, the CMDB control will delete the
resource from the CMDB.

GCP > Dataproc > Job > Discovery

Discover GCP Dataproc job 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 Guardrails 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 > Dataproc > Job > Regions policy, the CMDB
control will delete the resource from the CMDB.

GCP > Dataproc > Job > Labels

Take an action when an GCP Dataproc job labels is not updated based on the GCP > Dataproc > Job > Labels > * policies.

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

See Labels for more information.

GCP > Dataproc > Job > Policy

GCP > Dataproc > Job > Policy > Trusted Access

Take an action when GCP Dataproc Job policy is not trusted based on the
GCP > Dataproc > Job > 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 > Dataproc > Job > Usage

The Usage control determines whether the number of GCP Dataproc job resources exceeds the configured usage limit for this cluster.

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

GCP > Dataproc > Workflow Template > Active

Take an action when an GCP Dataproc workflow template is not active based on the
GCP > Dataproc > Workflow Template > 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 > Dataproc > Workflow Template > 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 > Dataproc > Workflow Template > Approved

Take an action when a GCP Dataproc workflow template is not approved based on GCP > Dataproc > Workflow Template > 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 > Dataproc > Workflow Template > CMDB

Record and synchronize details for the GCP Dataproc workflow template into the CMDB.

The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails 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 > Dataproc > Workflow Template > Regions policy, the CMDB control will delete the
resource from the CMDB.

GCP > Dataproc > Workflow Template > Discovery

Discover GCP Dataproc workflow template 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 Guardrails 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 > Dataproc > Workflow Template > Regions policy, the CMDB
control will delete the resource from the CMDB.

GCP > Dataproc > Workflow Template > Labels

Take an action when an GCP Dataproc workflow template labels is not updated based on the GCP > Dataproc > Workflow Template > Labels > * policies.

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

See Labels for more information.

GCP > Dataproc > Workflow Template > Policy

GCP > Dataproc > Workflow Template > Policy > Trusted Access

Take an action when GCP Dataproc Workflow Template policy is not trusted based on the
GCP > Dataproc > Workflow Template > 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 > Dataproc > Workflow Template > Usage

The Usage control determines whether the number of GCP Dataproc workflow template resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the GCP > Dataproc > Workflow Template > Usage policy, and set the limit with the GCP > Dataproc > Workflow Template > Usage > Limit policy.