Use Panorama to Forward Logs to Azure Security Center

Table of Contents

Use Azure Security Center Recommendations to Secure Your Workloads

Deploy the VM-Series Firewall on Azure Stack

Use Panorama to Forward Logs to Azure Security Center

Use Panorama templates and device groups to forward VM-Series firewall logs to Azure Security Center

Where Can I Use This?	What Do I Need?
Microsoft Azure Microsoft Azure Stack Azure® Marketplace Azure China Marketplace Azure Government Marketplace	VM-Series License (PAYG or BYOL) VM-Series plugin Panorama Panorama plugin for Azure

If you're using Panorama to manage your firewalls, you can use templates and device groups to forward firewall logs to the Azure Security Center. With the default Azure Security Center Log Forwarding profile, Threat, and WildFire Submissions log of low, medium, high, or critical severity generated on the firewall is displayed as security alerts on the Azure Security Center dashboard. So that you can focus and triage alerts more efficiently, you can set up granular log filters to only forward logs of interest to you, or forward high and critical severity logs only. You can also selectively attach the Log Forwarding profile to a few Security policy rules based on your applications and security needs.

To enable the Azure Security Center integration from Panorama, use the following workflow.

Add the firewall as a managed device on Panorama.
From Panorama, create a template and a device group to push log forwarding settings to the firewalls that will be forwarding logs to the Azure Security Center.
Specify the log types to forward to the Logging Service.
The way you enable forwarding depends on the log type. For logs that are generated based on a policy match, you use a Log Forwarding profile within a device group, and for other log types you use the Log Settings configuration within a template.
1. Configure forwarding of system, configuration, User-ID, and HIP Match logs.
  Select DeviceLog Settings.
  Select the Template that contains the firewalls you want to forward logs to the Logging Service.
  For each log type that you to forward to the Logging Service, Add a match list filter. Give it a Name, optionally define a Filter.
  Add Built-in Actions and enter a Name. The Azure-Security-Center-Integration action will be autoselected. Click OK.
  
  Click OK.
2. Configure forwarding of all other log types that are generated when a policy match occurs such as Traffic, Threat, WildFire Submission, URL Filtering, Data Filtering, and Authentication logs. To forward these logs, you must create and attach a Log Forwarding profile to each policy rule for which you want to forward logs.
  Select the Device Group, and then select ObjectsLog Forwarding to Add a profile. In the Log Forwarding profile match list, add each log type that you want to forward.
  Select Add in Built-in Actions to enable the firewalls in the device group to forward the logs to the Azure Security Center.
  
  Create basic security policy rules in the device group and select Actions to attach the Log Forwarding profile you created for forwarding logs to the Azure Security Center. Until the firewall has interfaces and zones and a basic Security policy, it won't let any traffic through, and only traffic that matches a Security policy rule will be logged (by default).
  For each rule you create, select Actions and select the Log Forwarding profile that allows the firewall to forward logs to the Azure Security Center.
Commit your changes to Panorama and, push them to the template and device group you created.
Verify that the firewall logs are being forwarded to the Azure Security Center.
1. Log in to the Azure portal, select the Azure Security Center.
2. Verify that you can see firewall logs as Security alerts on the Azure Security Center dashboard.