PIVTR-D
RAzure playbook · Network and edge

DDoS or application-layer attack

An attacker floods a public IP address with SYN, TCP or UDP traffic, or sends a high rate of valid-looking HTTP requests to a login page, search page or API. Azure DDoS Protection mitigates network layers 3 and 4 only, so an HTTP flood lands on the Application Gateway web application firewall (WAF), the Front Door WAF or the origin itself. Keep the service reachable first: confirm mitigation, then rate-limit and block at the WAF.

Look here

LogSearch for
Public IP metricsWhether the address is under attack and how many packets are dropped. The metrics are IfUnderDDoSAttack, PacketsDroppedDDoS, PacketsInDDoS, DDoSTriggerSYNPackets, DDoSTriggerTCPPackets and DDoSTriggerUDPPackets: az monitor metrics list --resource <public-ip-id> --metrics IfUnderDDoSAttack PacketsDroppedDDoS --interval PT1M --aggregation Maximum
AzureDiagnostics, DDoS categoriesMitigation notices, reports and flow logs. Needs DDoS Network Protection or DDoS IP Protection and a diagnostic setting on the public IP. Reports arrive every 5 minutes during mitigation, with a summary at the end: AzureDiagnostics | where Category in ("DDoSProtectionNotifications", "DDoSMitigationReports", "DDoSMitigationFlowLogs")
AzureDiagnostics, ApplicationGatewayFirewallLogTop sources and paths at the Application Gateway WAF. With a resource-specific diagnostic setting, the entries are in AGWFirewallLogs and AGWAccessLogs: AzureDiagnostics | where ResourceProvider == "MICROSOFT.NETWORK" and Category == "ApplicationGatewayFirewallLog" | summarize count() by clientIp_s, requestUri_s, bin(TimeGenerated, 1m)
AzureDiagnostics, FrontDoorWebApplicationFirewallLogTop sources and matched rules at Front Door. This log contains only requests that matched a WAF rule, and FrontDoorAccessLog has all requests: AzureDiagnostics | where ResourceProvider == "MICROSOFT.CDN" and Category == "FrontDoorWebApplicationFirewallLog" | summarize count() by clientIP_s, ruleName_s, action_s, bin(TimeGenerated, 1m)
Origin logsRequests that skip Front Door, in AppServiceHTTPLogs or the origin's own web logs. They arrive without the X-Azure-FDID header and from addresses outside the AzureFrontDoor.Backend service tag
SecurityAlertDDoS Protection alerts through Defender for Cloud: NETWORK_DDOS_DETECTED and NETWORK_DDOS_MITIGATED

Contain

#Item
1Record the attacked IP addresses, hostnames, start time and the top sources from the queries above in the T3 log
2Engage DDoS Rapid Response on DDoS Network Protection plans when the resource is severely degraded or down, when mitigation is not working, or when the attack has a critical business impact. Open a Technical support request, service DDOS Protection, select the DDoS plan linked to the virtual network, severity A, problem type Under attack
3Put the Application Gateway WAF policy in prevention mode: az network application-gateway waf-policy policy-setting update --policy-name <policy> --resource-group <rg> --mode Prevention --state Enabled
4Put the Front Door WAF policy in prevention mode: az network front-door waf-policy update --resource-group <rg> --name <policy> --mode Prevention
5Add an Application Gateway rate limit rule per client: az network application-gateway waf-policy custom-rule create --policy-name <policy> --resource-group <rg> --name RateLimitLogin --priority 90 --rule-type RateLimitRule --rate-limit-threshold 100 --action Block --group-by-user-session '[{"groupByVariables":[{"variableName":"ClientAddr"}]}]'
6Match the rule to the attacked path: az network application-gateway waf-policy custom-rule match-condition add --policy-name <policy> --resource-group <rg> --name RateLimitLogin --match-variables RequestUri --operator Contains --values /login
7Add a Front Door rate limit rule: az network front-door waf-policy rule create --resource-group <rg> --policy-name <policy> --name RateLimitLogin --priority 1 --rule-type RateLimitRule --rate-limit-duration 1 --rate-limit-threshold 1000 --action Block --match-variable RequestUri --operator Contains --values /login
8Block source ranges or countries with a MatchRule using IPMatch or GeoMatch on the same policies
9Close the origin to everything except Front Door. Allow the AzureFrontDoor.Backend service tag in the origin's network security group, and check the X-Azure-FDID header in the app

Eradicate and recover

#Item
1Create a DDoS Network Protection plan: az network ddos-protection create --resource-group <rg> --name <plan>
2Link the plan to each virtual network with public IPs in scope: az network vnet update --resource-group <rg> --name <vnet> --ddos-protection-plan <plan> --ddos-protection true
3Or protect a single public IP with DDoS IP Protection: az network public-ip update --resource-group <rg> --name <ip> --ddos-protection-mode Enabled
4Add a metric alert on IfUnderDDoSAttack for each protected public IP
5Turn on DDoS diagnostic logs and WAF logs to the workspace before the next attack
6Move rules from temporary blocks to lasting rate limits, and remove country or range blocks that stop real customers
7Save the post-mitigation reports, flow logs and WAF counts with the case evidence
Watch out
  • DDoS Rapid Response and cost protection come with DDoS Network Protection only. DDoS IP Protection has neither.
  • Front Door rate limiting counts per fixed window of one or five minutes, and thresholds below about 200 requests per minute let some requests through. Application Gateway uses a sliding window and counts each listener separately.
  • Application Gateway rate limits keyed on ClientAddr count the connecting address. When traffic arrives through a proxy or CDN, key the rule on ClientAddrXFFHeader.

Microsoft Learn: DDoS Protection overview, SKU comparison, DDoS Rapid Response, metric alerts, view DDoS diagnostic logs, public IP address supported metrics, manage DDoS Protection and DDoS IP Protection with the Azure CLI, Application Gateway WAF rate limiting overview and configuration, WAF log analytics and WAF logs, Front Door WAF rate limiting and monitoring, Front Door origin security, Azure CLI reference for az network. Checked October 2026. Defender for Cloud alerts for DDoS Protection: checked October 2026.

Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.