Blog Post

Microsoft Sentinel Blog
2 MIN READ

What’s new: Azure DDoS Protection connector in Public Preview for Azure Sentinel

Sarah_Young's avatar
Sarah_Young
Icon for Microsoft rankMicrosoft
Sep 09, 2020

This installment is part of a broader series to keep you up to date with the latest features in Azure Sentinel. The installments will be bite-sized to enable you to easily digest the new content.

 

Even more Azure Sentinel connector news for you! If you are using Azure DDoS Standard Protection, you can now ingest this via our connector into your Azure Sentinel workspace.

 

In addition to the core DDoS protection in the Azure platform, Azure DDoS Protection Standard provides advanced DDoS mitigation capabilities against network attacks. It's automatically tuned to protect your specific Azure resources. Protection is simple to enable during the creation of new virtual networks. It can also be done after creation and requires no application or resource changes.

 

Connecting Azure DDoS Protection Standard logs to Azure Sentinel enables you to view and analyze this data in your workbooks, query it to create custom alerts, and incorporate it to improve your investigation process, giving you more insight into your platform security.

 

 

 

How to enable Azure DDoS Protection log ingestion in Azure Sentinel

 

Prerequisite - You must have a configured Azure DDoS Standard protection plan.

 

1. From the Azure Sentinel navigation menu, select Data connectors.

 

2. Select Azure DDoS Protection from the data connectors gallery, and then select Open Connector Page on the preview pane.

 

3. Enable Diagnostic logs on all the firewalls whose logs you wish to connect:

a. Select the Open Diagnostics settings > link and choose a Public IP Address resource from the list.

 

b. Select + Add diagnostic setting.

c. In the Diagnostics settings screen

  • Enter a name in the Diagnostic setting name field.
  • Mark the Send to Log Analytics check box. Two new fields will be displayed below it. Choose the relevant Subscription and Log Analytics Workspace (where Azure Sentinel resides).
  • Mark the check boxes of the rule types whose logs you want to ingest. We recommend DDoSProtectionNotifications, DDoSMitigationFlowLogs, and DDoSMitigationReports.

d. Click Save at the top of the screen. Repeat this process for any additional firewalls (public IP addresses) for which you have enabled DDoS protection.

 

4. To use the relevant schema in Log Analytics for Azure DDoS Protection alerts, search for AzureDiagnostics. Here's an example query below:

 

AzureDiagnostics 
| where ResourceType == "PUBLICIPADDRESSES"
| sort by TimeGenerated

 

And that’s it! You will now have Azure DDoS Standard logs connected to your Sentinel workspace.

 

 

Get Started Today!

Try out the new connector and let us know your feedback using any of the channels listed in the Resources.

 

You can also contribute new connectors, workbooks, analytics and more in Azure Sentinel. Get started now by joining the Azure Sentinel Threat Hunters GitHub community and follow the guidance.

 

Updated Nov 03, 2021
Version 8.0
  • Thanks Anthony_Roman for the reply.
    I was able to find the diagnostics via the Azure Monitor.

    If we only see logs when a potential attack is detected, how do we confirm that the connector with Azure Sentinel is in working properly?

  • caiodaruizcorrea the diagnostic settings are best done centrally via Azure Monitor rather than on each individual Public IP. You are right that the Standard SKU IPs do not have diagnostic settings in the UI, but they do exist. To your last question, you will only see logs when a potential attack is detected. This will also trigger an alert in Azure Security Center if you use that.

  • Sarah_Young We have enabled the diagnostics on some of the public IP addresses but not all of them have the option to do so.

     

    Can you please advise if there are any limitations?

    Does it need to be enabled on all or just some IPs, and what type of IPs are supported?

     

    I logged a ticket with support and apparently even on the Microsoft lab for standard SKU public IP it is not showing the diagnostics option either.

     

    Even for the non standard SKU IPs, I do not see any logs getting generated and saved in the log analytics workspace. Is it only when there is a DDoS incident detected?

     

    Thanks,
    Caio