Take an action when an Azure Monitor action group is not active based on the&#92;n`Azure &gt; Monitor &gt; Action Group &gt; Active &gt; * policies`.&#92;n&#92;nThe Active control determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated compliance&#92;nenvironment, it&#39;s common to end up with a wide range of alarms that are difficult&#92;nand time consuming to clear. The Active control brings automated, well-defined&#92;ncontrol to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Action Group &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Monitor > Action Group

Azure > Monitor > Action Group > Active

Azure > Monitor > Action Group > Active > Age

Azure > Monitor > Action Group > Active > Last Modified

Take an action when an Azure Monitor action group is not approved based on `Azure &gt; Monitor &gt; Action Group &gt; Approved &gt; * policies`.&#92;n&#92;nThe 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.&#92;n&#92;nFor 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.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Monitor > Action Group > Approved

Azure > Monitor > Action Group > Approved > Custom

Azure > Monitor > Action Group > Approved > Usage

Record and synchronize details for the Azure Monitor action group into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is&#92;nresponsible for populating and updating all the attributes for that&#92;nresource type in the Guardrails CMDB.&#92;n&#92;n**Note:** If CMDB is set to Skip for a resource, then it will not be added&#92;nto the CMDB, and no controls that target it will run.&#92;n

Azure > Monitor > Action Group > CMDB

Maintain Azure &gt; Monitor &gt; Action Group configuration.&#92;n&#92;n**Note**: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored&#92;nand inherit from the stack that owns it.&#92;n

Azure > Monitor > Action Group > Configured

Azure > Monitor > Action Group > Configured > Claim Precedence

Azure > Monitor > Action Group > Configured > Source

Discover all Azure Monitor action group resources and add them to the CMDB.&#92;n&#92;nThe [Discovery](https://turbot.com/guardrails/docs/concepts/guardrails/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](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control.&#92;n

Azure > Resource Group

Azure > Monitor > Action Group > Discovery

Take an action when an Azure Monitor alerts is not active based on the&#92;n`Azure &gt; Monitor &gt; Alerts &gt; Active &gt; * policies`.&#92;n&#92;nThe Active control determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated compliance&#92;nenvironment, it&#39;s common to end up with a wide range of alarms that are difficult&#92;nand time consuming to clear. The Active control brings automated, well-defined&#92;ncontrol to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Alerts &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Monitor > Alerts

Azure > Monitor > Alerts > Active

Azure > Monitor > Alerts > Active > Age

Azure > Monitor > Alerts > Active > Last Modified

Take an action when an Azure Monitor alerts is not approved based on `Azure &gt; Monitor &gt; Alerts &gt; Approved &gt; * policies`.&#92;n&#92;nThe 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.&#92;n&#92;nFor 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.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Monitor > Alerts > Approved

Azure > Monitor > Alerts > Approved > Custom

Azure > Monitor > Alerts > Approved > Usage

Record and synchronize details for the Azure Monitor alerts into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is&#92;nresponsible for populating and updating all the attributes for that&#92;nresource type in the Guardrails CMDB.&#92;n&#92;n**Note:** If CMDB is set to Skip for a resource, then it will not be added&#92;nto the CMDB, and no controls that target it will run.&#92;n

Azure > Monitor > Alerts > CMDB

Azure > Monitor > Alerts > Configured

Azure > Monitor > Alerts > Configured > Precedence

Azure > Monitor > Alerts > Configured > Source

Discover all Azure Monitor alerts resources and add them to the CMDB.&#92;n&#92;nThe [Discovery](https://turbot.com/guardrails/docs/concepts/guardrails/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](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control.&#92;n

Azure > Monitor > Alerts > Discovery

Take an action when an Azure Monitor log profile is not active based on the&#92;n`Azure &gt; Monitor &gt; Log Profile &gt; Active &gt; * policies`.&#92;n&#92;nThe Active control determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated compliance&#92;nenvironment, it&#39;s common to end up with a wide range of alarms that are difficult&#92;nand time consuming to clear. The Active control brings automated, well-defined&#92;ncontrol to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Log Profile &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Monitor > Log Profile

Azure > Monitor > Log Profile > Active

Azure > Monitor > Log Profile > Active > Age

Azure > Monitor > Log Profile > Active > Last Modified

Take an action when an Azure Monitor log profile is not approved based on `Azure &gt; Monitor &gt; Log Profile &gt; Approved &gt; * policies`.&#92;n&#92;nThe 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.&#92;n&#92;nFor 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.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Monitor > Log Profile > Approved

Azure > Monitor > Log Profile > Approved > Custom

Azure > Monitor > Log Profile > Approved > Usage

Record and synchronize details for the Azure Monitor log profile into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is&#92;nresponsible for populating and updating all the attributes for that&#92;nresource type in the Guardrails CMDB.&#92;n&#92;n**Note:** If CMDB is set to Skip for a resource, then it will not be added&#92;nto the CMDB, and no controls that target it will run.&#92;n

Azure > Monitor > Log Profile > CMDB

Discover all Azure Monitor log profile resources and add them to the CMDB.&#92;n&#92;nThe [Discovery](https://turbot.com/guardrails/docs/concepts/guardrails/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](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control.&#92;n

Azure > Subscription

Azure > Monitor > Log Profile > Discovery

Configure a custom stack on Azure, per the custom `Stack &gt; Source`.&#92;n&#92;nA Guardrails `Stack` is a set of resources configured by Guardrails, as specified&#92;nvia Terraform source.  Stacks are responsible for the creation and deletion&#92;nof multiple resources. Once created, stack resources are responsible for&#92;nconfiguring themselves from the stack source via their `Configured` control.&#92;n

Azure > Monitor

Azure > Monitor > Stack

Azure > Monitor > Stack > Secret Variables

Azure > Monitor > Stack > Source

Azure > Monitor > Stack > Terraform Version

Azure > Monitor > Stack > Variables

actionGroup

actionGroupAka

invalid - does not support triangular braces, asterisk, ampersand, colon, slashes, question mark, plus sign and hash

actionGroupName

actionGroupServiceNow

alertAka

invalid - does not support triangular braces, asterisk, ampersand, colon, slashes, question mark and plus sign

alertName

alerts

alertsServiceNow

test01

test-02

teste01

logProfile

logProfileAka

logProfileName

logProfileServiceNow

monitor

monitorAka

azure-monitor

Determine the action to take when an Azure Monitor action group, based on the `Azure &gt; Monitor &gt; Action Group &gt; Active &gt; *` policies.&#92;n&#92;nThe control determines whether the resource is in active use, and if not,&#92;nhas the ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Action Group &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The age after which the Azure Monitor action group&#92;nis no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Action Group &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The number of days since the Azure Monitor action group was last modified before it is considered&#92;ninactive.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Action Group &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n

Determine the action to take when an Azure Monitor action group is not approved based on `Azure &gt; Monitor &gt; Action Group &gt; Approved &gt; *` policies.&#92;n&#92;nThe 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.&#92;n&#92;nFor 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.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure Monitor action group is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Monitor action group is not approved, it will be subject to the action specified in the `Azure &gt; Monitor &gt; Action Group &gt; Approved` policy.&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Approved`, `Not approved` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Approved` or `Not approved`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

string

Determine whether the Azure Monitor action group is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Monitor action group is not approved, it will be subject to the action specified in the `Azure &gt; Monitor &gt; Action Group &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Configure whether to record and synchronize details for the Azure Monitor action group into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.&#92;nAll policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to **&quot;Enforce: Enabled&quot;**.&#92;n&#92;nIf set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.&#92;n&#92;nTo cleanup resources and stop tracking changes, set this policy to **&quot;Enforce: Disabled&quot;**.&#92;n

Determine how to configure this resource.&#92;n&#92;n**Note**: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored&#92;nand inherit from the stack that owns it.&#92;n&#92;nThe policy values for Azure &gt; Monitor &gt; Action Group are deprecated and&#92;nreplaced by new values. The deprecated values will be removed in the next major version.&#92;n&#92;n| Deprecated Values                                |  Current Values                                                |&#92;n|--------------------------------------------------|----------------------------------------------------------------|&#92;n| Skip if using Configured &gt; Source                | Skip &#92;&#92;(unless claimed by a stack&#92;&#92;)                             |&#92;n| Check: Configured if using Configured &gt; Source   | Check: Per Configured &gt; Source &#92;&#92;(unless claimed by a stack&#92;&#92;)   |&#92;n| Enforce: Configured if using Configured &gt; Source | Enforce: Per Configured &gt; Source &#92;&#92;(unless claimed by a stack&#92;&#92;) |&#92;n

An ordered list of who is allowed to claim a resource.&#92;nA stack cannot claim a resource if it is already claimed by another&#92;nstack at a higher level of precedence.&#92;n

A HCL or JSON format Terraform configuration source used to configure this resource.

Determine the action to take when an Azure Monitor alerts, based on the `Azure &gt; Monitor &gt; Alerts &gt; Active &gt; *` policies.&#92;n&#92;nThe control determines whether the resource is in active use, and if not,&#92;nhas the ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Alerts &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The age after which the Azure Monitor alerts&#92;nis no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Alerts &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The number of days since the Azure Monitor alerts was last modified before it is considered&#92;ninactive.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Alerts &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n

Determine the action to take when an Azure Monitor alerts is not approved based on `Azure &gt; Monitor &gt; Alerts &gt; Approved &gt; *` policies.&#92;n&#92;nThe 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.&#92;n&#92;nFor 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.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure Monitor alerts is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Monitor alerts is not approved, it will be subject to the action specified in the `Azure &gt; Monitor &gt; Alerts &gt; Approved` policy.&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Approved`, `Not approved` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Approved` or `Not approved`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

Determine whether the Azure Monitor alerts is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Monitor alerts is not approved, it will be subject to the action specified in the `Azure &gt; Monitor &gt; Alerts &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Configure whether to record and synchronize details for the Azure Monitor alerts into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.&#92;nAll policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to **&quot;Enforce: Enabled&quot;**.&#92;n&#92;nIf set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.&#92;n&#92;nTo cleanup resources and stop tracking changes, set this policy to **&quot;Enforce: Disabled&quot;**.&#92;n

Determine how to configure this resource.  Note that if the resource&#92;nis managed by another stack, then the Skip/Check/Enforce values here are ignored&#92;nand inherit from the stack that owns it&#92;n

An ordered list of who is allowed to claim a resource.&#92;nA stack cannot claim a resource if it is already claimed by another&#92;nstack at a higher level of precedence.&#92;n&#92;nBy default, all resources are configured to use the precedence defined&#92;nhere, though they can override their Claim Precedence&#92;n

A HCL or JSON format Terraform configuration source used to configure this resource

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermissions for Azure Monitor that is used as input to the control that manages&#92;nthe IAM stack.&#92;n

Azure > Turbot > Permissions > Compiled > Service Permissions

Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-monitor

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermission levels for Azure Monitor that is used as input to the&#92;nstack that manages the Guardrails IAM permissions objects.&#92;n

Azure > Turbot > Permissions > Compiled > Levels

Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-monitor

Determine the action to take when an Azure Monitor log profile, based on the `Azure &gt; Monitor &gt; Log Profile &gt; Active &gt; *` policies.&#92;n&#92;nThe control determines whether the resource is in active use, and if not,&#92;nhas the ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Log Profile &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The age after which the Azure Monitor log profile&#92;nis no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Log Profile &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The number of days since the Azure Monitor log profile was last modified before it is considered&#92;ninactive.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Monitor &gt; Log Profile &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n

Determine the action to take when an Azure Monitor log profile is not approved based on `Azure &gt; Monitor &gt; Log Profile &gt; Approved &gt; *` policies.&#92;n&#92;nThe 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.&#92;n&#92;nFor 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.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure Monitor log profile is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Monitor log profile is not approved, it will be subject to the action specified in the `Azure &gt; Monitor &gt; Log Profile &gt; Approved` policy.&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Approved`, `Not approved` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Approved` or `Not approved`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

Determine whether the Azure Monitor log profile is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Monitor log profile is not approved, it will be subject to the action specified in the `Azure &gt; Monitor &gt; Log Profile &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Configure whether to record and synchronize details for the Azure Monitor log profile into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.&#92;nAll policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to **&quot;Enforce: Enabled&quot;**.&#92;n&#92;nIf set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.&#92;n&#92;nTo cleanup resources and stop tracking changes, set this policy to **&quot;Enforce: Disabled&quot;**.&#92;n

Azure > Monitor > Enabled

Azure > Monitor > Permissions > Levels

Configure whether permissions policies are in effect for Azure Monitor&#92;nThis setting does not affect Subscription level permissions (Azure/Admin, Azure/Owner, etc)&#92;n

Azure > Monitor > Permissions

Azure > Monitor > Permissions > Levels > Modifiers

Define the permissions levels that can be used to grant access to Storage an&#92;nAzure Subscription.  Permissions levels defined will appear in the UI to assign&#92;naccess to Guardrails users.&#92;n

A map of Azure API to Guardrails Permission Level used to customize Guardrails&#39;&#92;nstandard permissions. You can add, remove or redefine the mapping of&#92;nAzure API operations to Guardrails permissions levels here.&#92;n&#92;n```&#92;nexample:&#92;n  - &quot;Microsoft.Monitor/Monitor/delete&quot;: operator&#92;n  - &quot;Microsoft.Monitor/Monitor/write&quot;: admin&#92;n  - &quot;Microsoft.Monitor/Monitor/read&quot;: readonly&#92;n```&#92;n

azure_monitor_stack

Azure CIS v2.0.0 - Section 5 - Logging and Monitoring

Terraform secret variables in Terraform HCL that will be used as&#92;ninputs to the stack as a [.tfvars file](https://www.terraform.io/docs/configuration/variables.html#variable-definitions-tfvars-files).&#92;n&#92;nA Guardrails `Stack` is a set of resources configured by Guardrails,&#92;nas specified  via Terraform source.  Stacks are responsible&#92;nfor the creation and deletion of multiple resources. Once created,&#92;nstack resources are responsible for configuring themselves from&#92;nthe stack source via their `Configured` control.&#92;n

The Terraform HCL source used to configure this stack.&#92;n&#92;nA Guardrails `Stack` is a set of resources configured by Guardrails, as specified&#92;nvia Terraform source.  Stacks are responsible for the creation and deletion&#92;nof multiple resources. Once created, stack resources are responsible for&#92;nconfiguring themselves from the stack source via their `Configured` control.&#92;n

azure_monitor_stack_source

The Version of Terraform to use for this stack.&#92;nSpecify an [npm-style semver](https://docs.npmjs.com/misc/semver) string to&#92;ndetermine which version of the Terraform container&#92;nGuardrails will use to run this stack.&#92;n&#92;nA Guardrails `Stack` is a set of resources configured by Guardrails,&#92;nas specified  via Terraform source.  Stacks are responsible&#92;nfor the creation and deletion of multiple resources. Once created,&#92;nstack resources are responsible for configuring themselves from&#92;nthe stack source via their `Configured` control.&#92;n

azure_monitor_stack_terraform_version

Terraform variables in Terraform HCL that will be used as&#92;ninputs to the stack as a [.tfvars file](https://www.terraform.io/docs/configuration/variables.html#variable-definitions-tfvars-files).&#92;n&#92;nA Guardrails `Stack` is a set of resources configured by Guardrails,&#92;nas specified  via Terraform source.  Stacks are responsible&#92;nfor the creation and deletion of multiple resources. Once created,&#92;nstack resources are responsible for configuring themselves from&#92;nthe stack source via their `Configured` control.&#92;n

Azure > Monitor > Action Group > ServiceNow

Azure > Monitor > Action Group > ServiceNow > Configuration Item

Azure > Monitor > Action Group > ServiceNow > Configuration Item > Record

Azure > Monitor > Alerts > ServiceNow

Azure > Monitor > Alerts > ServiceNow > Configuration Item

Azure > Monitor > Alerts > ServiceNow > Configuration Item > Record

Azure > Monitor > Log Profile > ServiceNow

Azure > CIS v1 > 5 Logging and Monitoring > 5.1 Configuring Log Profile > 5.1.2 Ensure that Activity Log Retention is set 365 days or greater (Scored)

Azure > CIS v1 > 5 Logging and Monitoring > 5.1 Configuring Log Profile > 5.1.3 Ensure audit profile captures all the activities (Scored)

Azure > CIS v1 > 5 Logging and Monitoring > 5.1 Configuring Log Profile > 5.1.4 Ensure the log profile captures activity logs for all regions including global (Scored)

Azure > CIS v1 > 5 Logging and Monitoring > 5.1 Configuring Log Profile > 5.1.5 Ensure the storage container storing the activity logs is not publicly accessible (Scored)

Azure > CIS v1 > 5 Logging and Monitoring > 5.1 Configuring Log Profile > 5.1.6 Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) (Scored)

Azure > CIS v2.0 > 05 - Logging and Monitoring > 5.01 - Configuring Diagnostic Settings > 5.01.03 - Ensure the Storage Container Storing the Activity Logs is not Publicly Accessible

Azure > CIS v2.0 > 05 - Logging and Monitoring > 5.01 - Configuring Diagnostic Settings > 5.01.04 - Ensure the storage account containing the container with activity logs is encrypted with Customer Managed Key

Mod: azure-monitor

Recommended Version

Resource Types

Controls

IAM Roles

Policies

Policy Packs