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
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11107
PUBLISHED: 2020-04-02
An issue was discovered in XAMPP before 7.2.29, 7.3.x before 7.3.16 , and 7.4.x before 7.4.4 on Windows. An unprivileged user can change a .exe configuration in xampp-contol.ini for all users (including admins) to enable arbitrary command execution.
CVE-2020-11444
PUBLISHED: 2020-04-02
Sonatype Nexus Repository Manager 3.x up to and including 3.21.2 has Incorrect Access Control.
CVE-2020-7617
PUBLISHED: 2020-04-02
ini-parser through 0.0.2 is vulnerable to Prototype Pollution.The library could be tricked into adding or modifying properties of Object.prototype using a '__proto__' payload.
CVE-2020-8835
PUBLISHED: 2020-04-02
In the Linux kernel 5.5.0 and newer, the bpf verifier (kernel/bpf/verifier.c) did not properly restrict the register bounds for 32-bit operations, leading to out-of-bounds reads and writes in kernel memory. The vulnerability also affects the Linux 5.4 stable series, starting with v5.4.7, as the intr...
CVE-2020-8423
PUBLISHED: 2020-04-02
A buffer overflow in the httpd daemon on TP-Link TL-WR841N V10 (firmware version 3.16.9) devices allows an authenticated remote attacker to execute arbitrary code via a GET request to the page for the configuration of the Wi-Fi network.