CrowdStrike Update Causes BSOD Issues Globally

[Esben_D]

Banks, airlines, supermarkets, broadcasters, and more are all reporting Blue Screen of Death (BSOD) issues today after an update from cybersecurity provider CrowdStrike has caused computers to get stuck in a BSOD loop.

While this technically isn't a vulnerability, we've decided to cover it anyway to help out with identifying affected devices. You can find more info in the CrowdStrike blog post.

[SKFL]

The blog post and report is awesome but any way to add the channel file and timestamp?  

Also in looking at the bitlocker key report - each device has many entries all with the same timestamp.  How do we know which one to use?

[Esben_D]

could you clarify what you mean by "channel file and timestamp" ?

I'm not sure why you have multiple keys for a device, but in the Active Directory BitLocker Recovery Keys Audit the [Last Scanned] column should help. But if those are all identical, maybe you have multiple recovery keys back up into your AD?

[Esben_D]

I updated the on-prem report to include BitLocker recovery key for each asset. But if you have multiple keys on an asset, this will obviously cause "duplicate" rows.