Tofsee TLS Fingerprint Detection

[Stephen_Elliott]

Hi all,

Since the moment we updated our threat database to 8204-5736 we see THOUSANDS of 'Tofsee TLS Fingerprint Detection' threat matches.

I assume they are false positives? Anyone else seeing the same?

It's skewing our monitoring stats significantly so I may need to create an exception.

Thanks.

[MarkShanks]

@LRichman 

Are you still experiencing hits for "Non-RFC Compliant SSL Traffic on Port 443?"  Threat ID 56112.  I have seen a large uptick in this activity since Palo Alto updated the threat on 11-19-2019.  Thanks.

[LRichman]

@MarkShanks 

We are still experiencing hits on that threat signature across multiple firewalls at this time. Due to the informational severity and recent holidays, I have not had a chance to investigate it much at all. I will probably end up opening a support case for clarification on this matter.

[Stephen_Elliott]

Yep, we're seeing continual 'Non-RFC Compliant SSL Traffic on Port 44' alerts too, but nothing like the volumes seen on the Tofsee threat.

[jlieberman]

I am seeing lots of alerts for 

Name: Non-RFC Compliant SSL Traffic on Port 443

Unique Threat ID: 56112

to 31.13.70.50 which belongs to Facebook.  However, the device (android mobile phone) that is causing the alerts does not have facebook app installed.

[hisingh]

Hello 

Few Non-RFC Complaint signatures that was introduced in late last year and non-RFC Compliant SSL Traffic on Port 443(56112) is one of them. Please note that the main aim behind the signature TID 56112 is to detect suspicious and non-RFC compliant SSL traffic on port 443 or applications sending non-SSL traffic using port 443 or indicate possible malicious activity. 

You can capture the facebook traffic from the android device on your Firewall and check the traffic SSL protocol.

Best

Himani