One of the ways you could do something like this is through user-agent identfication attached to a custom vulnerability signature and assigning the vulnerability high enough that the traffic gets reset; just keep in mind that this isn't really a common use for this feature and you would likely have a large list of user-agent 'vulnerability' signature depending on what you are trying to do.
So for XP computers for example you would need to Pattern Match on http-req-headers and the pattern itself would be User-Agent:.+Windows NT 5\.|User-Agent:.+Windows XP
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!