Stunnel exe install#
Stunnel exe update#

stunnel-key with the name of the newly created key.

cert.pem with the name of your certificate.

key.pem with the name of your private key.

Or, on the stunnel server, use the following OpenSSL commands to generate a private key and a self-signed certificate.

Then copy the keys to the server you prepared for the stunnel installation.

Use your certificate management server to create an TLS certificate on your ICAP server.

You'll create a certificate in a later step.Ĭreate a certificate in one of the following ways: (default installation)ĭuring installation, don't create a new self-signed certificate.

Stunnel exe install#

Install stunnel on Windowsĭownload the latest Windows Server installation (This application should work on any recent Windows Server edition). If you're using Linux, you can use your Linux distribution manager to install it. Refer to the stunnel website for details about the types of servers that support stunnel installation.

A server - either a Windows Server or a Linux server based on a major distribution.

While highly recommended, this step is optional and can be skipped on test workloads.

Destination TCP port: As defined in your network.

Destination address(es): one or two IP address of the stunnel connected to the external ICAP server that you'll configure in the next steps.

Source addresses: Refer to Connect apps, under Prerequisites.

In order for Defender for Cloud Apps to send data through your stunnel to your ICAP server, open your DMZ firewall to the external IP addresses used by Defender for Cloud Apps with a dynamic source port number. The ICAP server and stunnel must be deployed together on the same network to make sure the traffic is encrypted. Deploying in other environments may result in degraded performance due to higher latency and lower throughput. However, other options including other Clouds and On-Premises deployment are supported. Since Defender for Cloud Apps runs in Azure, a deployment in Azure yields improved performance. Responses are sent back to Defender for Cloud Apps over the stunnel where it's used by the policy to determine subsequent actions such as notifications, quarantine, and sharing control. If external DLP scan is applied, the file is sent over the secure tunnel to the customer environment where it's relayed to the ICAP appliance for the DLP verdict: allowed/blocked. Architectureĭefender for Cloud Apps scans your cloud environment and based on your file policy configuration, decides whether to scan the file using the internal DLP engine or the external DLP. This guide provides the steps necessary for configuring the ICAP connection in Defender for Cloud Apps and the stunnel setup to secure communication through it. The stunnel setup provides TLS encryption functionality to your data as it travels between your DLP server and Defender for Cloud Apps.

To secure ICAP for transmission of your data, it's required to set up a secure TLS tunnel (stunnel) between your DLP solution and Defender for Cloud Apps. Integration is accomplished by using the standard ICAP protocol, an http-like protocol described in RFC 3507. The platform exports easy-to-use interfaces including REST API and ICAP, enabling integration with content classification systems such as Symantec Data Loss Prevention (formerly Vontu Data Loss Prevention) or Forcepoint DLP. Microsoft Defender for Cloud Apps can integrate with existing DLP solutions to extend these controls to the cloud while preserving a consistent and unified policy across on-premises and cloud activities. For more information about these changes, see Microsoft Defender for Cloud Apps in Microsoft 365 Defender. Microsoft 365 Defender will be the home for monitoring and managing security across your Microsoft identities, data, devices, apps, and infrastructure. This will simplify workflows, and add the functionality of the other Microsoft 365 Defender services. The Microsoft 365 Defender portal allows security admins to perform their security tasks in one location. Microsoft Defender for Cloud Apps is now part of Microsoft 365 Defender. To learn more about the recent renaming of Microsoft security services, see the Microsoft Ignite Security blog. For more information about the change, see this announcement.

Stunnel exe update#

In the coming weeks, we'll update the screenshots and instructions here and in related pages. It's now called Microsoft Defender for Cloud Apps. We've renamed Microsoft Cloud App Security.