Custom vulnerability object trigger

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Custom vulnerability object trigger

L1 Bithead

Trying to use a custom vulnerability object to raise a threat alert when a user directly enters a request for access to an IPv4 address . eg http://12.34.56.78  .  Ive created a object , with a pattern of (.*((?:\d{1,3}\.){3}\d{1,3})) and applied it to a vulnerability profile that is applied to a bunch of rules .   I can see the rules triggered but the vulnerability is not logging as a threat , ive also had the converse where a normal URL eg http://www.xyz.com is being flagged as a vulnerability as a false positive .    Anyone had success (consistently) with custom vulnerability objects using regex patterns ?    the field im using the regex pattern against is http-req-host-headers

0 REPLIES 0
  • 71 Views
  • 0 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!