Risk
1/29/2014
11:47 AM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

4 Hurdles That Trip Security Analytics Efforts

Don't let these people and process problems get in the way of security analytics effectiveness.

While much of the focus on emerging security analytics programs tends to fixate on the data science, algorithms, and technology that makes it all possible, people and process plays as much of a role in analytics as it does in any other facet of security. Many organizations today are learning that lesson the hard way as they find process-oriented impediments standing in the way of security analytics success.

Following are some of the common organizational mistakes that trip up enterprises.


Organizational silos block data flows

To get the full benefit out of a mature security analytics program, data scientists need to get their hands on a lot of contextual business data and IT operational data that doesn't come from security devices.

"Don't underestimate the importance of functional collaboration," says Jessica Gulick, chief strategist for Global Cyber solutions at CSG International. "Accurately correlating security data with business and IT analytics will promote a well-rounded approach."

Unfortunately, organizational structure can greatly impede the free flow of data.

"There [are] often these silos in larger organizations where the people who run the firewall or run the vulnerability scan might not even be in the security group; they're operations," says John Pescatore, director of emerging trends at SANS Institute. "Then the threat analytics guys are in the security group and they're using totally different tools, and the data found in the other silos never get banged into each other."

Read the rest of this article on Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Cruzward
50%
50%
Cruzward,
User Rank: Apprentice
2/18/2014 | 6:09:18 AM
Security
There are many techniques with which the security analysis can be done. But still before posting anything on the web a high level security is must because risk is involved with it.

squarespace review
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.