Skip to main content

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.

Comments

  1. 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.

    What 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.

    ReplyDelete
  2. you rock rory. if you do something like that, let me know. i'd love to see it.

    ReplyDelete
  3. http://www.huntland.co.uk/Downloads/MOM/AdvancedConsolidation.html

    ReplyDelete
  4. Your a legend man.This worked like a charm

    ReplyDelete
  5. Can the same be achieved in OpsManager 2007? I don't see Consolidation Rules in OM2007. Any help is greatly appreciated.

    Thanks!

    Rajesh

    ReplyDelete
  6. Can the same be achieved in OpsManager 2007? I don't see Consolidation Rules in OM2007. Any help is greatly appreciated.

    Thanks!

    Rajesh

    ReplyDelete

Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …