Control types for @turbot/gcp-firebase

• GCP > Firebase > API Enabled
• GCP > Firebase > Android App > Active
• GCP > Firebase > Android App > Approved
• GCP > Firebase > Android App > CMDB
• GCP > Firebase > Android App > Discovery
• GCP > Firebase > Android App > Usage
• GCP > Firebase > CMDB
• GCP > Firebase > Discovery
• GCP > Firebase > Firebase Project > CMDB
• GCP > Firebase > Firebase Project > Discovery
• GCP > Firebase > Web App > Active
• GCP > Firebase > Web App > Approved
• GCP > Firebase > Web App > CMDB
• GCP > Firebase > Web App > Discovery
• GCP > Firebase > Web App > Usage
• GCP > Firebase > iOS App > Active
• GCP > Firebase > iOS App > Approved
• GCP > Firebase > iOS App > CMDB
• GCP > Firebase > iOS App > Discovery
• GCP > Firebase > iOS App > Usage

GCP > Firebase > API Enabled

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

GCP > Firebase > Android App > Active

Take an action when an GCP Firebase android app is not active based on the
GCP > Firebase > Android App > 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 > Firebase > Android App > 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 > Firebase > Android App > Approved

Take an action when a GCP Firebase android app is not approved based on GCP > Firebase > Android App > 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 > Firebase > Android App > CMDB

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

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > Android App > Discovery

Discover GCP Firebase android app 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.

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > Android App > Usage

The Usage control determines whether the number of GCP Firebase android app resources exceeds the configured usage limit for this project.

You can configure the behavior of this control with the GCP > Firebase > Android App > Usage policy, and set the limit with the GCP > Firebase > Android App > Usage > Limit policy.

GCP > Firebase > CMDB

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

Discover GCP Firebase 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 > Firebase > Firebase Project > CMDB

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

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > Firebase Project > Discovery

Discover GCP Firebase firebase project 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.

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > Web App > Active

Take an action when an GCP Firebase web app is not active based on the
GCP > Firebase > Web App > 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 > Firebase > Web App > 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 > Firebase > Web App > Approved

Take an action when a GCP Firebase web app is not approved based on GCP > Firebase > Web App > 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 > Firebase > Web App > CMDB

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

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > Web App > Discovery

Discover GCP Firebase web app 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.

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > Web App > Usage

The Usage control determines whether the number of GCP Firebase web app resources exceeds the configured usage limit for this project.

You can configure the behavior of this control with the GCP > Firebase > Web App > Usage policy, and set the limit with the GCP > Firebase > Web App > Usage > Limit policy.

GCP > Firebase > iOS App > Active

Take an action when an GCP Firebase ios app is not active based on the
GCP > Firebase > iOS App > 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 > Firebase > iOS App > 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 > Firebase > iOS App > Approved

Take an action when a GCP Firebase ios app is not approved based on GCP > Firebase > iOS App > 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 > Firebase > iOS App > CMDB

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

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > iOS App > Discovery

Discover GCP Firebase ios app 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.

This control will automatically re-run every 24 hours because GCP does not currently support real-time events for this resource type.

GCP > Firebase > iOS App > Usage

The Usage control determines whether the number of GCP Firebase ios app resources exceeds the configured usage limit for this project.

You can configure the behavior of this control with the GCP > Firebase > iOS App > Usage policy, and set the limit with the GCP > Firebase > iOS App > Usage > Limit policy.