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 對任何錯誤或遺漏,或基於所提供的資訊而採取的任何行動不承擔任何責任。本部落格文章中連結的任何第三方網站或資源僅為方便起見而提供,Zscaler 對其內容或做法概不負責。所有內容如有變更,恕不另行通知。存取此部落格,即表示您同意這些條款,並承認您有責任自行驗證並根據您的需求適當使用資訊。

訂閱 Zscaler 部落格,第一時間獲取最新資訊!

提交此表格即表示您同意我們的隱私權政策。