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.

Comments
Ashley Madison CEO Resigns
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
9/4/2015 | 5:39:26 AM
Re: C-suiters resigning
Other pertinent factors, I think, include the breadth/depth of the breach, and the vulnerabilities (both technical and cultural) that contributed to the breach.

Another important factor: crisis response.  Adobe presents a great example of what not to do.  With their major breach a while back, the company first estimated that just under 3 million customers had been impacted.  They later amended that number to at least 38 million.  Eventually, it was revealed that more than 150 million customers' information was compromised.

Not good for business.
rlynxwiler617
50%
50%
rlynxwiler617,
User Rank: Apprentice
9/1/2015 | 9:45:01 AM
Re: C-suiters resigning
Your two types of companies was exactly what i was thinking when i wrote my response.  If every company has been breached to some degree (and I believe most if not all have already been) then every CxO in the nation should be stepping down at some point in the next few months.  I don't think this individual would have stepped down except for the high media visibility (and, of course, their business purpose), which is why I'm proposing that public perception/press are undeniable factors in who steps down and who doesn't.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
8/31/2015 | 11:25:45 PM
Re: C-suiters resigning
On the one hand, I think your cause-and-effect analysis here is spot on.

On the other hand, there is a popular saying in the security community that I think holds true: "There are two types of organizations -- those that know they have been breached, and those that don't yet know they have been breached."

Which is to say that to a certain degree, hacks -- while mitigatable -- are not wholesale preventable.
SgS125
50%
50%
SgS125,
User Rank: Ninja
8/31/2015 | 11:42:18 AM
Re: C-suiters resigning
Or in some cases it's just a valid result of poor performance just like any other job.  There are consequesnces for not doing a good job at most employers, why should we treat the c level suite any different?
jamieinmontreal
50%
50%
jamieinmontreal,
User Rank: Strategist
8/31/2015 | 9:51:44 AM
Re: C-suiters resigning
This is true, but the effect is then to force other CxOs to look at their organization's security posture and liability differently.   If the buck stops at the CEO's door for a data breach the trickle down effect should be to force tighter security across the organisation.

The Board, in deciding that releasing the CEO port-breach is tacitly agreeing that breach prevention is a strategic, executive level responsibility.   This is no bad thing.
rlynxwiler617
50%
50%
rlynxwiler617,
User Rank: Apprentice
8/29/2015 | 12:34:57 PM
Re: C-suiters resigning
I wonder if it's not so much the gov't regulators as much as saving face with the public.  Maybe the perception is that if I lose the trust of the public because of a breach, I can regain some of that by punishing someone at the highest levels, someone who is more visible than a first line manager.  My experience is that regulators are more concerned with the nuts and bolts of control changes rather than some figure head getting fired.  Who knows.
Joe Stanganelli
100%
0%
Joe Stanganelli,
User Rank: Ninja
8/28/2015 | 11:12:30 PM
C-suiters resigning
One of the main reasons we see C-suiters resigning in the wake of data breaches is because of pressure from politicians and regulatory authorities, who want to see that the company is doing *something*.  Firing/asking the C(x)O to resign is a good step in that direction because it's usually a far preferable action than being subject to heightened regulatory scrutiny and sanctions.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
Modern Day Insider Threat: Network Bugs That Are Stealing Your Data
David Pearson, Principal Threat Researcher,  10/21/2020
Are You One COVID-19 Test Away From a Cybersecurity Disaster?
Alan Brill, Senior Managing Director, Cyber Risk Practice, Kroll,  10/21/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-21269
PUBLISHED: 2020-10-27
checkpath in OpenRC through 0.42.1 might allow local users to take ownership of arbitrary files because a non-terminal path component can be a symlink.
CVE-2020-27743
PUBLISHED: 2020-10-26
libtac in pam_tacplus through 1.5.1 lacks a check for a failure of RAND_bytes()/RAND_pseudo_bytes(). This could lead to use of a non-random/predictable session_id.
CVE-2020-1915
PUBLISHED: 2020-10-26
An out-of-bounds read in the JavaScript Interpreter in Facebook Hermes prior to commit 8cb935cd3b2321c46aa6b7ed8454d95c75a7fca0 allows attackers to cause a denial of service attack or possible further memory corruption via crafted JavaScript. Note that this is only exploitable if the application usi...
CVE-2020-26878
PUBLISHED: 2020-10-26
Ruckus through 1.5.1.0.21 is affected by remote command injection. An authenticated user can submit a query to the API (/service/v1/createUser endpoint), injecting arbitrary commands that will be executed as root user via web.py.
CVE-2020-26879
PUBLISHED: 2020-10-26
Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header.