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
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.