Perimeter
3/15/2012
11:16 AM
Connect Directly
RSS
E-Mail
50%
50%

Nobody Cares About HIPAA

Compliance in many organizations is seen as only a costly inconvenience

Sometimes clarity comes out of the blue, including clarity about compliance issues. Recently I was meeting with friend and business associate Ben Drake. His company works with networking and data protection technology for a number of businesses.

I mentioned how some organizations with obvious HIPAA compliance issues seem uninterested in putting forth the effort to resolve them. Some won’t even acknowledge they have issues. Ben shrugged and matter-of-factly said, "Nobody cares about HIPAA."

That took a minute to soak in, but I got his point. Knowing Ben, I knew his comment was not literal and was for effect. But generally speaking, he has a strong point. In the greater scheme of many businesses, HIPAA (and other regulations) are commonly seen by management and staff as an annoyance and another meaningless expense.

Some organizations make only token efforts toward compliance, and those efforts are typically the least that can be done for the least cost. There is often an incomplete, one-time effort to "get compliant," but nothing much more after that. In Ericka Chickowski’s recent article "Healthcare Security Pros Need To Speak The Language Of Finance," Rick Kam pointed out that healthcare security issues “basically put the CFO and the CEO to sleep because they're talking compliance, talking costs, and talking about things that are not that interesting to these executives."

While there are exceptions, I think Kam's observation is THE reality for many organizations, even if no one will openly admit it. A common course of action by this type of leadership is usually one of three approaches: postpone, ignore, or delegate.

Postponement is easy to emotionally justify: "I'm very busy. I need to wait until I have time to really understand everything and not make a bad decision." The problem here is that security dangers don't care whether you wait; they will continue to put the organization's information and reputation at risk.

Ignoring the issue is popular, even if it is in the disguise of pretending to address the problem. Typically this is uncovered in audits where the organization convinced itself that difficult passwords and encrypted drives were all they needed to be compliant. The full picture of compliance was never identified, acknowledged, or funded.

Leaders who delegate security usually convince themselves they are handing a complex or technical task to someone who is more knowledgeable. That may be true to a point, but what they usually also do is inappropriately delegate the oversight of processes and the leadership critical for compliance and security. This approach then creates a host of new problems.

There is an old saying that you can tell what is genuinely important to someone (or to a company) by ignoring their words and simply watching where they spend their time and money. In many organizations, this simple test cuts through the emotion-based excuses and exposes who really understands the risks and benefits of compliance.

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 Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
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-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.