Welcome Guest. | Log In | Register | Membership Benefits
Dark Reading's security-views Weblog

Topics:   Security Views : Compliance Tech Center

Five Dangerous Compliance Assumptions

Many businesses fool themselves about their compliance problems

Feb 23, 2012 | 11:12 AM | 

By Glenn S. Phillips
Dark Reading

After 20 years of working with clients, I am still left shaking my head at the number of companies that declare with great confidence they are “fully compliant” when it is obvious they are not even close.

I think we all understand that compliance means conforming to applicable rules, typically specifications, policies, standards, or laws. Seems simple enough, right? Apparently not.

I find many organizations, especially those with fewer than 200 employees, that are claiming full compliance but have rarely even read the full requirements. This is particularly true in industries where compliance has no official compliance certification, such as HIPAA. They may have skimmed over a summary of the requirements, usually choosing to ignore certain parts by convincing themselves these rules don’t apply to them. These decisions are often made by a single employee, who then proclaims the company compliant and enables his or her fellow employees to blindly accept, and even promote, this convenient, but false, claim.

Companies that incorrectly claim compliance are usually making too many assumptions, some that benignly support their arguments, but others that dangerously fuel false beliefs concerning these companies’ capabilities or security.

Here are five dangerous compliance assumptions I see frequently:

1. “We’re secure -- that makes us compliant. We use passwords and firewalls.”
Whether I uncover it in an onsite assessment or in casual discussions with management, this belief is surprisingly common. Even if the IT team knows it not to be true, if management “feels safe,” they “feel secure.” It is an easy stretch to assume “feeling” secure means legitimate compliance with meaningful security standards.

2. “The IT manager said we are complaint.“
I think the old Russian proverb addresses this one best: Trust but verify. Every good organization has checks and balances throughout, even small organizations.

Bookkeepers are checked by accountants, who are checked by external CPAs. When I write, I have someone proofread my work and then an editor checks it. Having more than one point of confirmation is critical, as even the best of us can miss something important.

3. “Strong physical security is not really necessary here, we are all trustworthy.”
While that is admirable to think, it is usually just a lazy excuse to avoid restricting access to those who don’t actually need it. Or sometimes it can be a social problem: “Oh, Sally will think we don’t trust her if we restrict her access to the server room or that database.” Security is not about trust. It is about following a process designed to protect everyone, including Sally, and your other employees.

4. “Really complex, frequently changing passwords are the most secure.”
This assumption totally ignores the human component of security. Is a really complex password more secure from hacking tools? Sure. But far more security breaches come from access to passwords written down because they are too complex to remember. I don’t know many people who can remember “Er55%P22eRq12121z,” and to expect anyone to is foolish.

5. “The computer has a login, so it is secure.”
Unrestricted physical server and computer access is incredibly common in small organizations and retails stores. It is not uncommon in medical practices for the server room to be a closet, with the door left open so the equipment won’t overheat. If someone steals the server or a computer, they will then have as much time as they want to bypass your login. Your equipment might be more easily stolen than you realize.

Naturally, there are dozens of dangerous assumptions a company can make -- some more obvious than others. Because compliance requires a specific mindset, including changes to routines and embracing new habits, it can be like eating healthier or getting more regular exercise: We know it is very important, possibly even lifesaving, but often we don’t take action until it’s too late.

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand risks within.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
  June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
 
Featured Webcasts
Featured Whitepapers
Featured Reports