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.

Operations

4/12/2017
02:00 PM
Mike D. Kail
Mike D. Kail
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Cybersecurity & Fitness: Weekend Warriors Need Not Apply

It takes consistency and a repeatable but flexible approach to achieve sustainable, measurable gains in both disciplines.

There are several corollaries between the health and fitness industry and the cybersecurity industry. In both cases, people are looking for a "quick fix" such as a simple pill that bypasses the need for self-control, dedication, and rigor. The "weekend warrior" approach doesn’t work, and often simply results in frustration and little to no improvement.

There is also, in both cases, a steady stream of products or features flooding the market on a continuous basis, each with a slightly nuanced set of promises, gimmicks, and buzzwords. Consequently, despite all of these promises and good intentions, our overall levels of physical fitness and cybersecurity resilience are on the rapid decline. 

A Tactical Approach
Many of us grew up with our parents asking us the question, “Did you take your vitamins?” It’s an approach to health, which, while there is nothing wrong with taking vitamins, is simply a tactical part of an overall health and wellness program. This mindset is unfortunately too often the approach of a cybersecurity program. Disparate tools ("vitamins") are purchased and deployed to address a specific vertical portion of the application development and delivery life cycle. Meanwhile, the number of breaches continues to increase at an alarming rate. In both fitness and cybersecurity, there are no shortcuts. One has to put together a comprehensive strategy and be diligent about deploying and adhering to it. Consistency and a repeatable, but flexible, approach is what will result in sustainable, measurable gains.

A Strategic Plan 
Let’s say you decide that you want to run a marathon. You don’t start by going out and running 26.2 miles, but instead work on an overall plan that builds up your strength and resiliency over time. The same approach is needed for cybersecurity. First, you should assess the overall current state of your security posture. Second, collaborate with the various stakeholders and partners on the strategic plan to start embedding security best practices into all areas of the business, including the software development life cycle. Finally, make sure that you continue to communicate any updates to the plan, and more importantly, the ongoing results and subsequent improvements in security posture.

Sticking with It
The key to any long-term fitness program is sticking with it and being consistent. One simply doesn’t run a marathon and then stop working out in the hopes that the benefits stay with you indefinitely. The same applies to cybersecurity, and unfortunately the current compliance and regulations aren’t helpful with consistent rigor. For example, PCI Compliance only requires pen-testing/AppSec testing two times per year. Meanwhile hackers are continuously scanning your application infrastructure for vulnerabilities. The status quo simply won’t help, and new, disruptive approaches need to be adopted.

As with fitness, gains are made by periodic, disruptive changes, and security professionals need to start thinking in those terms in hopes of actually driving significant change. The base portion of your cybersecurity program should start with code security and static code analysis, and be a seamless step in the early part of the software development life cycle.

The next phase is at the continuous integration build step. This is where the automated scanning of third-party and open-source components and libraries should occur, as well as any additional static code analysis.

Finally, application security scanning and penetration testing should be performed before updates are delivered to production to discover any vulnerabilities and immediately remediate them. Visibility and assurance are now provided across all of your code repositories and application environments.

Continuous Improvement
Now that you’ve established a strong level of baseline resiliency, it’s time to think about different ways to continually improve your cyber fitness and not become lazy or complacent. It’s highly unlikely that your enterprise environment is remaining static, and, in fact, with today’s high-velocity approach to business outcomes, you need to remain agile and adaptive in your approaches to ensure that cybersecurity keeps pace. Collaboration and holding each other accountable works very well in sticking with a fitness program, and the same approach will make sure your cybersecurity posture stays in shape too.

[Check out the two-day Dark Reading Cybersecurity Crash Course at Interop ITX, May 15 & 16, where Dark Reading editors and some of the industry's top cybersecurity experts will share the latest data security trends and best practices.]

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 10/30/2020
'Act of War' Clause Could Nix Cyber Insurance Payouts
Robert Lemos, Contributing Writer,  10/29/2020
6 Ways Passwords Fail Basic Security Tests
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How to Measure and Reduce Cybersecurity Risk in Your Organization
In this Tech Digest, we examine the difficult practice of measuring cyber-risk that has long been an elusive target for enterprises. Download it today!
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-5991
PUBLISHED: 2020-10-30
NVIDIA CUDA Toolkit, all versions prior to 11.1.1, contains a vulnerability in the NVJPEG library in which an out-of-bounds read or write operation may lead to code execution, denial of service, or information disclosure.
CVE-2020-15273
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can ac...
CVE-2020-15276
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. Arbitrary JavaScript may be executed by entering a crafted nickname in blog comments. The issue affects the blog comment component. It is fixed in version 4.4.1.
CVE-2020-15277
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is affected by Remote Code Execution (RCE). Code may be executed by logging in as a system administrator and uploading an executable script file such as a PHP file. The Edit template component is vulnerable. The issue is fixed in version 4.4.1.
CVE-2020-7373
PUBLISHED: 2020-10-30
vBulletin 5.5.4 through 5.6.2 allows remote command execution via crafted subWidgets data in an ajax/render/widget_tabbedcontainer_tab_panel request. NOTE: this issue exists because of an incomplete fix for CVE-2019-16759. ALSO NOTE: CVE-2020-7373 is a duplicate of CVE-2020-17496. CVE-2020-17496 is ...