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
WSJ Report: Facebook Breach the Work of Spammers, Not Nation-State Actors
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/19/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
NC Water Utility Fights Post-Hurricane Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  10/16/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.