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

9/26/2013
06:25 PM
Mike Rothman
Mike Rothman
Commentary
50%
50%

Fixating On The Edges

Security folks tend to concentrate on their inability to block improbable attacks, while forgetting to focus on the attacks they're most likely to see

As security folks, we're trained to look for holes. To identify threat vectors that could result in successful attacks and/or data loss. We need to go through the mental exercises (and sometimes real-life pen tests) to feel good that we're doing our best to meet our charter and protect our information. But at times this mind set can lead even experienced folks down dark alleys and result in getting wrapped up in what I'll call "edge cases." You know, fixating on our inability to stop 5 percent of the attacks, while losing sight of the 95 percent of attacks we are far more likely to see.

I wish this epiphany were my idea, but per usual it's because I spend a bunch of time talking to really smart folks kind enough to share their wisdom and perspectives to benefit the rest of us. As I was facilitating a meeting of 20-plus CISOs earlier this week, one of the attendees made the point that we (as a business) get so wrapped up on blocking "all" of the attacks that we lose sight that it's not possible to do so. We want to give a thumbs-down to something because there are very random and difficult ways to exploit it.

We've seen this over and over again -- a point I made in my previous column that some folks have a vested interest in dousing the flames of a new and hot innovative technology. Security research correctly focuses on whether something can be broken and how, not necessarily how scalable or practical an attack.

To illustrate my point, let's revisit the attack published by the CCC, which showed how to beat TouchID with a 3D mold of a fingerprint captured from the device. From the article: "Essentially, CCC researchers demonstrated that an attacker with physical access to the phone could take a picture or scan the fingerprints of the device's owner and use that to create a mold of the fingerprint to launch an attack."

Good thing you got that MakerBot and have a stack of photo-sensitive PCB information lying around, right? Let's be realistic about the value of that device. Are its launch codes on it? Does it posses the combination to the 10-ton lock guarding Fort Knox? The map to the Holy Grail? There would have to be something similarly valuable to warrant producing a 3D mold to gain access to a phone.

It's like I tell my kids after they get a bunch of money for their birthdays: "Just because you have the money doesn't mean you should to spend all of the money." Same goes for security. Just because an attack is possible doesn't mean it's probable. And we, as an industry, get wrapped up in newfangled ways to defend against the improbable.

Ultimately security, like everything else, involves making a bet. You are betting your job that you have got the right people, processes, and technologies in place to protect your critical devices and information. To be clear, that's a bad bet -- but it's the only bet you have. To maximize your likelihood of success and minimize the need to start a job search, you need to play the odds. That means you may have to consciously decide to leave the edge cases unprotected, while making sure you can stop the most probable attacks.

Of course, it's more art than science to figure out which of those attacks are most probable. But that's another story for another day. Just keep in mind if the attack you read about in this here fine publication requires a MakerBot, or a can of dry ice, or an oscilloscope, or a soldering iron, and physical access to the device, then you can address that risk when you get all of the likely attacks you'll face mitigated. Which is basically the day before never.

Mike Rothman is President of Securosis and author of The Pragmatic CSO 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
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Navigating the Asia-Pacific Threat Landscape: Experts Dive In
Kelly Sheridan, Staff Editor, Dark Reading,  9/25/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/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-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...