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.

Perimeter

2/14/2012
11:11 AM
50%
50%

Being A Security Bully Does Not Make You Compliant

Compliance is not a tool for dodging work or dismissing business needs

Working with large organizations that have large IT staffs, we often encounter who I call “Security Bullies.” These people use compliance as a weapon against everyone, building a bureaucratic infrastructure that is their own private kingdom. While the Security Bully might be an individual, it is more common that the entire IT staff has taken on this behavior.

One easy sign to tell whether you have a Security Bully is the use of compliance as a way to deny most requests for support or changes (or sometimes even help). Even worse, Bullies use compliance as a means to say “no” without having to develop meaningful solutions.

For example, my team developed and supports the software used to operate one specialized department of a large medical center. The software is used for both business and logistical purposes. Some patient data is involved, so HIPAA is applicable. Citing security and compliance requirements, the medical center’s IT staff now exclusively manages the server where the application and database resides.

Recently there was a problem we traced to be a likely issue on the database server. (I say likely, of course, because even though we reproduced the problem and solution on our test server, one only proves a theory by actually solving the problem.)

While it was somewhat obscure, we found a documented database server issue that matched our problem. A hot patch for the server was available to address the problem. Without clearance to work directly on the server, we gave the client’s IT staff our suggested solution and how we arrived at it.

The response back was a detailed list of reasons why the hot patch could not be installed on the server, many of them being security, department, and regulatory rules, without any alternate plan, option, or offer of assistance for the department.

On closer examination, this reply turned out to be a list of excuses to avoid dealing with the department’s problem, since some of their arguments against the hot patch were within their ability and authority to address.

Once I politely reminded the IT staff that their rules prohibited us from direct work on this server and that ultimately it was their responsibility to keep the system working, their rules quickly became more flexible. They installed the patch quickly -- and without even running it on a test server first.

I found the omission of a test server step particularly interesting. When they thought we would have to do all of the work, their list of requirements prior to hot patch installation included setup of another test server (in addition to the one we had in our office). Apparently "the rules" changed once it became their work.

I share this story not to complain, but as a reminder. It is easy to become so focused on compliance and security that we forget the purpose of the organization or the support role of IT. Compliance is important, but it is not a tool for dodging inquiries or work, particularly when the requests are important to an organization's ability to function well.

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand risks within.

Glenn works with business leaders who want to leverage technology and understand the often hidden risks awaiting them. The Founder and Sr. Consultant of Forte' Incorporated, Glenn and his team work with business leaders to support growth, increase profits, and address ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/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-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...