Explore >> Select a destination
|
You are here 
|
krebsonsecurity.com | ||
| | | | |
www.oligo.security
|
|
| | | | | CrowdStrike outage shows the risks of kernel drivers and the need for safer, flexible eBPF-based sensors in cybersecurity. Learn how eBPF help. | |
| | | | |
www.danstroot.com
|
|
| | | | | Today I read that hospitals in Germany said they would cancel elective procedures; in Britain, some doctors in the National Health Service were unable to gain access to systems. Sky News, a major news channel in Britain, could not operate. At JPMorgan Chase there were delays in processing trades because bankers could not log into their work systems. How do we prevent this? | |
| | | | |
jmmv.dev
|
|
| | | | | Look, I like Rust. I really, really do, and I agree with the premise that memory-unsafe languages like C++ should not be used anymore. But claiming that Rust would have prevented the massive outage that the world went through last Friday is misleading and actively harmful to Rust's evangelism. Having CrowdStrike written in Rust would have minimized the chances of the outage happening, but not resolved the root cause that allowed the outage to happen in the first place. Thus, it irks me to see various folks blanket-claiming that Rust is the answer. It's not, and pushing this agenda hurts Rust's adoption more than it helps: C++ experts can understand the root cause and see that this claim is misleading, causing further divide in the systems programming world. ... | |
| | | | |
smist08.wordpress.com
|
|
| | | Introduction Last time, I blogged on the massive IT outage created by CrowdStrike. Since then CrowdStrike has released their postmortem of what went wrong. Also hackers have been disassembling the CrowdStrike code to analyze how it works. Keep in mind that estimates of the damage to the economy of this outage are around 5.4 billion,... | ||
