Perimeter
3/25/2013
01:59 PM
Connect Directly
RSS
E-Mail
50%
50%

Mission Impossible: 4 Reasons Compliance Is Impossible

Compliance, like security, is not a constant

It happened again. I heard a boastful manager tell the CEO the job was finished and with great confidence brag to his boss their organization was fully compliant. The CEO nodded with increasing approval, mentally embracing the idea that his worries on the matter were behind him for good. No money-grubbing consultant was going to fool him about “risks,” and technical managers would no longer dare ask for larger budgets for compliance needs. In his mind, the task had now been addressed and the goal reached, never to look back again.

If only the CEO had paid enough attention to the realities of situation rather than so quickly accepting a convenient delusion.

Maybe not today, maybe not this week, but soon, this CEO will pay for this mistake many times over. And worse, as long as he maintains his distance from the reality of the issue, this CEO will never understand the associated costs are completely his fault. Protecting his company in a meaningful way, and avoiding perhaps millions in unnecessary expenses, was his responsibility and was completely within his power to accomplish. He simply didn’t take the time to understand one simple fact about his company: compliance, like security, is not a constant.

No organization is completely compliant, just as total security is not possible. Why, you ask? It is really very simple.

1. People are involved. Technology can do many wonderful things, but at the end of the day it is only a tool created by people, used by people, and dependent on people. People make mistakes. Some lie, cheat, and steal. Others are incompetent or apathetic. Even the hardest working and most conscientious will occasionally make a mistake. Compliance and security are never complete because people are a big part of the risk chain.

2. Change is constant. Even an organization that somehow (magically) becomes completely secure and fully compliant in technology, procedures, and behavior today, by tomorrow, there will be new variables and new risks. Employees come and go, behaviors change day-to-day, technology advances, and risks keep evolving.

3. Compliance is interpreted, not defined. While laws and regulations can be extremely detailed and address a large number of circumstances, they can never completely define how to address every situation.

You may be able to complete a compliance or security checklist, but that will not make you fully compliant. It merely makes your list of identified issues or tasks complete. There will remain regulations you must choose how to apply to your company’s unique situation, problems that require unique solutions.

4. Technology is a tool, not a complete solution. I see way too many corporate leaders and technology managers who presume technology alone is responsible for data security and operational compliance.

Too many non-technical business leaders want an easy fix, a magic pill, they can just order up and consider the issues addressed. Likewise, I regularly see technology leaders who are all too happy focusing only on their tools. They are ill-equipped, or sometimes simply disinterested, in working with the aspects of compliance that involve their personnel.

The best leaders save money and time by understanding that compliance and security are processes, not outcomes. These processes continually change because people, risk, and technology continually change. Full compliance is impossible. However outstanding compliance behavior is not only possible, but also healthy and cost-effective.

Glenn S. Phillips knows perfect writing is impossible, but he keeps trying. He is the president of Forte' Incorporated where he works with business leaders who want to leverage technology and understand the often hidden risks awaiting them. Glenn 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
Register for Dark Reading Newsletters
Partner Perspectives
What's This?
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.

As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Featured Writers
White Papers
Cartoon
Current Issue
Dark Reading's October Tech Digest
Fast data analysis can stymie attacks and strengthen enterprise security. Does your team have the data smarts?
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-2013-7407
Published: 2014-10-22
Cross-site request forgery (CSRF) vulnerability in the MRBS module for Drupal allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.

CVE-2014-3675
Published: 2014-10-22
Shim allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted DHCPv6 packet.

CVE-2014-3676
Published: 2014-10-22
Heap-based buffer overflow in Shim allows remote attackers to execute arbitrary code via a crafted IPv6 address, related to the "tftp:// DHCPv6 boot option."

CVE-2014-3677
Published: 2014-10-22
Unspecified vulnerability in Shim might allow attackers to execute arbitrary code via a crafted MOK list, which triggers memory corruption.

CVE-2014-3828
Published: 2014-10-22
Multiple SQL injection vulnerabilities in Centreon 2.5.1 and Centreon Enterprise Server 2.2 allow remote attackers to execute arbitrary SQL commands via (1) the index_id parameter to views/graphs/common/makeXML_ListMetrics.php, (2) the sid parameter to views/graphs/GetXmlTree.php, (3) the session_id...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Follow Dark Reading editors into the field as they talk with noted experts from the security world.