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.

Application Security

1/5/2018
03:23 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

A Necessary Security Slowdown

The key to being more secure might well lie in the ability to slow down just a bit.

So here we are in the first week of a new year and we're already talking about a massive security vulnerability. It doesn't give one a warm and fuzzy feeling about what's to come.

There have been plenty of articles predicting the year that's ahead and this won't be another. Instead, let's look at what is certain -- and what can be done about it.

Here's the certainty: The systems we build, and the components on which they're built, are now so complex as to make it almost impossible to guarantee the stability and security of the whole, or even of any part of the whole. Put another way, we have to assume that pretty much everything is broken -- and broken in some catastrophic way -- the day that it's deployed. So what do we do about it?

First of all, if we can't protect the system we have to protect the critical data held within the system. That makes encryption more important than ever before. Data must be encrypted in transit and at rest. It must be encrypted every time, all the time. And that means that we have to make the process of encryption and decryption as secure, as automatic and as friction-free as possible. In other words, we have to lower the total cost of encryption to the point that there's not really a decision to be made around encryption -- it's just assumed at every step of the process.

And speaking of those steps, we have to assume that each step is broken and each transition between steps is compromised. This marks the end of the "encrypt once and forget it" method. Each app or service must be separately encrypted and each API must carry encryption for data passing through the process. That's a lot of extra encryption baggage but it's the cost we pay for building such wonderful, and wonderfully complex, systems.

Finally, we might just need to slow things down ever so slightly. Not the individual applications -- they should run as fast as hardware and security will allow. But companies are now taking pride in the scores of releases pushed each day as though speed was the only virtue worth pursuing in the modern enterprise. There's no denying that speed is important, but as any race-car driver will tell you, control is important too.

Agile is a very useful discipline and devops and very useful framework in which to implement agile. But in some organizations agile has become an excuse for sloppy and we're now seeing that there is a huge price to be paid for sloppy design and engineering.The new year has started on a note of danger, but let's all take a breath: There's much to be learned here and much to be done to make the rest of the year less dangerous. It's time to get to work.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15505
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1, and Sentry before 9.7.3 and 9.8.x before 9.8.1, allow remote attackers to execute arbitrary code via unspecified vectors.
CVE-2020-15506
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
CVE-2020-15507
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to read files on the system via unspecified vectors.
CVE-2020-15096
PUBLISHED: 2020-07-07
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using "contextIsolation" are affecte...
CVE-2020-4075
PUBLISHED: 2020-07-07
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not ...