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

3/15/2012
11:16 AM
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
Comments
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19037
PUBLISHED: 2019-11-21
ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
CVE-2019-19036
PUBLISHED: 2019-11-21
btrfs_root_node in fs/btrfs/ctree.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because rcu_dereference(root->node) can be zero.
CVE-2019-19039
PUBLISHED: 2019-11-21
__btrfs_free_extent in fs/btrfs/extent-tree.c in the Linux kernel through 5.3.12 calls btrfs_print_leaf in a certain ENOENT case, which allows local users to obtain potentially sensitive information about register values via the dmesg program.
CVE-2019-6852
PUBLISHED: 2019-11-20
A CWE-200: Information Exposure vulnerability exists in Modicon Controllers (M340 CPUs, M340 communication modules, Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions), which could cause the disclosure of FTP har...
CVE-2019-6853
PUBLISHED: 2019-11-20
A CWE-79: Failure to Preserve Web Page Structure vulnerability exists in Andover Continuum (models 9680, 5740 and 5720, bCX4040, bCX9640, 9900, 9940, 9924 and 9702) , which could enable a successful Cross-site Scripting (XSS attack) when using the products web server.