Control types for @turbot/azure-automation
- Azure > Automation > Automation Account > Active
- Azure > Automation > Automation Account > Approved
- Azure > Automation > Automation Account > CMDB
- Azure > Automation > Automation Account > Discovery
- Azure > Automation > Automation Account > Tags
- Azure > Automation > Runbook > Active
- Azure > Automation > Runbook > Approved
- Azure > Automation > Runbook > CMDB
- Azure > Automation > Runbook > Discovery
- Azure > Automation > Runbook > Tags
Azure > Automation > Automation Account > Active
Take an action when an Azure Automation automation account is not active based on theAzure > Automation > Automation 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 > Automation > Automation 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.
tmod:@turbot/azure-automation#/control/types/automationAccountActive
Azure > Automation > Automation Account > Approved
Take an action when an Azure Automation automation account is not approved based on Azure > Automation > Automation 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.
tmod:@turbot/azure-automation#/control/types/automationAccountApproved
Azure > Automation > Automation Account > CMDB
Record and synchronize details for the Azure Automation automation 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 > Automation > Automation Account > Regions
policy, the CMDB control will delete the
resource from the CMDB.
tmod:@turbot/azure-automation#/control/types/automationAccountCmdb
Azure > Automation > Automation Account > Discovery
Discover all Azure Automation automation 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 > Automation > Automation Account > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/azure-automation#/control/types/automationAccountDiscovery
Azure > Automation > Automation Account > Tags
Take an action when an Azure Automation automation account tags is not updated based on the Azure > Automation > Automation Account > Tags > *
policies.
If the resource is not updated with the tags defined in Azure > Automation > Automation Account > Tags > Template
, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
tmod:@turbot/azure-automation#/control/types/automationAccountTags
Azure > Automation > Runbook > Active
Take an action when an Azure Automation runbook is not active based on theAzure > Automation > Runbook > 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 > Automation > Runbook > 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.
tmod:@turbot/azure-automation#/control/types/runbookActive
Azure > Automation > Runbook > Approved
Take an action when an Azure Automation runbook is not approved based on Azure > Automation > Runbook > 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.
tmod:@turbot/azure-automation#/control/types/runbookApproved
Azure > Automation > Runbook > CMDB
Record and synchronize details for the Azure Automation runbook 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 > Automation > Runbook > Regions
policy, the CMDB control will delete the
resource from the CMDB.
tmod:@turbot/azure-automation#/control/types/runbookCmdb
Azure > Automation > Runbook > Discovery
Discover all Azure Automation runbook 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 > Automation > Runbook > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/azure-automation#/control/types/runbookDiscovery
Azure > Automation > Runbook > Tags
Take an action when an Azure Automation runbook tags is not updated based on the Azure > Automation > Runbook > Tags > *
policies.
If the resource is not updated with the tags defined in Azure > Automation > Runbook > Tags > Template
, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
tmod:@turbot/azure-automation#/control/types/runbookTags