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.

Careers & People

2/8/2017
10:30 AM
Mike D. Kail
Mike D. Kail
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

What to Watch (& Avoid) At RSAC

A renowned security veteran shares his RSA dance card, offering views on technologies destined for the dustbin of history and those that will move the industry forward.

As tens of thousands of IT executives, security leaders, and cyber engineers prepare to attend the 2017 RSA Security Conference in San Francisco next week, I put together a list of what I feel are the top technologies and areas to look at, both at the conference, and in the coming year.

First, a quick overview of the dinosaurs - technologies I am not interested in seeing, mainly because I don’t believe that these incremental approaches have  made significant progress against hackers.  

  • Endpoint Protection, including, for example, “next-gen,” money-backed guarantees, and other “gimmicks.” It seems to me that these technologies are always trying to keep up versus actually being proactive by constantly learning and adapting to new threats and attacks. 
  • SIEM. This is perhaps one of the least sexy sectors in the vast cybersecurity landscape. As more and more devices become part of the overall elastic network perimeter, the rate of data being produced is explosive. Once again, this is a technology that is always trying to catch up even though the operational costs of running and maintaining it are not trivial.
  • Incident Response Automation. (Otherwise known as, “How can we get the post-mortem completed as quickly as possible?”) Instead of trying to solve for something that’s already occurred, how about we start focusing on actually preventing the majority of incidents from happening in the first place? Advancing automation for more secure products and processes is good but right now the emphasis is in the wrong place.  

These are the areas that I believe are extremely compelling, and if developed and implemented correctly, can help security teams move in a positive direction towards improving their overall resiliency.

  • IoT Security. Internet-enabled now seems to be table stakes for any new device being released to the market. Given the recent large scale attacks caused by IoT devices, there needs to be an overall standard, and I really hope that UL starts being more transparent. Its Cybersecurity Assurance Program is a good start, but there needs to be far greater diligence applied to it.
  • Identity Management. Infrastructure has transformed into software-defined and elastic, yet most identity provider solutions still remain quite rigid. Many also only focus on the AuthN (authentication) part of identity versus AuthZ (Authorization),  where innovation should occur, combined with simple best practices such as “least privileges.’’ In the age where everything has an identity, there should be a platform that is adaptive enough to support this. 
  • Artificial Intelligence + Machine Learning. Skills shortage or not, scaling out human capital to attempt to keep pace with "The Singularity" is not an option. Continuous analysis and learning using a variety of techniques, including Behavioral Analysis and Game Theory, is what is required to truly move the needle in cybersecurity. This area also overlaps with my next area - DevOps - and the goal of creating a true culture of DevSecOps. In other words, an AI/ML solution has to be an API-driven platform solution, not another point-solution tool. (Note: If you are learning or hyperfocused on AI in general, you may want to check out Gigaom AI, also taking place in SF during RSAC).
  • DevSecOps. One of my core assertions is that security engineers need to adopt a software engineering mindset and approach to solutions. This is not dissimilar to what happened to “classic” system administrators during the shift to DevOps. Security needs to be seamlessly integrated into the entire software development lifecycle, instead of being a barrier to deploy and the “Department of No.”

Whether you agree with my choices or not, I hope that I have given you a different perspective into a variety of cybersecurity technologies. Controversial and innovative thinking is what drives progress! Share your thoughts in the comments.

Related Content:

 

Mike D. Kail is Chief Innovation Officer at Cybric. Prior to Cybric, Mike was Yahoo's chief information officer and senior vice president of infrastructure, where he led the IT and global data center functions for the company. Prior to joining Yahoo, Mike served as vice ... 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 9/25/2020
Google Cloud Debuts Threat-Detection Service
Robert Lemos, Contributing Writer,  9/23/2020
Shopify's Employee Data Theft Underscores Risk of Rogue Insiders
Kelly Sheridan, Staff Editor, Dark Reading,  9/23/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> ...