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

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
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.
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.
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27581
PUBLISHED: 2021-03-05
The Blog module in Kentico CMS 5.5 R2 build 5.5.3996 allows SQL injection via the tagname parameter.
CVE-2021-28042
PUBLISHED: 2021-03-05
Deutsche Post Mailoptimizer 4.3 before 2020-11-09 allows Directory Traversal via a crafted ZIP archive to the Upload feature or the MO Connect component. This can lead to remote code execution.
CVE-2021-28041
PUBLISHED: 2021-03-05
ssh-agent in OpenSSH before 8.5 has a double free that may be relevant in a few less-common scenarios, such as unconstrained agent-socket access on a legacy operating system, or the forwarding of an agent to an attacker-controlled host.
CVE-2021-3377
PUBLISHED: 2021-03-05
The npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.
CVE-2021-3420
PUBLISHED: 2021-03-05
A flaw was found in newlib in versions prior to 4.0.0. Improper overflow validation in the memory allocation functions mEMALIGn, pvALLOc, nano_memalign, nano_valloc, nano_pvalloc could case an integer overflow, leading to an allocation of a small buffer and then to a heap-based buffer overflow.