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.

Operational Security

12/18/2017
11:20 AM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

Security for the Broken Business

What is the IT security's responsibility when the business itself is intrinsically secure? The first step may be to point out the obvious.

IT security professionals have recently been talking about the importance of having "a seat at the table," that is, a voice in the corporate decision-making process. I've begun to doubt whether those professionals, or any other members of corporate management, fully appreciate what that seat could mean.

As a discipline, security is about protecting assets of every sort from dangers of every type. But what if... what if a portion of the organization -- or the organization itself, cannot be protected? What is security's responsibility then?

I was thinking about this recently as I listened to men, even older than myself, talking about the memories of a war long ended. As they discussed battles and action I was reminded of what little military strategy I've been taught. In strategy, positions and how to defend them are often discussed. In those discussions the hard truth is laid out: Some positions can't be defended.

Through geography or materiel, human resources or munitions, circumstances conspire to make certain positions so vulnerable to attack that there is no workable defense. And in those circumstances there's really only one option. Do not, under any circumstances, allow yourself to be caught in that position.

In business we like to believe that we're smart enough and the tools we wield so powerful that any position -- and circumstance -- can be successfully defended. It can be defended if only we apply enough discipline, intelligence, knowledge and technology. But it's possible that we're wrong.

Let's take a famous example, that of Equifax. Tens of thousands of words have been written looking for "what went wrong" at Equifax. Certainly there were mistakes and errors of process, procedure and action, but it's possible that that data would have been compromised at Equifax (or one of its competitors) even if those mistakes had not been made. Why? Because of the indefensible position.

The business in which Equifax finds itself requires vast stores of sensitive, personally identifiable information. Data comes into the system in huge streams and must be accessible, via applications and various products, to customers on a constant basis. It is possible that the business requirements (as the business currently exists) is impossible to truly secure. Today's question is whether there exists a CISO who could rise from their "seat at the table" and question the basic premise of the business.

I chose Equifax (and, by extension, the whole credit reporting industry) because it's very visible and has become hugely important. It's not alone in having some basic qualities that may make it impossible to protect. There are other important industries that share many of the same qualities and it's reasonable to ask whether those businesses are so important that any security breaches must be considered a reasonable cost of doing business.

If security is to take its place around the table in the executive suite then security leaders must be ready to talk about the most basic business issues. One of those issues has to be whether the organization has occupied an indefensible position -- and if it has, what to do about the horde rapidly advancing on all fronts.

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
Overcoming the Challenge of Shorter Certificate Lifespans
Mike Cooper, Founder & CEO of Revocent,  10/15/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/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-27621
PUBLISHED: 2020-10-22
The FileImporter extension in MediaWiki through 1.35.0 was not properly attributing various user actions to a specific user's IP address. Instead, for various actions, it would report the IP address of an internal Wikimedia Foundation server by omitting X-Forwarded-For data. This resulted in an inab...
CVE-2020-27620
PUBLISHED: 2020-10-22
The Cosmos Skin for MediaWiki through 1.35.0 has stored XSS because MediaWiki messages were not being properly escaped. This is related to wfMessage and Html::rawElement, as demonstrated by CosmosSocialProfile::getUserGroups.
CVE-2020-27619
PUBLISHED: 2020-10-22
In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.
CVE-2020-17454
PUBLISHED: 2020-10-21
WSO2 API Manager 3.1.0 and earlier has reflected XSS on the "publisher" component's admin interface. More precisely, it is possible to inject an XSS payload into the owner POST parameter, which does not filter user inputs. By putting an XSS payload in place of a valid Owner Name, a modal b...
CVE-2020-24421
PUBLISHED: 2020-10-21
Adobe InDesign version 15.1.2 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious .indd file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required to exploit this vulnerability.