Vulnerabilities / Threats

1/2/2018
02:00 PM
Carol Clark
Carol Clark
Commentary
Connect Directly
Facebook
Twitter
RSS
E-Mail vvv
50%
50%

The Cybersecurity 'Upside Down'

There is no stranger thing than being breached. Here are a few ways to avoid the horror.

Like many in cybersecurity, I'm more than a bit of a sci-fi fan and was easily reeled in by Netflix's Stranger Things. Stranger Things' Upside Down is an alternative reality where none of us wants to be. Landing in the Upside Down diverts circumstances in different, unintended directions and, in some cases, permanently changes lives.  

As breach headlines and the resulting fallout of these compromises continue to stream in, it's easy to imagine that the affected companies are now experiencing their own alternative, unintended reality. This wasn't the business plan they started the year with, but it is what will be managed for months, and likely a few years, to come. It's more than a bit… upside down. 

The Cybersecurity Upside Down is the alternate reality organizations enter once they have been materially compromised. It stops business, costs millions, and can have an incalculable impact on current and future customers. It's the inevitable, not-so-alternative reality for organizations if they don't take a strategic approach to security, especially as they transform their businesses. Small changes and more investments in new, disparate tools without a seismic shift in strategy will take you to the Cybersecurity Upside Down. 

What Does the Cybersecurity Upside Down Look Like?
In two words, "reactive chaos." You have no control of your environment and most of your efforts are diverted into understanding what happened, containing the damage, and remediating the issue. New projects, including cloud development and mergers and acquisitions, are significantly stalled. An organization new to the Cybersecurity Upside Down will quickly realize it is blind to what is happening on the network, unaware of where the weaknesses are and without the ability to quickly assess risk.

How Can You Stay Out of the Upside Down?
Do whatever you can to get visibility of your entire security posture and be able to measure it easily and, preferably, continuously so you can take proactive action. Many security organizations have started instrumenting for visibility at endpoints and networks. This is important and useful in monitoring, responding to, and, in some cases, being able to block potential exploits. But this is only a start.

Understanding and establishing true visibility for code and application security is a must for today's enterprises. Most companies are developing technology and using many different infrastructure providers and third-party components, and they're accelerating development practices due to competition and new methodologies such as DevOps. If organizations are not integrating security into the entire development lifecycle, they are exposed. Practices of manual pen testing twice per year, and/or siloed testing within development provide no visibility and painful remediation in an Upside Down event. 

Make sure to ask questions. Knowing how organizations in your supply chain are developing and protecting your products gives you a line of sight into issues and areas of potential risk. How easily can they update you on the security of their solutions? How will they handle remediation for the solutions? Do they continuously test? 

Systemically Avoid the Cybersecurity Upside Down
Weaknesses and vulnerabilities can be insidious. So, how can organizations root out the unintended consequences of how their company is operating?  Automate wherever possible to provide better visibility. Automating code and application security, for example, takes the burden off of siloed teams and developers. More-secure software is delivered faster, and automation enables a continuous view of your security posture.  

Embed the Culture of Security
Just one trip to the Upside Down will highlight quickly how well or how ineffectively DevOps, security, and development teams are working together. Embedding security champions within development teams and automating and orchestrating security are good examples of how to advance the culture of security in an organization. Threat modeling and red teaming are also good exercises to go through, as long as the results are embedded in the security posture going forward and improve overall operations. By integrating security early and often into the application development process, you can have the visibility and assurance that you need for the best defense against the Cybersecurity Upside Down. 

Related Content:

Carol Clark has over 17 years of experience in the software security industry. She is currently Vice President of Marketing at CYBRIC, where she is responsible for customer success programs. She has also held numerous leadership roles at RSA Security, including vice president ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Data Privacy Careers Are Helping to Close the IT Gender Gap
Dana Simberkoff, Chief Compliance and Risk Management Officer, AvePoint, Inc,  8/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10006
PUBLISHED: 2018-08-20
Jsish version 2.4.65 contains a CWE-476: NULL Pointer Dereference vulnerability in Function jsi_ValueCopyMove from jsiValue.c:240 that can result in Crash due to segmentation fault. This attack appear to be exploitable via a crafted javascript code. This vulnerability appears to have been fixed in 2...
CVE-2018-10006
PUBLISHED: 2018-08-20
The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This ...
CVE-2018-10006
PUBLISHED: 2018-08-20
Rust Programming Language Rust standard library version Commit bfa0e1f58acf1c28d500c34ed258f09ae021893e and later; stable release 1.3.0 and later contains a Buffer Overflow vulnerability in std::collections::vec_deque::VecDeque::reserve() function that can result in Arbitrary code execution, but no ...
CVE-2018-10006
PUBLISHED: 2018-08-20
JabRef version <=4.3.1 contains a XML External Entity (XXE) vulnerability in MsBibImporter XML Parser that can result in disclosure of confidential data, denial of service, server side request forgery, port scanning. This attack appear to be exploitable via Specially crafted MsBib file. This vuln...
CVE-2018-10006
PUBLISHED: 2018-08-20
zzcms version 8.3 and earlier contains a SQL Injection vulnerability in zt/top.php line 5 that can result in could be attacked by sql injection in zzcms in nginx. This attack appear to be exploitable via running zzcms in nginx.