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

6/7/2013
01:15 PM
Mike Rothman
Mike Rothman
Commentary
50%
50%

Putting Vulnerabilities And Threats Into Context

Advanced security research should play a role in your security program and be ready when science projects become weaponized attacks

Since I'm the new blogger in Dark Reading's Vulnerabilities & Threats Tech Center, it probably makes sense to explain a bit about my views on the role of advanced security research in your general security program. Security research is a critical aspect of your ability to defend yourself. To get a feel for why, go no further than the Great One's quote on a great hockey player:

"A good hockey player plays where the puck is. A great hockey player plays where the puck is going to be." -- Wayne Gretzky

Research and understanding emerging attack vectors help you understand where attackers are going to be. Breach reports and quarterly threat summaries only tell you where attackers have been. If you are trying to stay ahead of the game, then you should not be focusing the short amount of time during the day fighting fires, waging political battles, beating back auditors, and hanging up on vendor sales droids. That's right: Think about where things are going, not where they've been.

To be clear, my perspectives only apply if you do a decent job on blocking and tackling. The fact that a smart researcher will show how you can own an iPhone via the charger matters only if your security program and control set is sufficiently mature. If not, you've got some work to do. But since this is a forward-looking column in a forward-looking Tech Center, I'm not going to tell you what that work is. You can mine the rest of Dark Reading or the Securosis research library for lots of good guidance on security fundamentals.

But if you are ready to systematically factor advanced security research into your program, then I suggest you set up a firm monthly lunch meeting with the security team, ensuring you have something scheduled. You know how it goes with ad hoc meetings, which are always canceled in the wake of some emergency.

In the time between the meetings, use a collaboration tool like Instapaper, Evernote, or (shudder) SharePoint to aggregate interesting links and news items discussing cool, new exploits and/or research findings. It's easy to stay on top of this information because the media loves new attacks; there will be plenty of coverage for anything that's interesting -- and plenty for the stuff that's not.

Once you have your list of things to discuss, ask the team two questions: The first is whether you are exposed to this new attack? Do you have the devices shown to be exploitable by the research? Do you use the applications or technologies in question? If the answer to that question is yes, then ask yourself, what would we do differently to close this exploit? Pretty simple, eh?

You may need to do more research into the attack to understand what's really involved in stopping it. Once you know what's required to address the issue, you can put it on your list of things to address. Understand there may not be a great urgency to fix the issue immediately since a lot of advanced security research is not weaponized yet. But you know what you need to do when the time comes.

And amazingly enough, you'll be where the puck is, and the rest of the industry will be cleaning up the mess. The Great One will be proud.

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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.