mom: alerting on security events with a repeat window
yeah, the title is not very glamourous and probably doesn't make much sense. let me explain a bit on what i'm talking about.
let's say that you get an event for 529. one 529 probably doesn't mean very much or amount to anything since it's indicating a logon failure. i'm pretty sure that most people screw up putting in their password correctly the first time, second time, etc. now if you continue to get event 529 repeatedly, say for 30 minutes, for the same user, there might be a problem there, right? this is where setting up a repeat window is extremely helpful.
you'll need two rules to make this work, a consolidation rule and an event rule. fill in the following properties for both:
consolidation rule:
- provider name: security
- source: security
- event id: 529
- parameter 1: user field. leave it blank if you don't want to specify anything.
- parameter 2: domain group. same condition as parameter 1.
- consolidate: event number, source name, logging computer, parameter 1, parameter 2
- events must occur within: 1800 seconds (or 30 minutes)
the last field is your "window". essentially what you're doing is consolidating all the events that are picked up in a 30 minute period. don't worry, this will make sense as we go along.
event rule:
- provider name: security
- source: security
- event id: 529
- repeat count: is more than 10
the last field is how many times this event 529 is picked up in the 30 minute window before indicating that a problem exists. we can use repeat count in this event rule since the event that's issued after the 30 minute window (assuming there are any) will continue to keep up with how many times it occurred. if we break this down, if event 529 is detected more than 10 times in 30 minutes, alert me!
you can use this method anywhere that a repeated event in a time window indicates a problem. one last thing, if you're picking up security events, you'll want to enable guid resolution on your mom servers.
This is a cool idea and makes a lot of sense. To add to this, I would take into consideration the Password policy in your domain, defined through group policy as this might lock a user out after three bad password attempts which in turn might result in me lowering the repeat count originally proposed.
ReplyDeleteWhat might be just as important if the goal is to monitor for brute force login attacks (if that's what we classify this as) is to not alert on the agent at all because the majority of helpdesk calls are from users asking for a password reset or with account lockout issues. So instead, create a second consolidation rule on the management server that looks for similar events occuring for the same user on multiple MOM agents and then create an alert rule to run on the management server based on the repeat count of the consolidation rule which also runs on the Mgmt server.
you rock rory. if you do something like that, let me know. i'd love to see it.
ReplyDeletehttp://www.huntland.co.uk/Downloads/MOM/AdvancedConsolidation.html
ReplyDeleteYour a legend man.This worked like a charm
ReplyDeleteCan the same be achieved in OpsManager 2007? I don't see Consolidation Rules in OM2007. Any help is greatly appreciated.
ReplyDeleteThanks!
Rajesh
Can the same be achieved in OpsManager 2007? I don't see Consolidation Rules in OM2007. Any help is greatly appreciated.
ReplyDeleteThanks!
Rajesh