Meltdown and Spectre Vulnerability

Reply
Highlighted
djr
L3 Networker

Re: Meltdown and Spectre Vulnerability

Default Palo Action on any new threat = Alert 

 

...as far as I can tell.   I have always presumed it is deliberate, but I don't know how long they leave it before they feel confident enough to block.  We have spotted some very mature Critical or High threats which are still only "alert" as default action. 

L7 Applicator

Re: Meltdown and Spectre Vulnerability

Hello,

The defaults are set to alert as a safety measure. WHat we do is copy the default Vulnerability policies and manuall set the action based on severity. I.e. anything medium and higher is blocked or reset, etc. This way when new signatures come out, they may be classified as high or critical, but our policies are set so that they will be blocked in some fashion.

 

Hope that makes sense.

 

Regards,

L1 Bithead

Re: Meltdown and Spectre Vulnerability

So you override the default actions for those severities?  I have that configuration in place in some places, but the way the default actions as described to my be an SE from Palo Alto which got me thinking about that approach.  He said something to the effect that default action is evaluated very differently than severity.  They are basically set based on confidence that there will be no false positives.

 

Another example he gave was the Poodle signature which simply detected any SSLv3 - which you certainly wouldn't want to block, particularly at that time.  Granted that was an informational signature, not medium or higher, but you can look at Vulnerability Protection signatures '( severity contains 'critical' ) and ( action contains 'alert' )' and see 1704 signatures (over 1/10th) where the default action is alert (and one that is allow.)  

 

 

Do you even alert below medium?  All I have investigated in those severities have ended up on our whitelist so far.

djr
L3 Networker

Re: Meltdown and Spectre Vulnerability

We do drop/reset Critical and High because we have seen serious vulnerabilities being ignored because they are alert only, but we had worked out that the PAN approach was more based on confidence.  That makes lots of sense, but only if the action changes after a few days or so when they have worked out how reliable the detection is.  We have found that they stay on alert for months which just gives too large a window for attack.

 

We do alert everything but our logs are huge!  It's a good point maybe we don't need to, we just tend to log as much as possible so we can see what is going on.

L7 Applicator

Re: Meltdown and Spectre Vulnerability

Hello @chyates,

Yes, I am actually thinking of just performing a server side reset on my external facing zones so my servers connection gets reset but the attackers does not so it keeps their session open :).

 

 

image.png

 

Cheers!

L0 Member

Re: Meltdown and Spectre Vulnerability

How are IPS signatures possible for these attacks. Can anyone tell me what is the detection criteria ?

L5 Sessionator

Re: Meltdown and Spectre Vulnerability

While we do not disclose the specific logic our IPS signatures utilize due to the fact that this is considered proprietary information, I can say that our IPS signatures are used to detect instances wherein someone has weaponized a Meltdown or Spectre attack using malicious javascript or something similar.

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!