# Ensure that Network Security Group Flow logs are captured and sent to Log Analytics

- Source: https://support.icompaas.com/support/solutions/articles/62000229909-ensure-that-network-security-group-flow-logs-are-captured-and-sent-to-log-analytics
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [General](https://support.icompaas.com/support/solutions/62000037933) › [Azure Compliance / Control / Check](https://support.icompaas.com/support/solutions/folders/62000168797)
- Last updated: 2026-06-10
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

Network Security Group Flow Logs record IP traffic flowing through NSG rules and are collected by Azure Network Watcher. Sending these logs to a Log Analytics Workspace enables centralized monitoring, advanced analytics, traffic investigations, and threat detection. This control ensures that NSG Flow Logs are enabled for all applicable NSGs and that Log Analytics is selected as the destination to provide full visibility into network activity for security operations and compliance reporting.

  

Rationale:

If NSG Flow Logs are disabled or not sent to Log Analytics, network traffic data will not be recorded, reducing the ability to detect malicious patterns, investigate incidents, identify misconfigurations, or perform historical analysis. This results in a loss of visibility, weakens threat detection capability, and violates requirements of CIS, NIST, SOC2, and Azure Security Benchmark. Logging NSG traffic into Log Analytics ensures NSG events are captured and available for monitoring, auditing, and forensics.

  

Impact:

-   Enables full visibility into NSG network activity
    
-   Supports detection of unusual inbound/outbound traffic
    
-   Provides data for SIEM and threat-hunting workflows
    
-   Helps ensure compliance with network monitoring requirements
    

  

Default Value:

By default, NSG Flow Logs are disabled and no destination workspace is configured. The administrator must explicitly enable Flow Logs and configure a Log Analytics Workspace for log ingestion.

  

Pre-Requisites:

-   Network Watcher must be enabled in the region
    
-   Log Analytics Workspace must exist
    
-   RBAC permissions:
    

-   Microsoft.Network/networkWatchers/\*
    
-   Microsoft.OperationalInsights/workspaces/write
    
-   Microsoft.Network/networkSecurityGroups/\*
    

  

Test Plan:

1.  Sign in to the Azure Portal
    
2.  Search for Network Watcher
    
3.  Under the logs, Open NSG Flow Log
    
4.  Select the subscription and region
    
5.  Review each Network Security Group
    
6.  Verify Flow Logs are enabled
    

7.  If Flow Logs are not enabled, follow the implementation steps
    

  

Implementation Plan:

1.  Sign in to the Azure Portal
    
2.  Search for Network Watcher
    

3.  Open NSG flow logs
    
4.  Click Add flow log
    
5.  Select the target Network Security Group
    
6.  Enable Flow logs
    
7.  Set Flow log version 2
    
8.  Select Log Analytics workspace
    
9.  Choose the workspace
    
10.  Save the configuration
     

  

Backout Plan:

1.  Sign in to the Azure Portal
    
2.  Search for Network Watcher
    
3.  Open NSG flow logs
    
4.  Select the target Network Security Group
    
5.  Disable Flow logs
    
6.  Save the configuration
    

Reference:

-   [https://learn.microsoft.com/azure/network-watcher/network-watcher-nsg-flow-logging-overview](https://learn.microsoft.com/azure/network-watcher/network-watcher-nsg-flow-logging-overview)
    
-   [https://learn.microsoft.com/cli/azure/network/watcher/flow-log](https://learn.microsoft.com/cli/azure/network/watcher/flow-log)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
