Analytics
2/10/2012
12:14 PM
Quick Hits
Quick Hits
Quick Hits
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Does SIEM Make Sense For Your Company?

Ten questions to ask before implementing SIEM technology -- and how to choose the right system for your enterprise

[Excerpted from "Does SIEM Make Sense For Your Company," a new report posted this week on Dark Reading's Security Monitoring Tech Center.]

If there’s one thing that sets good incident-response teams apart from not-so-good ones, it’s planning. It may sound like an oversimplification, but ensuring you’ll have what you need before an incident happens makes all the difference. And nowhere is this more critical than when it comes to easy access and availability of log data.

Log information represents the only sensory input we have for past activity on our networks. And no matter how much real-time information any security data management system claims to provide, the bulk of any incident investigation will be spent dealing with events that have already transpired. The ability to store information and to access it in a meaningful way will be what makes or breaks incident response capabilities.

The only way to know what’s normal on a network is to gather as much information as possible on day-to-day activity and then look for anything that demonstrates deviation. This type of data monitoring, sorting, filtering, and correlation requires a highly specialized system known as SIEM, or security information and event management. SIEM is a welcome combination of what used to betwo separate product categories: SEM (security event management), which dealt with security event monitoring, correlation, and notification, and SIM (security information management), which dealt with the long-term storage and analysis of security data.

SIEM products are designed to serve as a warehouse for all the security alerts and logging information from a company’s disparate systems, providing both real-time access to current alert information and the ability to correlate recent incidents with others over time. Companies considering a SIEM product should ask themselves the following questions:

1. What do we expect from a SIEM system?
The worst thing you can do when purchasing any security product is to allow the vendor to define your requirements. Before you let a salesperson through the door, clearly define your expectations for a SIEM system.

Are you planning to use it as the cornerstone of a 24x7 security monitoring system? Will it be used to manage insider threats? Are you aiming to correlate attacks against your borders at multiple facilities? Is it simply a means of checking off some boxes on a compliance audit?

If compliance is a driving force in your search for a SIEM system, you probably have even more homework to do. SIEM systems vary widely here: Some fully embrace compliance with sets of built-in compliance-specific correlation rules, reports, and dashboard-type functionality; others include a few basic reports and claim they’ll support your compliance initiative.

To read the other nine questions -- and to get some advice on how you can store security data without breaking the bank -- download the full report on evaluating and implementing SIEM technology.

Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
JCharles
50%
50%
JCharles,
User Rank: Apprentice
12/3/2012 | 5:13:54 PM
re: Does SIEM Make Sense For Your Company?
True, start with a good SIM as it's 80% of the job. Then use a good SEM that allows you to pay as you go. Now there are tools out there that can do both like Secnology.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web