Threat signatures requiring ssl decryption

Reply
Highlighted
L1 Bithead

Threat signatures requiring ssl decryption

Is there a way to determine if a threat signature requires ssl decrypt in order to provide protection. I undertsnad this could have at least three posibilities being fully required, partially required, and not required. Using signature 14616 in content version 608 as an example, I cannot determine if I will ever see hits on this threat ID if I don't leverage ssl decrypt on the session. 

Tags (2)
L7 Applicator

Re: Threat signatures requiring ssl decryption

Non of the threat id's *require* that your traffic is decrypted, if it detects the signature then it will trigger. If it can't detect the signature because of the encryption then it will not trigger. 

L5 Sessionator

Re: Threat signatures requiring ssl decryption

Not a single signature will trigger on encrypted traffic. If you want to check encrypted traffic for threats, you MUST decrypt it. 

L7 Applicator

Re: Threat signatures requiring ssl decryption

santonic,

There is actually quite a few threat signatures that trigger based on packet header information

L5 Sessionator

Re: Threat signatures requiring ssl decryption

Yeah, signatures which check protocol compliance can still work.

But a short answer would be: if you want to check an encrypted session for possible threats, you have to decrypt it.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!