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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-8142
Published: 2014-12-20
Use-after-free vulnerability in the process_nested_data function in ext/standard/var_unserializer.re in PHP before 5.4.36, 5.5.x before 5.5.20, and 5.6.x before 5.6.4 allows remote attackers to execute arbitrary code via a crafted unserialize call that leverages improper handling of duplicate keys w...

CVE-2013-4440
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 generates weak non-tty passwords, which makes it easier for context-dependent attackers to guess the password via a brute-force attack.

CVE-2013-4442
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 uses weak pseudo generated numbers when /dev/urandom is unavailable, which makes it easier for context-dependent attackers to guess the numbers.

CVE-2013-7401
Published: 2014-12-19
The parse_request function in request.c in c-icap 0.2.x allows remote attackers to cause a denial of service (crash) via a URI without a " " or "?" character in an ICAP request, as demonstrated by use of the OPTIONS method.

CVE-2014-2026
Published: 2014-12-19
Cross-site scripting (XSS) vulnerability in the search functionality in United Planet Intrexx Professional before 5.2 Online Update 0905 and 6.x before 6.0 Online Update 10 allows remote attackers to inject arbitrary web script or HTML via the request parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.