Data loss prevention incident forwarding

1. A cloud-based security system comprising:

a plurality of enforcement nodes connected to one another, each of the plurality of enforcement nodes comprising one or more hardware processors and memory; a central authority connected to the plurality of enforcement nodes; and

a Data Loss Prevention (DLP) service executed between the plurality of enforcement nodes, wherein the DLP service includes one or more DLP rules based on one or more DLP engines for a tenant, and wherein, for the DLP service,

a first enforcement node is configured to monitor traffic of a user of the tenant, detect a DLP rule violation based on the one or more DLP rules, and forward DLP incident information to a second enforcement node, wherein the first enforcement node is on a different cloud than the second enforcement node, and

the second enforcement node is configured to transmit the DLP incident information to a server for the tenant, including both DLP triggering content that cause the DLP rule violation and DLP scan metadata, Wherein the second enforcement node is on a cloud utilized by the DLP service to send communications to the server.

2. The cloud-based security system of claim 1 , wherein the first enforcement node and the second enforcement node are configured to forward the DLP incident information and not persist the DLP triggering content in memory.

3. The cloud-based security system of claim 1 , wherein the DLP triggering content includes all or a portion of data that triggered the DLP rule violation so that the tenant can determine remediation.

4. The cloud-based security system of claim 1 , wherein the DLP scan metadata includes a plurality of a DLP dictionary, a DLP engine, a search score, a trigger, a time, a user, and a Uniform Resource Locator (URL).

5. The cloud-based security system of claim 1 , wherein the DLP rule violation is a violation of an Exact Data Match (EDM) index provided to the cloud-based security system as a hash signature so that underlying data is not accessible by the cloud-based security system, and wherein the triggering content includes the hash signature which is converted back to the underlying data at the server for the tenant.

6. The cloud-based security system of claim 1 , wherein the server includes an Internet Content Adaptation Protocol (ICAP) server that is one of located on-premises with the tenant and located in a cloud system and connected securely to another server located on-premises with the tenant.

7. The cloud-based security system of claim 1 , wherein the first enforcement node is configured to monitor the traffic that includes any of Secure Sockets Layer (SSL) traffic and Transport Layer Security (TLS) traffic as a proxy.

8. A non-transitory computer-readable storage medium having computer-readable code stored thereon for programming one or more processors at a first enforcement node on a first cloud in a cloud-based security system to perform steps of:

monitoring traffic of a user of a tenant;

implementing Data Loss Prevention (DLP) service for the tenant, wherein the DLP service includes one or more DLP rules based on one or more DLP engines for the tenant;

analyzing the traffic via the DLP service;

detecting a DLP rule violation based on the one or more DLP rules; and

forwarding DLP incident information to a second enforcement node that is configured to transmit the DLP incident information to a server for the tenant, including both DLP triggering content that cause the DLP rule violation and DLP scan metadata, wherein the second enforcement node is on a second cloud utilized by the DLP service to send communications to the server.

9. The non-transitory computer-readable storage medium of claim 8 , wherein the first enforcement node and the second enforcement node are configured to forward the DLP incident information and not persist the DLP triggering content in memory.

10. The non-transitory computer-readable storage medium of claim 8 , wherein the DLP triggering content includes all or a portion of data that triggered the DLP rule violation so that the tenant can determine remediation.

11. The non-transitory computer-readable storage medium of claim 8 , wherein the DLP scan metadata includes a plurality of a DLP dictionary, a DLP engine, a search score, a trigger, a time, a user, and a Uniform Resource Locator (URL).

12. The non-transitory computer-readable storage medium of claim 8 , wherein the DLP rule violation is a violation of an Exact Data Match (EDM) index provided to the cloud-based security system as a hash signature so that underlying data is not accessible by the cloud-based security system, and wherein the triggering content includes the hash signature which is converted back to the underlying data at the server for the tenant.

13. The non-transitory computer-readable storage medium of claim 8 , wherein the server includes an Internet Content Adaptation Protocol (ICAP) server that is one of located on-premises with the tenant and located in a cloud system and connected securely to another server located on-premises with the tenant.

14. The non-transitory computer-readable storage medium of claim 8 , wherein the first enforcement node is configured to monitor the traffic that includes any of Secure Sockets Layer (SSL) traffic and Transport Layer Security (TLS) traffic as a proxy.

15. A method implemented by a first enforcement node on a first cloud comprising:

monitoring traffic of a user of a tenant;

implementing Data Loss Prevention (DLP) service for the tenant, wherein the DLP service includes one or more DLP rules based on one or more DLP engines for the tenant;

analyzing the traffic via the DLP service;

detecting a DLP rule violation based on the one or more DLP rules; and

forwarding DLP incident information to a second enforcement node that is configured to transmit the DLP incident information to a server for the tenant, including both DLP triggering content that cause the DLP rule violation and DLP scan metadata, wherein the second enforcement node is on a second cloud utilized by the DLP service to send communications to the server.

16. The method of claim 15 , wherein the first enforcement node and the second enforcement node are configured to forward the DLP incident information and not persist the DLP triggering content in memory.

17. The method of claim 15 , wherein the DLP triggering content includes all or a portion of data that triggered the DLP rule violation so that the tenant can determine remediation, and

wherein the DLP scan metadata includes a plurality of a DLP dictionary, a DLP engine, a search score, a trigger, a time, a user, and a Uniform Resource Locator (URL).

18. The method of claim 15 , wherein the DLP rule violation is a violation of an Exact Data Match (EDM) index provided to the cloud-based security system as a hash signature so that underlying data is not accessible by the cloud-based security system, and wherein the triggering content includes the hash signature which is converted back to the underlying data at the server for the tenant.

19. The method of claim 15 , wherein the server includes an Internet Content Adaptation Protocol (ICAP) server that is one of located on-premises with the tenant and located in a cloud system and connected securely to another server located on-premises with the tenant.

20. The method of claim 15 , wherein the first enforcement node is configured to monitor the traffic that includes any of Secure Sockets Layer (SSL) traffic and Transport Layer Security (TLS) traffic as a proxy.