Narrowing down User-agent string for custom signatures

Reply
Highlighted
L0 Member

Narrowing down User-agent string for custom signatures

I have a couple of signatures for identifying hacker tools by the user-agent string (i.e. Hajiv).  I am currently using pattern-match with http-req-headers but I would like to get even narrower to ensure the signature is only triggering if Hajiv is in the user-agent field where now it may trigger if hajiv is anywhere in the request headers.  It doesn't false positive much but I would like to tighten it down. 

Tags (2)
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!