Take an action when an Azure Network Watcher flow log is not active based on the&#92;n`Azure &gt; Network Watcher &gt; Flow Log &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; Network Watcher &gt; Flow Log &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 > Network Watcher > Flow Log

Azure > Network Watcher > Flow Log > Active

Azure > Network Watcher > Flow Log > Active > Age

Azure > Network Watcher > Flow Log > Active > Last Modified

Take an action when an Azure Network Watcher flow log is not approved based on `Azure &gt; Network Watcher &gt; Flow Log &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 > Network Watcher > Flow Log > Approved

Azure > Network Watcher > Flow Log > Approved > Custom

Azure > Network Watcher > Flow Log > Approved > Usage

Record and synchronize details for the Azure Network Watcher flow log 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 > Network Watcher > Flow Log > CMDB

Discover all Azure Network Watcher flow log 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 > Network Watcher > Network Watcher

Azure > Network Watcher > Flow Log > Discovery

Raise an alarm if the network security group (NSG) flow log retention policy is not configured to meet the defined policy requirements.&#92;n&#92;n**Note:** This check applies exclusively to flow logs using V2 storage accounts.&#92;n

Azure > Network Watcher > Flow Log > Retention Policy

Azure > Network Watcher > Flow Log > Retention Policy > Days

Take an action when an Azure Network Watcher network watcher is not active based on the&#92;n`Azure &gt; Network Watcher &gt; Network Watcher &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; Network Watcher &gt; Network Watcher &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 > Network Watcher > Network Watcher > Active

Azure > Network Watcher > Network Watcher > Active > Age

Azure > Network Watcher > Network Watcher > Active > Last Modified

Take an action when an Azure Network Watcher network watcher is not approved based on `Azure &gt; Network Watcher &gt; Network Watcher &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 > Network Watcher > Network Watcher > Approved

Azure > Network Watcher > Network Watcher > Approved > Custom

Azure > Network Watcher > Network Watcher > Approved > Regions

Azure > Network Watcher > Network Watcher > Approved > Usage

Record and synchronize details for the Azure Network Watcher network watcher 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&#92;nCMDB controls also use the Regions policy associated with the resource. If&#92;nregion is not in `Azure &gt; Network Watcher &gt; Network Watcher &gt; Regions` policy, the CMDB control will delete the&#92;nresource from the CMDB.&#92;n

Azure > Network Watcher > Network Watcher > CMDB

Discover all Azure Network Watcher network watcher 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&#92;n**Note:** Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in `Azure &gt; Network Watcher &gt; Network Watcher &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n

Azure > Resource Group

Azure > Network Watcher > Network Watcher > Discovery

Take an action when an Azure Network Watcher network watcher tags is not updated based on the `Azure &gt; Network Watcher &gt; Network Watcher &gt; Tags &gt; *` policies.&#92;n&#92;nIf the resource is not updated with the tags defined in `Azure &gt; Network Watcher &gt; Network Watcher &gt; Tags &gt; Template`, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Network Watcher > Network Watcher > Tags

Azure > Network Watcher > Network Watcher > Tags > Template

Microsoft.NetworkNetworkWatcherRGTestVM1-nsg

NetworkWatcher_northeurope

flowLog

flowLogAka

flowLogId

flowLogProperties

flowLogServiceNow

networkWatcher

networkWatcherAka

networkWatcherId

networkWatcherName

networkWatcherService

networkWatcherServiceAka

networkWatcherServiceNow

targetResourceId

azure-networkwatcher

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

Azure > Turbot > Permissions > Compiled > Service Permissions

Azure > Subscription

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

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermission levels for Azure Network Watcher 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-networkwatcher

Determine the action to take when an Azure Network Watcher flow log, based on the `Azure &gt; Network Watcher &gt; Flow Log &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; Network Watcher &gt; Flow Log &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 Network Watcher flow log&#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; Network Watcher &gt; Flow Log &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 Network Watcher flow log 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; Network Watcher &gt; Flow Log &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 Network Watcher flow log is not approved based on `Azure &gt; Network Watcher &gt; Flow Log &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_networkwatcher_flowlog_approved

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

Determine whether the Azure Network Watcher flow log is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Network Watcher flow log is not approved, it will be subject to the action specified in the `Azure &gt; Network Watcher &gt; Flow Log &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

azure_networkwatcher_flowlog_approved_custom

string

Determine whether the Azure Network Watcher flow log is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Network Watcher flow log is not approved, it will be subject to the action specified in the `Azure &gt; Network Watcher &gt; Flow Log &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 Network Watcher flow log 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

Raise an alarm if the network security group flow log retention policy is not configured to meet policy.&#92;n&#92;n**Note:** This check applies exclusively to flow logs using V2 storage accounts.&#92;n

azure_networkwatcher_flow_log_retention_policy

Azure CIS v2.0.0 - Section 6 - Networking

The number of days for which the flow logs are retained. Flow logs are deleted by Azure at the end of a retention period.&#92;n

azure_networkwatcher_flow_log_retention_policy_days

Determine the action to take when an Azure Network Watcher network watcher, based on the `Azure &gt; Network Watcher &gt; Network Watcher &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; Network Watcher &gt; Network Watcher &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 Network Watcher network watcher&#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; Network Watcher &gt; Network Watcher &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 Network Watcher network watcher 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; Network Watcher &gt; Network Watcher &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 Network Watcher network watcher is not approved based on `Azure &gt; Network Watcher &gt; Network Watcher &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_network_watcher_approved

Determine whether the Azure Network Watcher network watcher is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Network Watcher network watcher is not approved, it will be subject to the action specified in the `Azure &gt; Network Watcher &gt; Network Watcher &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

azure_network_watcher_approved_custom

A list of Azure regions in which Azure Network Watcher network watchers are approved for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and &#39;?&#39; wildcard characters.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Network Watcher network watcher is created in a region that is not in the approved list, it will be subject to the action specified in the `Azure &gt; Network Watcher &gt; Network Watcher &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure Network Watcher network watcher is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Network Watcher network watcher is not approved, it will be subject to the action specified in the `Azure &gt; Network Watcher &gt; Network Watcher &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 Network Watcher network watcher 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&#92;nCMDB controls also use the Regions policy associated with the resource. If region is not in `Azure &gt; Network Watcher &gt; Network Watcher &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n&#92;n(**Note**: Setting CMDB to **&quot;Skip&quot;** will also pause these changes.)&#92;n

A list of Azure regions in which Azure Network Watcher network watchers are supported for use.&#92;n&#92;nAny network watchers in a region not listed here will not be recorded in CMDB.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n

Azure > Network Watcher > Network Watcher > Regions

A list of Azure regions in which Azure Network Watcher resources are approved for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Network Watcher resources&#39; Approved &gt; Regions policies.&#92;n

Azure > Network Watcher

Azure > Network Watcher > Approved Regions [Default]

Azure > Network Watcher > Enabled

Azure > Network Watcher > Permissions > Levels

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

Azure > Network Watcher > Permissions

Azure > Network Watcher > 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.Network Watcher/Network Watcher/delete&quot;: operator&#92;n  - &quot;Microsoft.Network Watcher/Network Watcher/write&quot;: admin&#92;n  - &quot;Microsoft.Network Watcher/Network Watcher/read&quot;: readonly&#92;n```&#92;n

A list of Azure regions in which Azure Network Watcher resources are supported for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Network Watcher resources&#39; Regions policies.&#92;n

Azure > Network Watcher > Regions

A template used to generate the keys and values for Azure Network Watcher resources.&#92;n&#92;nBy default, all Network Watcher resource Tags &gt; Template policies will use this value.&#92;n

Azure > Network Watcher > Tags Template [Default]

Determine the action to take when an Azure Network Watcher network watcher tags are not updated based on the `Azure &gt; Network Watcher &gt; Network Watcher &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensure Azure Network Watcher network watcher tags include tags defined in `Azure &gt; Network Watcher &gt; Network Watcher &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Network Watcher Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

The template is used to generate the keys and values for Azure Network Watcher network watcher.&#92;n&#92;nTags not defined in Network Watcher Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Network Watcher > Flow Log > ServiceNow

Flow Log resource in Azure Network Watcher service.

Azure > CIS v1 > 6 Networking > 6.04 Ensure that Network Security Group Flow Log retention period is &#39;greater than 90 days&#39; (Scored)

Azure > CIS v2.0 > 05 - Logging and Monitoring > 5.01 - Configuring Diagnostic Settings > 5.01.06 - Ensure that Network Security Group Flow logs are captured and sent to Log Analytics

Azure > CIS v2.0 > 06 - Networking > 6.05 - Ensure that Network Security Group Flow Log retention period is &#39;greater than 90 days&#39;

Azure > Network Watcher > Flow Log > ServiceNow > Configuration Item

Azure > CIS v2.0 > 05 - Logging and Monitoring > 5.01 - Configuring Diagnostic Settings > 5.01.06 - Ensure that Network Security Group flow logs are captured and sent to Log Analytics

Azure > Network Watcher > Flow Log > ServiceNow > Configuration Item > Record

Azure > Network Watcher > Network Watcher > ServiceNow

Network Watcher resource in Azure Network Watcher service.

Mod: azure-networkwatcher

Recommended Version

Resource Types

Controls

IAM Roles

Policies

Policy Packs