Zscaler 블로그

Zscaler 블로그의 최신 업데이트를 이메일로 받아보세요

Products & Solutions

To inspect or to not inspect SSL: Why is this even a question?

image
MIKE RUIZ
April 20, 2017 - 3 분 소요
>To inspect or to not inspect SSL: Why is this even a question?

Over half of the Internet today uses SSL (TLS) to encrypt traffic between your application and the server on the internet.  By the end of 2016, 80% of all traffic across Google properties was encrypted, and here at Zscaler, between 55-60% of all traffic that traverses our cloud is encrypted.

This is meant to keep your private information private.  That also means that you can be infected by malware hiding in SSL traffic, and even use SSL to communicate with C&C servers.  You can look at the news websites at any given moment and see the latest security breach.  With the risk to your data, your business, and your reputation how can you afford to let hackers remain hidden and private?  You can’t.

I’m a privacy and an encryption advocate. However, given the ease with which bad actors can obtain, and then misuse, SSL certificates, it’s vitally important that businesses inspect this traffic.  That may sound like tricky thing to balance with the fact that I’m suggesting you must inspect traffic inside of that encryption to protect your very survival. In fact, fifty-four percent of the threats that we stop at Zscaler are hiding inside encrypted traffic; you can read our recent research on the threats that hid in SSL traffic .  If you’re interested in security you’ve probably noticed the CERT notice and blog about the risks of SSL inspection.  I can sum it up reasonably well in saying “if you implement inspection poorly you could create new exposure”, or perhaps even better, my favorite phrase “ you can configure anything to not work.”

If SSL inspection is crucial to protect the security of your enterprise, how do you also protect the privacy of your data and of your employees?  Here are some simple guidelines to protect everyone:

  • Ensure your proxy has some key capabilities:

    • Block undecryptable traffic

    • Block traffic from sites with untrusted or revoked certificates

    • Block weak and deprecated encryption ciphers while adding modern strong ciphers with a phased in approach

    • Have sufficient capacity to inspect ALL traffic while opting out per your business policy specific sites, applications, domains out of SSL inspection

    • Scale your proxy so it can inspect scan and encrypt traffic on the same box or service

  • Ensure you have key policies and procedures:

    • Centralized administration of scanning policies and settings to avoid misconfigurations letting malware through

    • Lock down and periodically verify the trusted root certificate list on devices, or provide the same off-network protection for those devices that you do when they're on network.

    • Limited access to the network including appliances, credentials, switches, routers, etc.

As the world moves nearly ubiquitously to SSL/TLS your security posture must also adapt. Proper classification and maintenance of IP and Hostname lists are useful tools in your defense strategy; the only question around SSL inspection is how soon you can get started.

form submtited
읽어주셔서 감사합니다

면책 조항: 이 블로그 게시물은 정보 제공만을 목적으로 Zscaler에서 작성하였으며, 정확성, 완전성 또는 신뢰성에 대한 어떠한 보증도 없이 "있는 그대로" 제공됩니다. Zscaler는 제공된 정보를 기반으로 수행된 조치나 오류 또는 누락에 대해 어떠한 책임도 지지 않습니다. 이 블로그 게시물에 링크된 제3자 웹사이트나 리소스는 편의를 위해서만 제공되며, Zscaler는 해당 웹사이트의 콘텐츠나 관행에 대해 책임을 지지 않습니다. 모든 콘텐츠는 예고 없이 변경될 수 있습니다. 이 블로그에 접속함으로써 귀하는 본 약관에 동의하며 귀하의 필요에 따라 정보를 확인하고 사용할 전적인 책임이 귀하에게 있음을 인정합니다.

Zscaler 블로그의 최신 업데이트를 이메일로 받아보세요

양식을 제출함으로써 귀하는 당사의 개인정보 보호정책에 동의하는 것입니다.