Thompson88

5 ms·

1. 1.▲
   Organizations are changing cybersecurity providers in wake of CrowdStrike outage(helpnetsecurity.com)

   1 points by Thompson88 2y ago|0 comments
2. 2.▲
   Lessons from CrowdStrike outage and Amazon's playbook(calcalistech.com)

   1 points by Thompson88 2y ago|0 comments
3. 3.▲
   by Thompson88 2y ago

   Confirmed: It was a management problem. I noticed in CrowdStrike's post mortem report that they didn't say a thing about management.
4. 4.▲
   by Thompson88 2y ago

   Two months on from the global IT outage on 19 July, the full impact is still only now becoming apparent.
5. 5.▲
   CrowdStrike: Company to face questions over global IT outage(bbc.com)

   1 points by Thompson88 2y ago|1 comments
6. 6.▲
   by Thompson88 2y ago

   The concentration of so much mission-critical technology in the hands of a few large suppliers makes incidents like the Microsoft-CrowdStrike outage all the more dangerous.
7. 7.▲
   CrowdStrike incident shows we need to rethink cyber(computerweekly.com)

   2 points by Thompson88 2y ago|1 comments
8. 8.▲
   by Thompson88 2y ago

   Clearly there weren't any code review workflow processes in place, which is astonishing. That's why our primary focus is-transparency, accountability, and system integrity to bring a decentralized, transparent, and reliable platfo
9. 9.▲
   by Thompson88 2y ago

   While they're still blaming Microsoft as if it isn't possible to run the code they update outside of the kernel and only use the kernel mode code for observation and action, but not logic.