How do I integrate Zscaler DLP with Symantec DLP via ICAP?

Go with Symantec DLP. If you have any questions let me know @ Ejaz.hassan@risetechno.com. 

Data loss prevention (DLP) is an important security technology that can help organizations protect their data from unauthorized access, misuse, and data loss. DLP solutions are designed to detect data breaches and alert companies about the possible security risks associated with data storage. They can be used to block data transfers or restrict access to data stored in cloud-based data stores. In addition, DLP solutions can be used to monitor data usage and detect malicious behavior such as data theft or data leakage. By implementing data loss prevention technology, companies can protect their data from external threats and unauthorized access. When it comes to Email Cloud Security, Symantec DLP, Proofpoint DLP, and Microsoft Purview DLP are all strong contenders. But which solution is the right one for you? Well, that depends on your specific needs. If you prioritize ease of use and scalability in your Email Cloud Security solutions, then Symantec DLP is the right choice. If, on the other hand, you value data privacy and protection then Proofpoint DLP is a better option. Finally, Microsoft Purview DLP stands out for its comprehensive analytics tools that give users greater insight into their Email Cloud Security performance. So which Email Cloud Security solution do you pick? Choose wisely! It could make all the difference.

Zscaler will protect PII for all users regardless of their geolocations as well it will simplify compliance requirement's by eliminating complexity of legacy systems and securing your cloud data across all channels data in motion, at rest, and across endpoints and clouds.

It really comes down to the Regex that's being used from Zscaler's DLP. That's the one area that we find technical limitations because the rest of the industries use an RE2, and Regex and Zscaler just aren't there. It's not because of the technology and they can't code it. It's because of the cost of these actual Regex strings from a query perspective. There's limited flexibility from a Regex perspective as far as data matching and expanding your DLP dictionaries and libraries. In the next release, I would like to see RE2 Regex supported.