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

4/20/2012
09:35 AM
50%
50%

You Need Help, Not An Accomplice

Compliance is about being better and not just proving you are right

I met recently with a potential client to discuss a proposed HIPAA and HITECH compliance assessment. Doing a quick run-through of their current status, I quickly realized there were some problems, the biggest one being the client's perspective on the current situation.

The first problem I uncovered is very common in every line of consulting work: this potential client was not really looking for better answers; they were looking for an accomplice. They wanted their solution to be validated and endorsed instead of evaluated and improved.

The second problem was the staff's compliance work, which was woefully incomplete and which they had no interest in acknowledging. They repeatedly cited the things they had done correctly, but had total disregard for the missing elements of the work. Sure they had an encrypted database, ran updates and patches regularly, and had strong password policies. It was not the completed tasks that were my concern -- it was that these alone did not bring them anywhere close to reasonable compliance.

The staff was quite insistent that their plan made them completely secure and that no extra work or cost would be necessary. I was asked only to approve their work so they could pass along our third-party review to their own clients as proof they were indeed compliant.

If only that were the situation. The staff asserted that because they used a software firewall, a hardware firewall was not necessary. They had never tested a full restore of their backup, had no documentation for configuring a secure server from scratch, and offsite backup was only once a month.

I pointed out that the issues that concerned me went far beyond compliance issues, they were business risk issues. The poor CEO didn't know who to believe. She clearly trusted her IT staff and had distanced herself so much from oversight of this department, she had left herself at their mercy. She had neither the expertise to overrule them nor the understanding to reach her own independent conclusions.

I got the impression she perceived the entire exercise as a discussion of expensive, never-ending technology magic, when she really wanted simply the quickest, cheapest conclusion so she could go back to pretending all was well.

The risks we uncovered were dismissed by her IT staff as either irrelative or not applicable to their company. "We know how to set up a server, and technology changes so often, we shouldn’t waste our time with a document no one will read anyway," sums up their attitude.

I could tell this IT staff also suffered the common unspoken fear, "If we document everything, we can more easily be replaced."

In the end, staff dysfunction won out, which is just as well, as my employees are not corporate social counselors, and I doubt our recommendations would have been followed anyway. It would have wasted the client's money and risked my company’s reputation. And realistically, they may be in great shape, at least as long as nothing ever goes wrong.

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand risks within. He is the author of the book Nerd-to-English and you can find him on twitter at @NerdToEnglish. 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
Windows 10 Migration: Getting It Right
Kevin Alexandra, Principal Solutions Engineer at BeyondTrust,  5/15/2019
Artist Uses Malware in Installation
Dark Reading Staff 5/17/2019
Baltimore Ransomware Attack Takes Strange Twist
Kelly Jackson Higgins, Executive Editor at Dark Reading,  5/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12198
PUBLISHED: 2019-05-20
In GoHttp through 2017-07-25, there is a stack-based buffer over-read via a long User-Agent header.
CVE-2019-12185
PUBLISHED: 2019-05-20
eLabFTW 1.8.5 is vulnerable to arbitrary file uploads via the /app/controllers/EntityController.php component. This may result in remote command execution. An attacker can use a user account to fully compromise the system using a POST request. This will allow for PHP files to be written to the web r...
CVE-2019-12184
PUBLISHED: 2019-05-19
There is XSS in browser/components/MarkdownPreview.js in BoostIO Boostnote 0.11.15 via a label named flowchart, sequence, gallery, or chart, as demonstrated by a crafted SRC attribute of an IFRAME element, a different vulnerability than CVE-2019-12136.
CVE-2019-12173
PUBLISHED: 2019-05-18
MacDown 0.7.1 (870) allows remote code execution via a file:\\\ URI, with a .app pathname, in the HREF attribute of an A element. This is different from CVE-2019-12138.
CVE-2019-12172
PUBLISHED: 2019-05-17
Typora 0.9.9.21.1 (1913) allows arbitrary code execution via a modified file: URL syntax in the HREF attribute of an AREA element, as demonstrated by file:\\\ on macOS or Linux, or file://C| on Windows. This is different from CVE-2019-12137.