Risk // Compliance
6/3/2013
11:21 AM
50%
50%

Can't Fix What You Hide

Willful ignorance may be bliss, but rarely is it compliant

The CEO I was talking with didn't understand his own company's compliance requirements. And he didn't want to understand them. He had delegated this, as many in business do, to his IT director. "Technology will fix this problem" is a common approach.

The company's IT director had actually made a good-faith effort to understand the compliance regulations. He had implemented a number of changes to his team's processes and procedures: new password rules, more detailed logging, database security changes, and so forth.

There are actually major problems with this all-too-common approach:

1. Much of compliance and security cannot be addressed through technology alone. Technology is a tool used by people. No matter how great the technology, the "people factor" cannot be ignored.

2. Hiding behind technology, or blaming it, is socially acceptable, unfortunately. Too many business leaders, technology leaders included, shrug off their role in compliance and security with a, "Well, we just need to update our computers," or, "Our servers need more security." This attitude is more than simplistic; it's inaccurate and potentially dangerous.

3. The IT team may be assigned compliance responsibility, but not adequately trained or enabled to deal with many of the regulations. To make this worse, businesses rarely spend the money to educate the IT team on these issues or to bring in an expert to help.

4. IT rarely has the authority to change either business processes or employee behavior. Assigning new passwords and securing databases will not make a system secure if employees have bad habits that leave important information open and available.

5. Many business leaders give only lip service to making priorities of security and compliance. They fail to understand these business functions are not options or add-ons, but, in reality, are outcomes of the business processes they oversee.

Everyone I talked with at the company in question told me security was important. Some even said they were certain their company was compliant with its industry's regulations.

The truth is, the company's leaders were actively deceiving themselves. Compliance is a headache no one wanted to take the time to deal with, and it was easier to assume someone else had already addressed the issue.

The assumption that company data is secure, even without testing or assessments, is common. Assuming compliance is accomplished with a simple IT checklist is common as well, and commonly encourages small risks to grow into enormous ones. The shock when data is lost or a compliance audit fails -- that's common, too.

Ignorance is bliss, but where compliance and data security are involved, it is also an invisible, but completely avoidable, danger to the health of your business.

Glenn S. Phillips does not want you to suffer from avoidable danger. 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
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-4440
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 generates weak non-tty passwords, which makes it easier for context-dependent attackers to guess the password via a brute-force attack.

CVE-2013-4442
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 uses weak pseudo generated numbers when /dev/urandom is unavailable, which makes it easier for context-dependent attackers to guess the numbers.

CVE-2013-7401
Published: 2014-12-19
The parse_request function in request.c in c-icap 0.2.x allows remote attackers to cause a denial of service (crash) via a URI without a " " or "?" character in an ICAP request, as demonstrated by use of the OPTIONS method.

CVE-2014-2026
Published: 2014-12-19
Cross-site scripting (XSS) vulnerability in the search functionality in United Planet Intrexx Professional before 5.2 Online Update 0905 and 6.x before 6.0 Online Update 10 allows remote attackers to inject arbitrary web script or HTML via the request parameter.

CVE-2014-2716
Published: 2014-12-19
Ekahau B4 staff badge tag 5.7 with firmware 1.4.52, Real-Time Location System (RTLS) Controller 6.0.5-FINAL, and Activator 3 reuses the RC4 cipher stream, which makes it easier for remote attackers to obtain plaintext messages via an XOR operation on two ciphertexts.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.