Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.ai.fuzzy    |    Fuzzy logic... all warm and fuzzy-like    |    1,275 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 522 of 1,275    |
|    Kirt Undercoffer to CMOS    |
|    Re: Detecting Anomalies of events    |
|    18 Oct 05 03:14:41    |
      XPost: comp.ai, comp.ai.neural-nets, comp.databases       XPost: sci.math       From: kirtu@earthlink.net              CMOS wrote:       > hi all,       > i need to build a system which will find any anomalies of a particular       > activity. The system will be feeded with events that are happening and       > it should be able to find any significant deviation from the normal       > operation. ...       > 1 ) webserver access       ...       > 5 ) access ( login ) patterns, frequency to a particular system       > ...       >       > basically i need to be alerted on       >       > deviation of events's frequency from normal       > deviation in pattern of events that are happening, etc       >       > i wonder whether there is any area in mathematics / computer science       > which deal with that kind of problems. So i really appreciate if some       > one can suggest me a good path for the project.              You have made a mistake common to this kind of problem.              Namely you are assuming that derivations from an observed norm is an       error.              With the domains listed you can get away with this. But there are       domains where this assumption will be false. Specifically this       assumption does not necessarily hold for computer log file analysis or       in fact in any domain in which misconfiguration and/or malfunctions       (i.e. bugs requiring patches or hotfixes applied to a large number of       systems [like the endless stream of hotfixes that Microsoft was putting       out before they started staging their hotfixes as upgrades]) are very       common and can be seen as normal. In fact with such systems outliers       can actually be correctly configured systems! With these sorts of       domains the problem is compounded because there isn't generally a       universal baseline that can be established because different systems       have differing configurations because of different needs in different       environments.              Regarding even the domains listed, access is handled best by policy and       policy isn't always reflected in actually access patterns. If you have       a large number of users and there have been long-term undetected       intrusion, then simply looking for outliers alone will not detect the       intrusion because the currently undetected intrusion is already       established as the norm (an extreme but possible condition). Outlier       analysis like this can only detect new intrusion. So consider adding       policy checking.              BTW - these issues came up in a real life system I was working on where       people from a major defense contractor made the same naive assumption.              Kirt Undercoffer              [ comp.ai is moderated. To submit, just post and be patient, or if ]       [ that fails mail your article to |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca