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

6/23/2013
12:27 PM
Mike Rothman
Mike Rothman
Commentary
50%
50%

The Slippery Slope Of Security Invisibility

Everyone seems to want security to just be there, invisible to end users. Everyone except the security industry, that is, if it wants to survive

I really liked my partner Rich Mogull's recent Dark Reading blog on "Security Needs More Designers, Not Architects." He makes the point that user experience is key to the success of security controls, and that companies like Apple and others have been working hard to design security under the hood of their general consumer offerings to make security invisible.

I believe that in the long run, security isn't a standalone offering. It must be included in the fabric of the technological ecosystem and that no one should really have to think about how to secure something -- that whatever it is it would be built with security in mind. Of course, in the long run I'll be dead, and so will you. To be clear, I'm not sure we'll ever see this kind of security invisibility in my lifetime. Or my kids', for that matter. But I am a professional cynic, so take that skepticism for what it is.

Yet one of the things that will inevitably get in the way of building security into everything is how it impacts the existing multibillion-dollar security industry. The short answer is dramatically. The jobs that you and I do daily will probably go away if security is just there. There will be a need for security knowledge, but not necessarily security specialization. You can bet that multibillion-dollar industries do not go quietly into the night. And there is a definite disincentive for these incumbent security vendors to fade into the background.

Let me give you a little example of what I'm talking about. I worked a few lifetimes ago with a fellow who spent time as a product manager for a major antivirus company. Yes, when antivirus kind of worked. He told me the story about how the company decided to silence the notifications of signature updates since it was kind of annoying to the customers. The product updated silently when necessary and the user would be none the wiser. Win-win, right?

Actually, it was a big loss for the vendor. The customers loved it. They were no longer pestered by useless notifications. But the vendor saw a measurable negative impact in its product renewals. Since users no longer saw the updates happening, they thought the product wasn't doing anything. So they didn't renew. Makes perfect sense in hindsight. The AV vendor turned notifications back on, and renewal rates went back to historical levels. Amazing how that worked.

It's unfortunate, but if no one thinks security is there, they'll forget to continue paying for it. And getting funding for those key projects will get harder and harder. In fact, most security practitioners feel this pain every day. In the aftermath of a breach, they get whatever they want. No matter the cost. They need to fix the problem, and senior management certainly won't let money get in the way. Not when there is a perp walk hanging in the balance.

Of course, if you're that strange combination of good at security and lucky as hell, you may not have had a breach in a while. Your reward? Groveling to the CFO to explain (again) why security is still important.

Operating system vendors and others that provide infrastructure products and services can get away with making security invisible. In fact, they want to do so, as evidenced by the work of Microsoft and Apple over the past few years. But security vendors and internal security groups need to figure out a way to not antagonize users and force them around your controls, while being just visible enough to ensure the organization knows security is important and warrants increasing investment. Good luck with that.

Rich's future vision of elegantly designed security that just works is truly a compelling vision. The problem is getting there. I think in comparison you'll say Frodo's journey to destroy the One Ring in Mount Doom was a stroll in the park.

Mike's bold perspectives and irreverent style are invaluable as companies determine effective strategies to grapple with the dynamic security threatscape. Mike specializes in the sexy aspects of security, like protecting networks and endpoints, security management, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20477
PUBLISHED: 2020-02-19
PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342.
CVE-2019-20478
PUBLISHED: 2020-02-19
In ruamel.yaml through 0.16.7, the load method allows remote code execution if the application calls this method with an untrusted argument. In other words, this issue affects developers who are unaware of the need to use methods such as safe_load in these use cases.
CVE-2011-2054
PUBLISHED: 2020-02-19
A vulnerability in the Cisco ASA that could allow a remote attacker to successfully authenticate using the Cisco AnyConnect VPN client if the Secondary Authentication type is LDAP and the password is left blank, providing the primary credentials are correct. The vulnerabilities is due to improper in...
CVE-2015-0749
PUBLISHED: 2020-02-19
A vulnerability in Cisco Unified Communications Manager could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack on the affected software. The vulnerabilities is due to improper input validation of certain parameters passed to the affected software. An attacker ...
CVE-2015-9543
PUBLISHED: 2020-02-19
An issue was discovered in OpenStack Nova before 18.2.4, 19.x before 19.1.0, and 20.x before 20.1.0. It can leak consoleauth tokens into log files. An attacker with read access to the service's logs may obtain tokens used for console access. All Nova setups using novncproxy are affected. This is rel...