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.

Endpoint

5/21/2013
01:56 AM
50%
50%

Even SMBs Should Look To Log Management For Security

A firewall, patch procedure, anti-malware and, possibly, an IDS are a good start. But to detect breaches, small and medium businesses should focus on logging activity and looking out for suspicious behavior

For small and midsize businesses, having the basics of security in place is important: Every business, no matter what size, should have a firewall, a patch- or vulnerability-management process, anti-malware software, and possibly an intrusion detection -- or prevention -- system.

Yet those technologies aim to make the company's network more difficult to compromise. To detect actual breaches, companies need to turn to the logs. While log management has not historically been a major focus for SMBs, analyzing log data can help companies detect and investigate breaches, and are mandated by many compliance requirements.

Retaining and analyzing logs is about knowing what transpires inside the business' network, and companies of any size should look for ways to use that information, says Tim Mather, CISO for Splunk, the maker of the eponymous data-analysis tool.

"You have to have good log management because that is the definitive record of all the interactions between machines and humans," he says.

Companies need to make the most out of the security data they produce or else find themselves oblivious of any breach of their network. Yet most are. While more than two-thirds of attackers exfiltrate business data within hours, it take nearly two-thirds of companies months to detect the breach, according to the 2013 Verizon Data Breach Investigations Report. And in seven out of 10 cases, the company is not the one to detect the breach -- an outsider does.

The problem for most companies is the time required to set up a reliable logging system and the knowledge needed to cull information from the log files, says Barry Kouns, president of Risk Based Security, a security consultancy and service provider.

"The systems can collect data really nicely, but the problem is how to interpret that information," he says.

While the largest companies have the security expertise to tailor their systems to their security needs, smaller firms generally do not. More often then not, compliance mandates -- especially the Payment Card Industry Data Security Standard (PCI-DSS) -- require that a company implement log retention and review them daily.

"These firms have to meet a requirement to capture their logs, yet a lot of these customers do not have a dedicated security team," says Andy Leach, product manager at AlertLogic, a maker of log-management products and services.

Small and midsize businesses should start by determining what systems need to be protected and what their log management policy will be, says Mark Seward, senior director of security and compliance marketing for Splunk. Most often, companies will be driven by compliance requirements, but they should not limit themselves, he says. While compliance requirements are a good way to spur the adoption of log management technologies, companies should focus on gaining awareness of the security events happening on their network.

[Straight-shooting advice -- and some out-of-the-box thinking -- on how smaller companies can save money on security while doing it better. See 5 Ways For SMBs To Boost Security But Not Costs.]

"Good security breeds good compliance and not the other way around -- compliance is the low bar," he says.

Next, business managers should determine whether they have the in-house expertise to run their own log management process. Playing around with Splunk, which is free for limited use, can be a good way to determine whether the collection and analysis of logs can be done with company staff, says Michael Gough, a senior security specialist at a 500-employee gaming company, which he asked not to be named. Gough uses the software to analyze the company's security data for signs of problems.

"Logging is an art and needs to be set up by someone who understands what to look for -- a security consultant -- so outsource this if you don't have in-house staff," he says.

Security information and event management (SIEM) products -- such as those from AlienVault and SolarWinds -- can help companies track information from logs, highlight security issues, and prioritize necessary fixes.

Finally, for the large number of SMBs whose information technology group does not have the time or in-house expertise, a cloud or managed service can help them develop a log-management strategy and then maintain the logs and report on security incidents.

"The critical part is that these systems don't run themselves, and there needs to be a level of care and maintenance to get information out of the service," says Risk Based Security's Kouns.

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. Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
CVE-2020-5990
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
CVE-2020-25483
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
CVE-2020-5977
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.