Security event manager

From Wikipedia, the free encyclopedia
Jump to: navigation, search

A security event manager (SEM), and the related SIM and SIEM, are computerized tools used on data networks to centralize the storage and interpretation of logs, or events, generated by other software running on the network.[1][2][3]

The acronyms SEM, SIM and SIEM have sometimes been used interchangeably,[4] but generally refer to the different primary focus of products:

  • Log Management: Focus on simple collection and storage of log messages and audit trails[5]
  • Security information management (SIM): Long-term storage as well as analysis and reporting of log data.[6]
  • Security event manager (SEM): Real-time monitoring, correlation of events, notifications and console views.
  • Security information and event management (SIEM): Combines SIM and SEM and provides real-time analysis of security alerts generated by network hardware and applications.[7][8]

In practice many products in this area will have a mix of these functions, so there will often be some overlap - and many commercial vendors also promote their own terminology.[citation needed]

Event logs[edit]

Many systems and applications which run on a computer network generate events which are kept in event logs. These logs are essentially lists of activities that occurred, with records of new events being appended to the end of the logs as they occur. Protocols, such as syslog and SNMP, can be used to transport these events, as they occur, to logging software that is not on the same host on which the events are generated. The better SEMs provide a flexible array of supported communication protocols to allow for the broadest range of event collection.

It is beneficial to send all events to a centralized SEM system for the following reasons:

  • Access to all logs can be provided through a consistent central interface
  • The SEM can provide secure, forensically sound storage and archival of event logs (this is also a classic log management function)
  • Powerful reporting tools can be run on the SEM to mine the logs for useful information
  • Events can be parsed as they hit the SEM for significance, and alerts and notifications can be immediately sent out to interested parties as warranted
  • Related events which occur on multiple systems can be detected which would be impossible to detect if each system had a separate log
  • Events which are sent from a system to a SEM remain on the SEM even if the sending system fails or the logs on it are accidentally or intentionally erased

Security analysis[edit]

Although centralised logging has existed for long time, SEMs are a relatively new idea, pioneered in 1999 by a small company called E-Security,[9] and are still evolving rapidly. The key feature of a Security Event Management tool is the ability to analyse the collected logs to highlight events or behaviors of interest, for example an Administrator or Super User logon, outside of normal business hours. This may include attaching contextual information, such as host information (value, owner, location, etc.), identity information (user info related to accounts referenced in the event like first/last name, workforce ID, manager's name, etc.), and so forth. This contextual information can be leveraged to provide better correlation and reporting capabilities and is often referred to as Meta-data. Products may also integrate with external remediation, ticketing, and workflow tools to assist with the process of incident resolution. The better SEMs will provide a flexible, extensible set of integration capabilities to ensure that the SEM will work with most customer environments.

Regulatory requirements[edit]

SEMs are often sold to help satisfy U.S. regulatory requirements such as those of Sarbanes-Oxley, PCI-DSS, GLBA.[citation needed]

Standardization[edit]

One of the major problems in the SEM space is the difficulty in consistently analyzing event data. Every vendor, and indeed in many cases different products by one vendor, uses a different proprietary event data format and delivery method. Even in cases where a "standard" is used for some part of the chain, like Syslog, the standards don't typically contain enough guidance to assist developers in how to generate events, administrators in how to gather them correctly and reliably, and consumers to analyze them effectively.

As an attempt to combat this problem, a couple parallel standardization efforts are underway. First, The Open Group is updating their circa 1997 XDAS standard, which never made it past draft status. This new effort, dubbed XDAS v2, will attempt to formalize an event format including which data should be included in events and how it should be expressed. The XDAS v2 standard will not include event delivery standards but other standards in development by DMTF may provide a wrapper.

In addition, MITRE is also in the midst of a standardization effort called CEE that is somewhat broader in scope - it attempts to define an event structure as well as delivery methods.

Vendor products[edit]

See also[edit]

References[edit]

  1. ^ http://www.securityinformationeventmanagement.com/security-event-management.php SIEM
  2. ^ Preparing for Security Event Management
  3. ^ A Practical Application of SIM/SEM/SIEM Automating Threat Identification
  4. ^ Swift, David (26 December 2006). "A Practical Application of SIM/SEM/SIEM, Automating Threat Identification" (PDF). SANS Institute. p. 3. Retrieved 14 May 2014. ...the acronym SIEM will be used generically to refer... 
  5. ^ http://csrc.nist.gov/publications/nistpubs/800-92/SP800-92.pdf
  6. ^ Jamil, Amir (29 July 2009). "The difference between SEM, SIM and SIEM" (Blog). 
  7. ^ "SIEM: A Market Snapshot". Dr.Dobb's Journal. 5 February 2007. 
  8. ^ The Future of SIEM - The market will begin to diverge
  9. ^ "Novell buys e-Security", 2006, ZDNet
  10. ^ "Assuria Log Manager Overview". Assuria Ltd. Retrieved 24 March 2015. 
  11. ^ "CCTM - Awards - Assuria Log Manager Version 4". UK Government (Crown Copyright). 2011. Archived from the original on 4 December 2011. Retrieved 24 March 2015. 

External links[edit]