Control types for @turbot/gcp-monitoring

• GCP > Monitoring > API Enabled
• GCP > Monitoring > Alert Policy > Active
• GCP > Monitoring > Alert Policy > Approved
• GCP > Monitoring > Alert Policy > CMDB
• GCP > Monitoring > Alert Policy > Discovery
• GCP > Monitoring > Alert Policy > Usage
• GCP > Monitoring > CMDB
• GCP > Monitoring > Discovery
• GCP > Monitoring > Group > Active
• GCP > Monitoring > Group > Approved
• GCP > Monitoring > Group > CMDB
• GCP > Monitoring > Group > Discovery
• GCP > Monitoring > Group > Usage
• GCP > Monitoring > Notification Channel > Active
• GCP > Monitoring > Notification Channel > Approved
• GCP > Monitoring > Notification Channel > CMDB
• GCP > Monitoring > Notification Channel > Discovery
• GCP > Monitoring > Notification Channel > Usage

GCP > Monitoring > API Enabled

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

GCP > Monitoring > Alert Policy > Active

Take an action when an GCP Monitoring alert policy is not active based on the
GCP > Monitoring > Alert Policy > 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 > Monitoring > Alert Policy > 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 > Monitoring > Alert Policy > Approved

Take an action when a GCP Monitoring alert policy is not approved based on GCP > Monitoring > Alert Policy > 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 > Monitoring > Alert Policy > CMDB

Record and synchronize details for the GCP Monitoring alert policy 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 > Monitoring > Alert Policy > Discovery

Discover GCP Monitoring alert policy 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 > Monitoring > Alert Policy > Usage

The Usage control determines whether the number of GCP Monitoring alert policy resources exceeds the configured usage limit for this project.

You can configure the behavior of this control with the GCP > Monitoring > Alert Policy > Usage policy, and set the limit with the GCP > Monitoring > Alert Policy > Usage > Limit policy.

GCP > Monitoring > CMDB

Record and synchronize details for the GCP Monitoring 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 > Monitoring > Discovery

Discover GCP Monitoring 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 > Monitoring > Group > Active

Take an action when an GCP Monitoring group is not active based on the
GCP > Monitoring > Group > 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 > Monitoring > Group > 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 > Monitoring > Group > Approved

Take an action when a GCP Monitoring group is not approved based on GCP > Monitoring > Group > 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 > Monitoring > Group > CMDB

Record and synchronize details for the GCP Monitoring group 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 > Monitoring > Group > Discovery

Discover GCP Monitoring group 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 > Monitoring > Group > Usage

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

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

GCP > Monitoring > Notification Channel > Active

Take an action when an GCP Monitoring notification channel is not active based on the
GCP > Monitoring > Notification Channel > 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 > Monitoring > Notification Channel > 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 > Monitoring > Notification Channel > Approved

Take an action when a GCP Monitoring notification channel is not approved based on GCP > Monitoring > Notification Channel > 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 > Monitoring > Notification Channel > CMDB

Record and synchronize details for the GCP Monitoring notification channel 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 > Monitoring > Notification Channel > Discovery

Discover GCP Monitoring notification channel 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 > Monitoring > Notification Channel > Usage

The Usage control determines whether the number of GCP Monitoring notification channel resources exceeds the configured usage limit for this project.

You can configure the behavior of this control with the GCP > Monitoring > Notification Channel > Usage policy, and set the limit with the GCP > Monitoring > Notification Channel > Usage > Limit policy.