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/25/2013
01:59 PM
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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Another COVID-19 Side Effect: Rising Nation-State Cyber Activity
Stephen Ward, VP, ThreatConnect,  7/1/2020
Lessons from COVID-19 Cyberattacks: Where Do We Go Next?
Derek Manky, Chief of Security Insights and Global Threat Alliances, FortiGuard Labs,  7/2/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15599
PUBLISHED: 2020-07-07
Victor CMS through 2019-02-28 allows XSS via the register.php user_firstname or user_lastname field.
CVE-2020-8916
PUBLISHED: 2020-07-07
A memory leak in Openthread's wpantund versions up to commit 0e5d1601febb869f583e944785e5685c6c747be7, when used in an environment where wpanctl is directly interfacing with the control driver (eg: debug environments) can allow an attacker to crash the service (DoS). We recommend updating, or to res...
CVE-2020-12821
PUBLISHED: 2020-07-07
Gossipsub 1.0 does not properly resist invalid message spam, such as an eclipse attack or a sybil attack.
CVE-2020-15008
PUBLISHED: 2020-07-07
A SQLi exists in the probe code of all Connectwise Automate versions before 2020.7 or 2019.12. A SQL Injection in the probe implementation to save data to a custom table exists due to inadequate server side validation. As the code creates dynamic SQL for the insert statement and utilizes the user su...
CVE-2020-8519
PUBLISHED: 2020-07-07
SQL injection with the search parameter in Records.php for phpzag live add edit delete data tables records with ajax php mysql