why are there duplicated threats (protections) ?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

why are there duplicated threats (protections) ?

L0 Member

Hello,

Browsing on the list of threats, i see many threats that repeat themself, only with different ID.

What does that mean?

6 REPLIES 6

L4 Transporter

Hi,

We differentiate sig by Threat ID. Would you list out some examples that you are seeing different ID but same sig description?

Jones

Detail

31826

    HTTP JavaScript Obfuscation Detected     low    

Detail

31825

    HTTP JavaScript Obfuscation Detected     low    

Hi all,

 

Running 7.0.9 with App/Thr version 660-3840.

 

ID: 40021 MS-RDP Brute Force Attempt

ID: 40026 MS-RDP Brute Force Attempt

 

In this situation, at this moment our system is not detecting MS-RDP attemps.

 

Last detection was at 11th January 17, just before update App/Thr file.

 

¿Are there any way to inicializate vulnerability protection any solution to this?

 

Thanks in advance.

Do you have more news about this issue ???

 

regards

@SChaouche,

This is usually done to avoid signature issues. There may be multiple different signatures for some of the same threats that get seperated out due to how the signatures that the threats actually trigger on would interact with eachother. 

there is no 40026 anymore.

 

Regards

 

  • 3702 Views
  • 6 replies
  • 0 Likes
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!