Perimeter
4/16/2012
11:26 AM
Connect Directly
RSS
E-Mail
50%
50%

Your Compliance Is Decaying Every Day

As soon as you train your colleagues about compliance, noncompliance is back in charge

As soon as you train staff, implement new technology, and make business process changes to become (or remain) compliant, the next day you are already less compliant. People's habits are hard to break, and what we are taught begins to fade within hours.

At the same time, risks to technology and security never rest or stop changing, whether from smarter malicious technology or simply the pace an organization’s technology continues to be updated and modified. It can be hard to monitor and verify for compliance without slowing down the necessary pace of business.

In a discussion I had with one CEO who was concerned about the expense of training, he said, “What if I spend all this money training my staff, and they leave? Then I’ve wasted all that time and money.” As politely as I could, I leaned over and quietly said, “What if you don’t train them, and they stay?”

He paused a moment, processing my question. I was relieved when he smiled and gave that nod we all give when we’ve had an “a-ha” moment. Training is not an extra, and its related costs are not optional. Training is something we pay for when we choose to do it, but it’s also something we pay for when we choose not to.

Untrained staff, like everyone else, will develop habits in their work. Without training, these will more often than not be bad habits that cost organizations money. This cost might not have its own line item -- it might be hidden in payroll and hard to identify immediately -- but it will be there. On the other hand, ongoing training helps your staff know the expectations and requirements of a job well done.

Organizations that do not include regular training and coaching for all aspects of their business operations typically see such education as an extra expense they can defer (or ignore). Oh, they claim they know training is important, but if they don’t show any commitment in either time or budget, they are deceiving themselves. This mindset applies to compliance, as well, because true compliance requires specific processes to be part of your daily operations, not add-on tasks at the end of projects.

Proper compliance training is really about much more than compliance. It is about how to perform work that includes compliant processes and procedures. The actions that lead to better compliance cannot be bolted on at the end of training or in separate compliance classes.

While annual training is better than no training at all, few of us recall the details of classes we took months ago. Effective training is intentionally designed to regularly reinforce processes that are compliant, secure, and healthy for the organization. Like fighting decay, being compliant requires regular updates, repairs, and attention. Compliance is your best effort toward maintaining the health of your company.

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand risks within. He 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
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.