Perimeter

3/8/2012
02:24 PM
50%
50%

Six Things Management Needs To Better Understand About Compliance

It may be boring or scary to management, but compliance is ultimately their burden to bear

Compliance with HIPAA, PCI, and host of other regulations and laws is often seen by business leaders as just an expensive IT project. "Just throw technology at it and let me know when you’re done." Well, it doesn't work that way.

Granted, there are some IT professionals who will accept this approach because it grants them more power and reduces oversight of their work. After all, dealing with a disinterested, nontechnical boss is not fun or effective. The best-run organizations have management who knows their important role in compliance.

In my work, here are six things I believe senior management and business owners must understand to have companies that are compliant with their required standards, laws, and regulations.

1. Compliance is not a homework assignment -- it is how your organization operates every day.
Sure, you may pass an audit on occasion, but audits are not a check of how you did today. The audits are a look at how you operate day in and day out; what is the process, how is it managed, how is it tracked, and how can you prove it?

2. Management has responsibilities that cannot be delegated.
For example, it should never be your IT staff's responsibility to decide how long to keep archived emails. That is a legal decision that should be defined in management's policy, managed by IT processes, and verified by either management or someone not in IT.

3. Systems are not compliant -- organizations are compliant.
Computer systems do not operate in a vacuum. They are tools for employees. Companies are the people and their tools doing something. Compliance is about how the something works, not just the tools.

4. Employees and business processes are typically a much bigger problem for compliance and security than computer systems.
Study after study has found that network breaches and hacking result in far fewer problems than sloppy processes and employee behavior.

5. Management does not have to become technical, but it does have to demand its technical staff communicates effectively.
All too often, senior executives delegate their leadership responsibility, believing they can't possibly understand all of the details their technical staff brings to them. I contend they should not have to become technical, but they should require their technical staff be business-conversant. Plain language is the best business tool, and every specialty in a business can be discussed sensibly this way.

6. Accurate self-assessment is extremely difficult.
Think about how often someone proofreading your writing finds a problem. The same goes for the far more complex processes and procedures required for compliance. The more removed from the day-to-day aspects of a business or department, the easier it is to spot issues. Even if not required, an outside auditor (or even just someone from another department) may be more effective at a lower cost than your own staff spending hours hoping to see through their own mental filters.

Organizational leadership cannot delegate compliance; it must come from their leadership. Without the proper support, participation, and leadership, compliance becomes only more expensive, time consuming, and, sometimes, impossible.

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

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
Comments
Newest First  |  Oldest First  |  Threaded View
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Number of Retailers Impacted by Breaches Doubles
Ericka Chickowski, Contributing Writer, Dark Reading,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14492
PUBLISHED: 2018-07-21
Tenda AC7 through V15.03.06.44_CN, AC9 through V15.03.05.19(6318)_CN, and AC10 through V15.03.06.23_CN devices have a Stack-based Buffer Overflow via a long limitSpeed or limitSpeedup parameter to an unspecified /goform URI.
CVE-2018-3770
PUBLISHED: 2018-07-20
A path traversal exists in markdown-pdf version <9.0.0 that allows a user to insert a malicious html code that can result in reading the local files.
CVE-2018-3771
PUBLISHED: 2018-07-20
An XSS in statics-server <= 0.0.9 can be used via injected iframe in the filename when statics-server displays directory index in the browser.
CVE-2018-5065
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
CVE-2018-5066
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.