Secure Developer Workflows Without Slowing Innovation

Over 86% of all threats are delivered over encrypted traffic: not inspecting traffic in developer environments increases risk and leaves your organization vulnerable. Moreover, development teams release often and rapidly so your organization remains competitive and gains market share—but that speed can also lead to an oversight that causes a security incident. In this context, inspecting traffic and new files before they are embedded in the developer’s code base is paramount to maintaining a strong, resilient security posture.

In the past integrating encrypted traffic inspection has proven problematic for development teams: their code does not reference the correct certificate store or they design their app to employ “certificate pinning,” a security technique that prevents man-in-the-middle (MITM) attacks and secures access to your organization’s applications. Unfortunately, both scenarios prevent traffic TLS/SSL inspection via proxy.

Zscaler now provides the means for your security or IT teams to empower developer teams with scalable, policy-based TLS/SSL inspection or, in the case of certificate-pinned apps, easily bypass inspection for this category of apps.

Outright blocking means your developers can’t directly introduce risk during development,  prior to releasing new code to production in your environment. That said, without other DLP policy they could inadvertently introduce third-party code into the overall code base, resulting in malicious code with a backdoor or other threat being introduced into a production app. 

From a productivity standpoint, blocking access to other developer resources puts your software engineers at a competitive disadvantage: with ZIA’s SSL/TLS inspection integrated with their workflows, they can still remain competitive while preventing threats from compromising your organization’s security.