Vulnerabilities / Threats

8/31/2016
04:35 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

More Than 40% Of Attacks Abuse SSL Encryption

New report shows risk of not inspecting encrypted packets.

There’s an important caveat about encrypted traffic from new research released this week: Encryption works so well that hackers are using it as cover.

A new study from A10 and the Ponemon Institute found that 80% of respondents say their organizations have been the victim of a cyberattack or malicious insiders in the past year -- and 41% of the attacks have used encryption to evade detection. In addition, 75% say malware hidden within encrypted traffic is a risk to their organizations.

At issue: The report found that SSL encryption not only hides data from would-be hackers but also from common security tools.

“Hackers are using SSL encryption to slide by standard perimeter defenses,” says Chase Cunningham, director of cyber operations at A10 Networks.

Cunningham says companies need to start thinking about using technologies that can inspect SSL packets and quarantine the bad or malicious packets. He adds that it’s going to become even more important as organizations move encrypted data out to the cloud – companies need to know if all those encrypted packets out in the cloud are secure.

The three main reasons organizations don’t decrypt encrypted traffic, according to the report: lack of enabling security tools (47%), insufficient resources (45%), and performance degradation (45%). 

Another 53% of the respondents admit that their security solutions are collapsing under growing SSL bandwidth demands and key lengths.

Kevin Bocek, vice president of security strategy and threat intelligence at Venafi, says the A10 research validates what they’ve been saying for the past several months about the dangers lurking inside encrypted traffic. He points out three aspects to inspecting encrypted traffic.

First, companies must focus on key management for inbound traffic. Bocek says they need to know where the keys are and use automated tools that keep them regularly updated.

Second, companies need to set up a trusted authority for outbound traffic so when the system initiates a new connection, a new certificate is created. Bocek says most security tools have these kinds of capabilities.

Finally, the same kind of key management a company sets up for inbound traffic must be used for internal (East-West) traffic. “Basically for East-West traffic the company controls the end, whether it’s one data center to another data center or one network segment to another network segment,” he adds.

Bottom line: Security managers need to understand that encrypted packets represent a legitimate threat that must be managed and inspected regularly. 

Related Content:

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
theb0x
50%
50%
theb0x,
User Rank: Ninja
9/2/2016 | 7:53:54 PM
Re: Encryption is a double edge sword
Broken encryption algorithms can be a huge advantage in obtaining a better understanding of the metrics of the attack itself. Ssl injection and stripping can be performed to reverse engineer the attack vector to mitigate the risk.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
9/2/2016 | 10:58:32 AM
Re: Encryption is a double edge sword
Agreed but still better than no encryption at all.
theb0x
100%
0%
theb0x,
User Rank: Ninja
9/1/2016 | 9:22:25 AM
Re: Encryption is a double edge sword
SSL / TLS is still broken.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
8/31/2016 | 9:17:44 PM
Encryption is a double edge sword
The same proponents for encryption to secure data are also the same proponents to be utilized for malicious intent.
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Is Threat Intelligence Garbage?
Chris McDaniels, Chief Information Security Officer of Mosaic451,  5/23/2018
More Than Half of Users Reuse Passwords
Curtis Franklin Jr., Senior Editor at Dark Reading,  5/24/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Shhh!  They're watching... And you have a laptop?  
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11440
PUBLISHED: 2018-05-25
Liblouis 3.5.0 has a stack-based Buffer Overflow in the function parseChars in compileTranslationTable.c.
CVE-2013-3018
PUBLISHED: 2018-05-24
The AXIS webapp in deploy-tomcat/axis in IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1.2 and 7.2.0 through 7.2.1.4 allows remote attackers to obtain sensitive configuration information via a direct request, as demonstrated by happyaxis.jsp. IBM X-Force ID: 84354.
CVE-2013-3023
PUBLISHED: 2018-05-24
IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1.2 and 7.2.0 through 7.2.1.4 might allow remote attackers to obtain sensitive information about Tomcat credentials by sniffing the network for a session in which HTTP is used. IBM X-Force ID: 84361.
CVE-2013-3024
PUBLISHED: 2018-05-24
IBM WebSphere Application Server (WAS) 8.5 through 8.5.0.2 on UNIX allows local users to gain privileges by leveraging improper process initialization. IBM X-Force ID: 84362.
CVE-2018-5674
PUBLISHED: 2018-05-24
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader before 9.1 and PhantomPDF before 9.1. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw...