Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

5/17/2012
02:42 PM
50%
50%

Manage Risk As A Strategy, Comply With Regulations As A Tactic

Compliance alone should never be the only goal

Good business management makes it easier and safer to run a business correctly. And as a benefit, this makes compliance with applicable regulations and laws easier and natural, not merely a huge distraction.

I have a prospective client I have met with occasionally for a couple of years. They are in constant agony about how they can meet regulation requirements, deal with the associated cost, and find the time required to focus on compliance. At the same time, many of their business processes and computer systems are a patchwork fraught with very real risks and expensive manual processes. Their mindset is to find a cheap compliance approach to "add on" to their current systems and work procedures.

I have failed to get this prospective client to recognize that, while compliance is very important, the biggest risks to business survival are their current processes, procedures, and systems. They are literally only one big internal failure away from closing the doors for good. In the meantime, they keep searching for an unrealistically inexpensive compliance plan that will fit their one-of-a-kind approach to business.

These business leaders have an emotional need, not a logical approach. Out of habit, they feel safe with their current operations and have become blind to the dangers. With these obstacles firmly in place, it’s clear that nothing is going to change until it’s too late.

The irony of this situation is that, if this company leadership truly addressed their operational risks and flawed processes, almost every one of their compliance issues would be addressed with little extra effort or cost.

For many organizations, I recommend using compliance as a guide to improving their businesses. Regardless of your industry or applicable laws and regulations, compliance efforts include a focus on security, processes, procedures, documentation, oversight, and planning. By working to become compliant, or by maintaining compliance, businesses actually have a great guide to addressing many of their business risks. The guidelines for compliance in any industry can give businesses discreet actions to take, measurable outcomes, and documented metrics.

Regulations and laws can seem like a costly burden for organizations. There are costs of time, attention, and money to ensure compliance. We find the best-run companies understand that compliance with their applicable requirements is not an add-on task. In fact, they don’t even consider compliance to be an end goal. The best-run companies understand compliance is a valuable added benefit of simply running their businesses well.

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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.