Attack Chain

1. Initial Access: An attacker gains access to an Azure account with sufficient privileges to manage Network Watcher and initiate packet captures.
2. Discovery: The attacker uses the compromised account to explore the Azure environment, identifying target VNets and subnets containing potentially valuable data.
3. Packet Capture Configuration: The attacker configures the Network Watcher Packet Capture feature to capture traffic from the targeted VNet or subnet. This involves specifying the target VM or network interface and the duration of the capture.
4. Start Packet Capture: The attacker initiates the packet capture process, which begins recording network traffic based on the configured parameters. The MICROSOFT.NETWORK/*/STARTPACKETCAPTURE/ACTION operation is triggered in the Azure activity logs.
5. Data Acquisition: Network traffic, including unencrypted credentials or sensitive data, is captured and stored in a designated storage account.
6. Data Exfiltration (Potential): If the attacker has configured the packet capture to store data outside the secure environment, they may exfiltrate the captured data for further analysis or malicious use.
7. Credential Access: The attacker analyzes the captured network traffic to identify and extract credentials or other sensitive information.
8. Lateral Movement/Privilege Escalation: Using the acquired credentials, the attacker attempts to move laterally within the Azure environment, gaining access to additional systems and resources, or escalate privileges to gain higher-level control.

Impact

Successful exploitation could lead to the compromise of sensitive data, including user credentials, API keys, and proprietary information. The impact could range from unauthorized access to internal systems and data breaches to complete control over the affected Azure resources. The severity depends on the scope of the captured network traffic and the sensitivity of the data transmitted. Organizations in all sectors utilizing Azure are potentially vulnerable. The number of victims can vary depending on the access level of the compromised account and the targeted resources.

Recommendation

• Deploy the Sigma rules in this brief to your SIEM and tune for your environment to detect malicious packet capture activity in Azure.
• Review Azure activity logs for instances of MICROSOFT.NETWORK/*/STARTPACKETCAPTURE/ACTION, MICROSOFT.NETWORK/*/VPNCONNECTIONS/STARTPACKETCAPTURE/ACTION, or MICROSOFT.NETWORK/*/PACKETCAPTURES/WRITE operations with a Success outcome, as identified in the rule query.
• Implement the recommendations for Response and Remediation provided in the Setup section of the referenced Elastic rule to improve detection and response capabilities.
• Regularly audit Azure user roles and permissions to ensure that only authorized personnel have the ability to manage Network Watcher and initiate packet captures.