![]() ![]() 22% of organizations say that their security team has various problems related specifically to SSL/TLS (i.e. ![]() 22% of organizations say that their security and networking teams have some collaboration problems that impact their ability to inspect SSL/TLS traffic.This is an old and familiar story – the security team wants to inspect network traffic in-line while the networking team prefers tools that hang off a span port and run in promiscuous mode. 24% of organizations say that their networking team is suspicious of any technology that may impact performance or disrupt network traffic for a critical service.This is a major problem as it may be wise to inspect this traffic by sending it through AV engines, sandboxing appliances, web threat gateways, etc. 26% of organizations say that it is difficult to integrate SSL/TLS decryption and various packet filtering technologies.For example, ESG research indicates that: Given this, (87%) organizations surveyed decrypt and then inspect SSL/TLS traffic for signs of reconnaissance activity, malware, C2 communications, etc.ĭecrypting and inspecting SSL/TLS traffic is the right thing to do from a security perspective, but this activity comes with its share of operational and technical challenges. A majority (87%) of organizations surveyed as part of a recent ESG research project say they encrypt at least 25% of their overall network traffic today (note: I am an ESG employee)ĬISOs realize that network encryption is a mixed blessing as it protects the confidentiality/integrity of network traffic but also represents a new threat vector. As I’ve mentioned in several recent blogs, enterprise organizations are encrypting more and more of their network traffic. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |