Microsoft AzureOverview
Enable Network Watcher for Azure subscriptions.
Rationale
Network diagnostic and visualization tools available with Network Watcher help users understand, diagnose, and gain insights into the Azure network.
Impact
Running and storing network data incurs additional costs per transaction, which can quickly add up for high-volume networks.
Default Value
Network Watcher is automatically enabled.
When you create or update a virtual network in your subscription, Network Watcher will be enabled automatically in your Virtual Network's region. There is no impact on your resources or associated charge for automatically enabling Network Watcher.
References
- https://learn.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview
- https://docs.azure.cn/zh-cn/cli/network/watcher?view=azure-cli-latest#az_network_watcher_list
- https://docs.azure.cn/zh-cn/cli/network/watcher?view=azure-cli-latest#az_network_watcher_configure
- https://learn.microsoft.com/en-us/azure/network-watcher/network-watcher-create
- https://learn.microsoft.com/en-us/azure/security/benchmarks/security-controls-v2-logging-threat-detection#lt-3-enable-logging-for-azure-network-activities
- https://azure.microsoft.com/en-ca/pricing/details/network-watcher/
Remediation guidance
Opting out of Network Watcher automatic enablement is a permanent change. Once you opt-out, you cannot opt-in without contacting support.
To manually enable Network Watcher in each region where you want to use Network Watcher capabilities, follow the steps below.
Remediate from Azure Portal
- Use the Search bar to search for and click on the
Network Watcherservice. - Click
Create. - Select a
Regionfrom the drop-down menu. - Click
Add.
Remediate from Azure CLI
az network watcher configure --locations <region> --enabled true --resource-group <resource_group>
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Azure
Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Azure Connectors without network watchers in all used regions
Connectors
Covered asset types
Expected check: eq []
{
AzureRegionsWithoutNetworkWatcher {
...AssetFragment
}
}
