Control types for @turbot/azure-frontdoorservice

Azure > Front Door > Front Door > Active

Take an action when an Azure Front Door front door is not active based on the
Azure > Front Door > Front Door > 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 > Front Door > Front Door > 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.

URI
tmod:@turbot/azure-frontdoorservice#/control/types/frontDoorActive

Azure > Front Door > Front Door > Approved

Take an action when an Azure Front Door front door is not approved based on Azure > Front Door > Front Door > 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.

URI
tmod:@turbot/azure-frontdoorservice#/control/types/frontDoorApproved

Azure > Front Door > Front Door > CMDB

Record and synchronize details for the Azure Front Door front door into the CMDB.

The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.

Note that 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.

URI
tmod:@turbot/azure-frontdoorservice#/control/types/frontDoorCmdb
Category

Azure > Front Door > Front Door > Discovery

Discover all Azure Front Door front door 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.

URI
tmod:@turbot/azure-frontdoorservice#/control/types/frontDoorDiscovery