Microsoft Defender for Cloud Apps
Cloud and workloads

Integrate with Open Systems

In brief

The page now includes a licensing prerequisite and introductory instructions for deploying the Defender for Cloud Apps and Open Systems integration. Metadata was also updated.

What Defender admins need to know

Administrators deploying this integration should review the licensing requirements and deployment guidance.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Integrate Defender for Cloud Apps with Open Systems

Prerequisites

Before you begin, make sure you have the following licenses:

  • A valid license for Microsoft Defender for Cloud Apps
  • A valid license for Open Systems Secure Web Gateway

Deployment

To deploy the integration between Defender for Cloud Apps and Open Systems, follow these steps:

  1. Contact your Technical Account Manager in Open Systems to get the Microsoft Cloud App Security with Secure Web Gateway Configuration Guide to integrate the products.
  2. Investigate cloud apps discovered on your network. For more information and investigation steps, see Working with cloud discovery.
  3. Any app that you set as unsanctioned in Defender for Cloud Apps will be retrieved by Open Systems, and then automatically blocked. It can take up to one hour for the app to be blocked on the Open Systems Secure Web Gateway. If you need the app to be blocked immediately after tagging it as Unsanctioned, contact Open Systems customer support. For more information about unsanctioning apps, see Sanctioning/unsanctioning an app.