Perimeter
1/18/2013
02:35 PM
Connect Directly
RSS
E-Mail
50%
50%

Acing An Audit In 30 Minutes

Compliance audits don't have to be chaotic events

I asked a client in the insurance business about its recent audit. The president of the company told me that, once again, the audit went fine. Actually, it went better than fine. As usual, it aced the audit. Zero deficiencies, zero issues, zero problems. The auditors said it was the most organized office and easiest file review they had ever seen.

That was impressive, but the best part was yet to come. "How long did it take to prepare for the audit?" I asked. She said her staff spent about 30 minutes preparing for the auditors. Then she added that 15 minutes of that time was making sure the conference room and restrooms were tidy.

Yes, you read that right. Their audit prep time was half an hour.

Want to know how they do this every time? There's no real secret. This company's staff is focused on processes that properly support all necessary business tasks every day.

Security, compliance, documentation, and financial accountability are all built into its processes, not added on later. When there is a new problem that is not addressed with its processes, it doesn't simply address the problem; it learns from it and adjust its processes accordingly.

If a member of the staff encounters a new problem without a process to address it, then the employee brings it to management so a method can be developed to detect and/or address the problem next time.

The company's president told me new employees are either able to adapt to its problem-solving process and high-quality mind set, or they don't make it. In her words, "It's not personal; the process really works out who makes it here."

The president also realized early in the life of the business that a key to supporting processes was the appropriate technology. Instead of using off-the-shelf software, she invested in building custom software that matched her vision of compliant and efficient processes.

Was custom software expensive? Not over time. In fact, the company can now offer significantly more services than its competitors with half of the number of employees. Because the company's software was built with the end in mind, the technology makes audits a breeze, with all necessary data immediately available.

Unlike many organizations, this company never has to really do anything to get ready for an audit. The planning on appropriate and necessary processes, plus the professional discipline to follow the processes, makes them ready for an audit every day.

For this company, audits are not the test of completion and accuracy. It holds itself to that standard every day, through processes and culture. It is a system any organization can build and maintain. All it takes is forethought, adaptability, and discipline.

Glenn S. Phillips loves the company president he just wrote about. He is the president of Forte' Incorporated where he works with business leaders who want to leverage technology and understand the often hidden risks within. 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 Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
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-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.