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.
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.
I am seeing lots of alerts for
Name: Non-RFC Compliant SSL Traffic on Port 443
Unique Threat ID: 56112
to 184.108.40.206 which belongs to Facebook. However, the device (android mobile phone) that is causing the alerts does not have facebook app installed.
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.
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!