Control types for @turbot/azure-mysql

• Azure > MySQL > Flexible Server > Active
• Azure > MySQL > Flexible Server > Approved
• Azure > MySQL > Flexible Server > CMDB
• Azure > MySQL > Flexible Server > Discovery
• Azure > MySQL > Flexible Server > Encryption in Transit
• Azure > MySQL > Flexible Server > Minimum TLS Version
• Azure > MySQL > Flexible Server > Tags
• Azure > MySQL > Server > Active
• Azure > MySQL > Server > Approved
• Azure > MySQL > Server > CMDB
• Azure > MySQL > Server > Discovery
• Azure > MySQL > Server > Encryption in Transit
• Azure > MySQL > Server > Tags

Azure > MySQL > Flexible Server > Active

Take an action when an Azure MySQL flexible server is not active based on the
Azure > MySQL > Flexible Server > 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 > MySQL > Flexible Server > 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 > MySQL > Flexible Server > Approved

Take an action when an Azure MySQL flexible server is not approved based on Azure > MySQL > Flexible Server > 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 > MySQL > Flexible Server > CMDB

Record and synchronize details for the Azure MySQL flexible server 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 > MySQL > Flexible Server > Regions policy, the CMDB control will delete the
resource from the CMDB.

Azure > MySQL > Flexible Server > Discovery

Discover all Azure MySQL flexible server 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 > MySQL > Flexible Server > Regions policy, the CMDB control will delete the resource from the CMDB.

Azure > MySQL > Flexible Server > Encryption in Transit

Define the Encryption in Transit settings required for Azure > MySQL > Flexible Server.

The Encryption in Transit control compares the Encryption in Transit settings against the Encryption in Transit policies for the resource (Azure > MySQL > Flexible Server > Encryption in Transit), raises an alarm, and takes the defined enforcement action.

Azure > MySQL > Flexible Server > Minimum TLS Version

Define the Minimum TLS Version setting required for Azure > MySQL > Flexible Server.

Azure > MySQL > Flexible Server > Tags

Take an action when an Azure MySQL flexible server tags is not updated based on the Azure > MySQL > Flexible Server > Tags > * policies.

If the resource is not updated with the tags defined in Azure > MySQL > Flexible Server > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

Azure > MySQL > Server > Active

Take an action when an Azure MySQL server is not active based on the
Azure > MySQL > Server > 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 > MySQL > Server > 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 > MySQL > Server > Approved

Take an action when an Azure MySQL server is not approved based on Azure > MySQL > Server > 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 > MySQL > Server > CMDB

Record and synchronize details for the Azure MySQL server 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 > MySQL > Server > Regions policy, the CMDB control will delete the
resource from the CMDB.

Azure > MySQL > Server > Discovery

Discover all Azure MySQL server 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 > MySQL > Server > Regions policy, the CMDB control will delete the resource from the CMDB.

Azure > MySQL > Server > Encryption in Transit

Define the Encryption in Transit settings required for Azure > MySQL > Server.

The Encryption in Transit control compares the Encryption in Transit settings against the Encryption in Transit policies for the resource
(Azure > MySQL > Server > Encryption in Transit), raises an alarm, and takes the defined enforcement action

Azure > MySQL > Server > Tags

Take an action when an Azure MySQL server tags is not updated based on the Azure > MySQL > Server > Tags > * policies.

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

See Tags for more information.