4 ms·
It would be helpful to include what specifically went wrong when there is a security incident at your company. Every failure should be a learning opportunity fo
by pg_bot 7y ago
It would be helpful to include what specifically went wrong when there is a security incident at your company. Every failure should be a learning opportunity for others. Perhaps there should be some sort of safe harbor for disclosing security compromises as it benefits the greater community.
I can understand why you'd want to cover your ass in this type of situation. However, I think keeping these things secret leads to more harm over time as people brush off weaknesses in their own systems for lack of concrete examples of where it caused harm.
Was an employee careless with credentials? Was some service not updated? Was it a typical attack like a SQL injection that caused the leak? Having more real world info helps people model threats better.
- peeters 7y agoI wouldn't take this disclosure as an indication that they won't do a public post-mortem. The latter takes time and you want to get it right and to be thorough, on the other hand you want the disclosure to come as soon as possible for users' security.
- yingw787 7y agoYeah, I would have liked to see them commit to a comprehensive post-mortem in the Q&A.