Perimeter
7/18/2012
02:26 PM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Risks Deferred Are Risks Accepted

Decisions to delay compliance and security efforts do not delay the risks

The client did something I’ve seen many times before. The staff considered addressing obvious compliance and security issues, and then decided to postpone that work. While they said they were simply going to push the work back a few months, as typically happens, the postponement became indefinite.

Or perhaps more accurately, the postponement will be indefinite until a costly problem exposes these ignored risks as real, costly and immediate.

Like most clients, they claimed a number of reasons to postpone this work: cash flow, timing, budget restrictions, pending new projects, disruption to other projects, and the time required by management and staff.

Sounding sincere about their need to address these compliance and security issues, clients say, “This is going to be a lot of work, and we need to take care of other matters first so we can better focus on this with less distraction.”

Yet despite claiming to believe compliance and security work is important, clients usually minimize their concerns about risk. After all, they say, as they’ve grown their business, the risks have never materialized, and they really need to put their cash into the growth of the business.

As a business owner, I realize there are times you must make risky decisions. I know there are times where you do have to postpone important work because of something as simple as cash flow or lack of manpower. However, these risky decisions should be made with a sincere evaluation and acceptance of the risks, not by turning a convenient blind-eye and manufacturing emotional justification.

Too many leaders become overwhelmed by the size of the risks they have created -- or allowed to be created -- over time. When these issues become obvious, for whatever the reason, the most common response unfortunately is not to attack these risks full-blast or even to start whittling them down. No, the most common response is to push all these risks into the back of a dark closet where they can be ignored, where they can be put out of sight and out of mind.

Business leaders who decide to defer addressing real security and compliance risks must understand they are essentially self-insuring this risk. They have accepted the risks, even if that acceptance is by default or denial.

If a problem develops from these ignored compliance and security risks, it will be the business that pays the cost, whether it be cash, distraction, reputation, and, perhaps even, sanctions. Perhaps some risks are worth taking, but in most cases I see few leaders acknowledge the true risks and actual consequences. Apparently ignorance is bliss even when the ignorance is by choice.

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand the often hidden 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
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-0460
Published: 2014-04-16
The init script in kbd, possibly 1.14.1 and earlier, allows local users to overwrite arbitrary files via a symlink attack on /dev/shm/defkeymap.map.

CVE-2011-0993
Published: 2014-04-16
SUSE Lifecycle Management Server before 1.1 uses world readable postgres credentials, which allows local users to obtain sensitive information via unspecified vectors.

CVE-2011-3180
Published: 2014-04-16
kiwi before 4.98.08, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands via shell metacharacters in the path of an overlay file, related to chown.

CVE-2011-4089
Published: 2014-04-16
The bzexe command in bzip2 1.0.5 and earlier generates compressed executables that do not properly handle temporary files during extraction, which allows local users to execute arbitrary code by precreating a temporary directory.

CVE-2011-4192
Published: 2014-04-16
kiwi before 4.85.1, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands as demonstrated by "double quotes in kiwi_oemtitle of .profile."

Best of the Web