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.

Vulnerabilities / Threats

4/30/2015
06:25 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Breaking The Security Fail Cycle

How security teams are evolving in the face of today's threats.

INTEROP -- Las Vegas -- Security's heavy reliance and emphasis on technology--due to both its heritage and the reality of a shortage of manpower--is part of the reason attackers are getting the upper hand, experts said here this week.

A lack of security humans to connect the dots from the abundance of security alerts and data generated by various security tools in the enterprise can easily lead to a needle-in-the-haystack "fail." Target's dismissal of real alerts amid the piles of false positives it had to cull through has become a cautionary tale of just how challenging it is to parse security data today.

Meanwhile, security products and startups continue to emerge and in some cases bolt on yet another layer or specific fix, which complicates things further for the security team.

"When you go walk the [show] floor and see all these new capabilities, and tools that solve this and that … the question you should always ask is 'What is this going to help let me stop doing?'" Mike Zachman, deputy CISO of Caterpillar said today. "Every security solution is an addition, but never a subtraction. You have to make that a mental model: when you buy a tool, what [will it allow you to] stop doing? If you can't answer that, you'd better feel good" about what the product will do, he said during a panel discussion here chaired by John Pironti of IP Architects LLC.

Ofer Elzam, director of enterprise product security at Sophos, says top of mind for him lately is how to make security simpler. "A lot of breaches we see: it's not a lack of tools, but security is very complex. [The victims] have limited resources to manage those," Elzam said.

Meanwhile, companies are wrestling with basic security hygiene duties such as the piles of software patches that keep landing on their desks. Eric Hanselman, chief analyst of 451 Research, says the basics are actually not as easy as they would seem. With patching, for instance, it's not just apply every patch you get. "There are going to be systems we can't patch," where a patch could break an application, he said.

It's a matter of being creative with the resources you have and automating some security processes, said Elliott Glazer of Max Security and a former CISO. "It only takes one unpatched system in a poorly segmented network" for an attack, he said. "You've got to think about ways of mitigating that risk, with people, process, and technology."

When it comes to patching, no company will achieve 100% patched, Hanselman said. "You can't get there. Patch as much as you can," he said. Network segmentation of systems where the "patch density isn't so high" helps as well as monitoring systems that you can't segment, he said.

Caterpillar's Zachman says his company assesses patches for criticality and uses a timetable for applying them. "We have a standard timetable we hold ourselves to, based on criticality," he said. The operational teams who "own" the affected systems are responsible for applying those fixes on those deadlines, he said.

451's Hanselman concurred that the "owners" of vulnerable systems should maintain them and patch them. The vulnerability risk analysis from new patches should be shared with these teams and provided to them, along with an understanding of the risks of the flaws to attack, he said.

This is part of the evolution of the security team as more of a provider to the business, the panelists said.

Caterpillar's Zachman said his team has become akin to security consultants. "We consult with them, explain the risk, and help them understand how they can mitigate it if they can't comply … But it's up to them to say yes, I accept that risk. We make sure it's documented and understood," he said.

"Any discussion in security is a risk-based discussion," Eric Green, senior vice president of Mobile Active Defense, said here today in another panel discussion. "You have to decide where you can prioritize based on the business." 

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
aziza bond
50%
50%
aziza bond,
User Rank: Apprentice
5/4/2015 | 1:52:49 PM
Re: Simplify, rethink, simplify, rethink
You are totally true , there is a difference there
macker490
100%
0%
macker490,
User Rank: Ninja
5/3/2015 | 7:25:07 AM
Re: Simplify, rethink, simplify, rethink
there is a fundamental difference between an old "dumb head" terminal like a VT-100 or a 3270 -- and a PC: the PC can have multiple applications open at the same time -- AND -- the PC User's credentials apply to all the open apps.   this is wrong from the get-go and promotes leakage of secure data between apps: while memory may be protected: file systems are not.   this may be rectified by using NAMED SPACES so that application programs do NOT have free run of all the data resources on the user workstation combined with free use of the user's credentials.
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
5/1/2015 | 12:45:02 AM
"Stop Doing"
A kernel of wisdom in this article notes "the question you should always ask is 'What is this going to help let me stop doing?'"  That is because every security solution "is an addition, but never a subtraction."

It is always amazing to me the amount of overhead on man hours applications specially designed to "help" the Enterprise actually ingest.  In particular, security software (of which I've had the pleasure of managing two, so I know from experience) seems to take the cake.  

Being able to assess an application, the time it will require to implement and whether its features once live will save or incur time cost is a great skill and an important part of procurement. 

 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
4/30/2015 | 11:32:29 PM
Simplify, simplify, simplify
Security simplification may indeed be the most important InfoSec step we can take -- across the board.  Most security mishaps, I daresay, happen because of laziness and/or an overpermissiveness so as to not compromise accessibility and functionality (security's mortal foes).  The less conflict security innovations can present between security and accessibility, the more security we can expect to see.
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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-3460
PUBLISHED: 2021-04-13
The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could lead to the communication channel being accessible by an attacker.
CVE-2021-3462
PUBLISHED: 2021-04-13
A privilege escalation vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could allow unauthorized access to the driver's device object.
CVE-2021-3463
PUBLISHED: 2021-04-13
A null pointer dereference vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could cause systems to experience a blue screen error.
CVE-2021-3471
PUBLISHED: 2021-04-13
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.
CVE-2021-3473
PUBLISHED: 2021-04-13
An internal product security audit of Lenovo XClarity Controller (XCC) discovered that the XCC configuration backup/restore password may be written to an internal XCC log buffer if Lenovo XClarity Administrator (LXCA) is used to perform the backup/restore. The backup/restore password typically exist...