Tarring and feathering technologists who happen to be in the vicinity of e.g. security errors will not successfully achieve resolutions for the process flaws which allowed those errors to happen.
-
-
"Someone robbed the bank and now depositors have lost their money!" "THEY SHOULD MAKE A LAW!" We *had the law*! The money is still gone! There need to be a few dozen things that a bank does as a matter of course because it is in a universe where crime exists!
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Technologists in the vicinity of a security error and a CSO at a company which had a security breach are two very different things. I see the argument is more about accountability than criminality.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Almost any company <10 years old, likely has had many, many, many security breaches that just weren’t publicized. What do you call it when a sysadmin runs “mongodump?”
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Being a CSO already appears to be a tough enough job as is. In many cases the role seems positioned to take the fall in the event of a breach. Until data breaches cost shareholders significant money this will keep happening. Make data a liability.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.