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

6/18/2010
01:31 PM
Rob Enderle
Rob Enderle
Commentary
50%
50%

BP And The Importance Of Calling Out Corruption

A recent article in Rolling Stone shows how the combination of a corrupt process for ensuring the safety of oil rigs, corruption of the information on the risk, the actual BP disaster -- and politics -- has resulted in the biggest environmental disaster in the country's history. It also mirrors a massive problem in IT security where political expediency, short-term financial gains, and personal benefits often trump good business practice.

A recent article in Rolling Stone shows how the combination of a corrupt process for ensuring the safety of oil rigs, corruption of the information on the risk, the actual BP disaster -- and politics -- has resulted in the biggest environmental disaster in the country's history. It also mirrors a massive problem in IT security where political expediency, short-term financial gains, and personal benefits often trump good business practice.Rooting out corruption should remain a high priority for any security organization, but it's not often taken seriously enough. (Here's Rolling Stone's Investigative Report on the BP Oil Spill, by Tim Dickenson.)

One of the first experiences I had with corruption was while running an internal audit team for a large multinational company. We ran into a problem where the U.S. government had been intentionally overbilled by $1 million, but it fell outside the scope of our team's work, and this practice had been overlooked by another team that had done a review before us. After attempting to escalate and resolve the problem, it became clear the political fallout would adversely impact the senior management of the firm, and I got the, "If you carry this forward, then your career is over" talk.

Regretfully, I was both young and newly married, so backed down. It is one of my life's regrets.

But this highlights the problem with even wanting to investigate corruption: The person doing the investigation, regardless of the outcome, is putting his or her job and career at risk. No one should have to choose between doing the right thing and his or her own future ever -- let alone on a regular basis.

Having faced this problem myself and chosen badly, it is hard for me not to feel sympathy for those in the Minerals Management Service who tried to point out the problems that resulted in the spill. In fact, the article clearly showcases that people who might have been able to help prevent the disaster would have been passed over for promotion or managed out of the agency under both parties.

If it's a career-killer to focus on corruption, then why should you still focus on it?

Just look at what is happening to BP and the satisfaction rating of the Obama administration. It is likely that this one spill will cause BP to fail and Obama to be a one-term president. The fallout of the disaster is already resulting in broad staffing changes in the Minerals Management Service, and the result will likely be that the majority of folks that covered up these bad practices will lose their jobs and careers. As the investigations continue, many could end up broken financially or incarcerated for extended periods of time.

Allowing corruption might seem like the easier path, but it is potentially a company-killer, and employees who are fired or laid off from a firm or organization that has been tainted by corruption generally find themselves pariahs in a tight job market.

In the end, your real choice when it comes to investigating and reporting corruption isn't report it or save your career. It's report it or resign. In fact, in many cases you might have to report it and resign, but in the end you'll likely be better off long-term than if you allow it to continue because then you are likely to be fired and be unemployable.

It isn't particularly heroic if the personal reward for a particular action is clear. In this case, however, the alternative to not being heroic is vastly worse, and playing the hero and investigating and reporting corruption is in your own best interest. In my own case, I still regret folding under pressure, and both changed careers and changed that practice after doing it that once.

Here is hoping you can learn from my example and this BP case and not have to live with making this mistake yourself.

-- Rob Enderle is president and founder of Enderle Group. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Lessons from the NSA: Know Your Assets
Robert Lemos, Contributing Writer,  12/12/2019
4 Tips to Run Fast in the Face of Digital Transformation
Shane Buckley, President & Chief Operating Officer, Gigamon,  12/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19807
PUBLISHED: 2019-12-15
In the Linux kernel before 5.3.11, sound/core/timer.c has a use-after-free caused by erroneous code refactoring, aka CID-e7af6307a8a5. This is related to snd_timer_open and snd_timer_close_locked. The timeri variable was originally intended to be for a newly created timer instance, but was used for ...
CVE-2014-8650
PUBLISHED: 2019-12-15
python-requests-Kerberos through 0.5 does not handle mutual authentication
CVE-2014-3536
PUBLISHED: 2019-12-15
CFME (CloudForms Management Engine) 5: RHN account information is logged to top_output.log during registration
CVE-2014-3643
PUBLISHED: 2019-12-15
jersey: XXE via parameter entities not disabled by the jersey SAX parser
CVE-2014-3652
PUBLISHED: 2019-12-15
JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL.