Control types for @turbot/azure-cosmosdb

• Azure > Cosmos DB > Database Account > Active
• Azure > Cosmos DB > Database Account > Approved
• Azure > Cosmos DB > Database Account > CMDB
• Azure > Cosmos DB > Database Account > Discovery
• Azure > Cosmos DB > Database Account > Tags
• Azure > Cosmos DB > MongoDB Collection > Active
• Azure > Cosmos DB > MongoDB Collection > Approved
• Azure > Cosmos DB > MongoDB Collection > CMDB
• Azure > Cosmos DB > MongoDB Collection > Discovery
• Azure > Cosmos DB > MongoDB Database > Active
• Azure > Cosmos DB > MongoDB Database > Approved
• Azure > Cosmos DB > MongoDB Database > CMDB
• Azure > Cosmos DB > MongoDB Database > Discovery
• Azure > Cosmos DB > SQL Container > Active
• Azure > Cosmos DB > SQL Container > Approved
• Azure > Cosmos DB > SQL Container > CMDB
• Azure > Cosmos DB > SQL Container > Discovery
• Azure > Cosmos DB > SQL Database > Active
• Azure > Cosmos DB > SQL Database > Approved
• Azure > Cosmos DB > SQL Database > CMDB
• Azure > Cosmos DB > SQL Database > Discovery

Azure > Cosmos DB > Database Account > Active

Take an action when an Azure Cosmos DB database account is not active based on the
Azure > Cosmos DB > Database Account > 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 (Azure > Cosmos DB > Database Account > 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: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

Azure > Cosmos DB > Database Account > Approved

Take an action when an Azure Cosmos DB database account is not approved based on Azure > Cosmos DB > Database Account > 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.

Azure > Cosmos DB > Database Account > CMDB

Record and synchronize details for the Azure Cosmos DB database account 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 Azure > Cosmos DB > Database Account > Regions policy, the CMDB control will delete the
resource from the CMDB.

Azure > Cosmos DB > Database Account > Discovery

Discover all Azure Cosmos DB database account resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Note: Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in Azure > Cosmos DB > Database Account > Regions policy, the CMDB control will delete the resource from the CMDB.

Azure > Cosmos DB > Database Account > Tags

Take an action when an Azure Cosmos DB database account tags is not updated based on the Azure > Cosmos DB > Database Account > Tags > * policies.

If the resource is not updated with the tags defined in Azure > Cosmos DB > Database Account > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

Azure > Cosmos DB > MongoDB Collection > Active

Take an action when an Azure Cosmos DB mongodb collection is not active based on the
Azure > Cosmos DB > MongoDB Collection > 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 (Azure > Cosmos DB > MongoDB Collection > 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: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

Azure > Cosmos DB > MongoDB Collection > Approved

Take an action when an Azure Cosmos DB mongodb collection is not approved based on Azure > Cosmos DB > MongoDB Collection > 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.

Azure > Cosmos DB > MongoDB Collection > CMDB

Record and synchronize details for the Azure Cosmos DB mongodb collection 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.

Azure > Cosmos DB > MongoDB Collection > Discovery

Discover all Azure Cosmos DB mongodb collection resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Azure > Cosmos DB > MongoDB Database > Active

Take an action when an Azure Cosmos DB mongodb database is not active based on the
Azure > Cosmos DB > MongoDB Database > 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 (Azure > Cosmos DB > MongoDB Database > 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: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

Azure > Cosmos DB > MongoDB Database > Approved

Take an action when an Azure Cosmos DB mongodb database is not approved based on Azure > Cosmos DB > MongoDB Database > 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.

Azure > Cosmos DB > MongoDB Database > CMDB

Record and synchronize details for the Azure Cosmos DB mongodb database 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.

Azure > Cosmos DB > MongoDB Database > Discovery

Discover all Azure Cosmos DB mongodb database resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Azure > Cosmos DB > SQL Container > Active

Take an action when an Azure Cosmos DB sql container is not active based on the
Azure > Cosmos DB > SQL Container > 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 (Azure > Cosmos DB > SQL Container > 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: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

Azure > Cosmos DB > SQL Container > Approved

Take an action when an Azure Cosmos DB sql container is not approved based on Azure > Cosmos DB > SQL Container > 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.

Azure > Cosmos DB > SQL Container > CMDB

Record and synchronize details for the Azure Cosmos DB sql container 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.

Azure > Cosmos DB > SQL Container > Discovery

Discover all Azure Cosmos DB sql container resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Azure > Cosmos DB > SQL Database > Active

Take an action when an Azure Cosmos DB sql database is not active based on the
Azure > Cosmos DB > SQL Database > 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 (Azure > Cosmos DB > SQL Database > 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: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

Azure > Cosmos DB > SQL Database > Approved

Take an action when an Azure Cosmos DB sql database is not approved based on Azure > Cosmos DB > SQL Database > 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.

Azure > Cosmos DB > SQL Database > CMDB

Record and synchronize details for the Azure Cosmos DB sql database 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.

Azure > Cosmos DB > SQL Database > Discovery

Discover all Azure Cosmos DB sql database resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.