Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Analytics

4/26/2012
04:47 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Logs Still Tough To Decipher, SANS Survey Says

More organizations employ log management and SIEM tools, but are still struggling to sort the bad traffic from the good

More organizations are using log event management and Security Information and Event Management (SIEM) products, but they are struggling to distinguish between suspicious and normal traffic, according to the SANS 8th Annual Log Management Survey.

Some 58 percent of organizations surveyed by SANS employ a log management tool for gathering and analyzing logs, and 37 percent are running a SIEM. Around 22 percent say they collect logs and then process them with a SIEM, according to the survey of 600 IT professionals, which was sponsored by HP Enterprise Security, LogLogic, LogRhythm, Sensage, Splunk, Tripwire, and Trustwave.

"The data suggest that respondents are having difficulty separating normal traffic from suspicious traffic," said Jerry Shenk, author of the SANS report. "They need advanced correlation and analysis capabilities to shut out the noise and get the actionable information they need. But first they need to get more familiar with their logs and baseline what is normal."

Interestingly, some 22 percent of the respondents say they have "little or no" automation for their logging and analysis, with no plans to remedy that. "The most common reasons given for not automating include lack of time and money ... resources that are closely intertwined. Respondents cited two additional reasons: the lack of management buy-in and insufficient time to evaluate the options available in different SIEM and log management products," according to the SANS report.

More than 80 percent say they collect logs mainly to look out for attacks, while 65 percent say they do so for forensic analysis and correlation, and 58 percent for preventing security incidents. Also important for logging is to help detect advanced threats, according to 54 percent of the respondents, and for meeting compliance (55 percent).

They are gathering logs mainly from Windows servers, which account for about 85 percent of the respondents, followed by security devices (more than 80 percent), networking devices (nearly 80 percent), and networking and security systems (around 70 percent). There were some other less-obvious devices being logged as well: "Some of the new items included 'Control systems for physical plant/operations' with eight percent, 'Access controls for physical plant' with 17 percent, and 'Cloud-based or outsourced services/applications' with eight percent," according to the report.

How much time do organizations spend analyzing logs? Some 35 percent spend "none to a few hours a week," the survey found.

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

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
NXLog
50%
50%
NXLog,
User Rank: Apprentice
10/30/2017 | 11:06:41 AM
Pending Review
This comment is waiting for review by our moderators.
JCharles
50%
50%
JCharles,
User Rank: Apprentice
1/9/2013 | 4:28:10 PM
re: Logs Still Tough To Decipher, SANS Survey Says
So most organizations either don't own a Log Manager / SIEM or for those that do, they can't run it to it's full potential. Why ? because they're too complicated, time consuming & expensive. But thankfully there are solutions out there that aren't like Secnology.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/4/2020
Abandoned Apps May Pose Security Risk to Mobile Devices
Robert Lemos, Contributing Writer,  5/29/2020
Cybersecurity Spending Hits 'Temporary Pause' Amid Pandemic
Kelly Jackson Higgins, Executive Editor at Dark Reading,  6/2/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13817
PUBLISHED: 2020-06-04
ntpd in ntp before 4.2.8p14 and 4.3.x before 4.3.100 allows remote attackers to cause a denial of service (daemon exit or system time change) by predicting transmit timestamps for use in spoofed packets. The victim must be relying on unauthenticated IPv4 time sources. There must be an off-path attac...
CVE-2020-13818
PUBLISHED: 2020-06-04
In Zoho ManageEngine OpManager before 125144, when <cachestart> is used, directory traversal validation can be bypassed.
CVE-2020-6640
PUBLISHED: 2020-06-04
An improper neutralization of input vulnerability in the Admin Profile of FortiAnalyzer may allow a remote authenticated attacker to perform a stored cross site scripting attack (XSS) via the Description Area.
CVE-2020-9292
PUBLISHED: 2020-06-04
An unquoted service path vulnerability in the FortiSIEM Windows Agent component may allow an attacker to gain elevated privileges via the AoWinAgt executable service path.
CVE-2019-16150
PUBLISHED: 2020-06-04
Use of a hard-coded cryptographic key to encrypt security sensitive data in local storage and configuration in FortiClient for Windows prior to 6.4.0 may allow an attacker with access to the local storage or the configuration backup file to decrypt the sensitive data via knowledge of the hard-coded ...