Re:Panerabread.com leaks millions of customer records
by smileysteve on Tuesday April 03, 2018 @08:19AM
(#16743909)
Pull the plug.
The final "stick" and reason for a C in the title is the responsibility to shut down the data (and website) until such a point it can be secured.
It's should be considered more of a fiduciary duty (protect shareholders, customers) to protect data as making the right investment or HR decisions.
Re:Panerabread.com leaks millions of customer records
by tptacek on Tuesday April 03, 2018 @12:08PM
(#16746073)
"Pulling the plug" is almost never a capability provided to a company security team.
Re:Panerabread.com leaks millions of customer records
by tedunangst on Tuesday April 03, 2018 @11:35AM
(#16745646)
What happens when the CIO plugs it back in?
Re:Panerabread.com leaks millions of customer records
by smileysteve on Thursday April 05, 2018 @01:09PM
(#16766755)
The CIO then accepts full liability.
Re:Panerabread.com leaks millions of customer records
by benmmurphy on Tuesday April 03, 2018 @12:31PM
(#16746337)
If we were running under the liability model the CSO's final option would be to resign which sucks. But he is basically in the same situation that any employee is who is being forced to do something that is clearly illegal. But, I guess that is a good argument for why liability might not work because you end up not having a security team or you put good people into legal dilemmas that they shouldn't have to deal with.
Re:Panerabread.com leaks millions of customer records
by PakG1 on Thursday April 05, 2018 @09:07PM
(#16770168)
For example (issue may or may not have been legal, but point is the guy resigned): https://arstechnica.com/tech-policy/2016/10/report-fbi-andor...
Re:Panerabread.com leaks millions of customer records
by notyourday on Tuesday April 03, 2018 @08:24AM
(#16743943)
Which is why we need jail time for execs.
It is very simple: with big $$ there should be a big risk.
This security director handled Dylan's bug report badly and deserves the reputation hit he's getting. But if we're going to suggest liability (let alone criminal liability) for security flaws, we should at least have some idea of what it is we're regulating.