Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article explains how to configure the integration between Microsoft Defender for Cloud Apps and Zscaler, including prerequisites and setup steps. If you work with both Microsoft Defender for Cloud Apps and Zscaler, integrate the two to enhance your cloud discovery experience. Zscaler, as a standalone cloud proxy, monitors your organization's traffic and enables you set policies for blocking transactions. Together, Defender for Cloud Apps and Zscaler provide the following capabilities:
- Seamless cloud discovery: Use Zscaler to proxy your traffic and send it to Defender for Cloud Apps. Integrating the two services means that you don't need to install log collectors on your network endpoints to enable cloud discovery.
- Automatic blocking: After configuring the integration, Zscaler's block capabilities are automatically applied on any apps you set as unsanctioned in Defender for Cloud Apps.
- Enhanced Zscalar data: Enhance your Zscaler portal with the Defender for Cloud Apps risk assessment for leading cloud apps, which can be viewed directly in the Zscaler portal.
Prerequisites
Before you deploy the Zscaler integration, make sure you have the following prerequisites:
- A valid license for Microsoft Defender for Cloud Apps, or a valid license for Microsoft Entra ID P1
- A valid license for Zscaler Cloud 5.6
- An active Zscaler NSS subscription
Deploy the Zscaler integration
Perform the following steps to deploy and complete the Zscaler integration:
In the Zscalar portal, configure the Zscaler integration for Defender for Cloud Apps. For more information, see the Zscaler documentation.
In Microsoft Defender XDR, complete the integration with the following steps:
Select Settings > Cloud apps > Cloud discovery > Automatic log upload > +Add data source.
In the Add data source page, enter the following settings:
- Name = NSS
- Source = Zscaler QRadar LEEF
- Receiver type = Syslog - UDP
For example:
Note
Make sure the name of the data source is NSS. For more information about setting up NSS feeds, see Adding Defender for Cloud Apps NSS Feeds.
To view a sample discovery log, select View sample of expected log file > Download sample log. Make sure that the downloaded sample log matches your log files.
After completing the integration steps, any app that you set as unsanctioned in Defender for Cloud Apps is pinged by Zscaler every two hours, and then blocked according to the blocking settings configured in your Zscaler portal. For more information, see Sanctioning/unsanctioning an app.
Continue by investigating cloud apps discovered on your network. For more information and investigation steps, see Working with cloud discovery.
Next steps
If you run into any problems, we're here to help. To get assistance or support for your product issue, please open a support ticket.
