With all the Crowdstrike news making center stage today, it's important for infosec and IT teams to understand, this could have been limited.. Also, bad updates happen from software vendors more than you think and should be expected.
Basic hygiene practices and processes could have prevented all of your systems from going belly up at once... here is my opinion.
1. Not all systems should be updated at the same exact time.
2. Crowdstrike has a very robust deployment model for auto-updating, referred to as N (current version), with options for N-1, N-2, etc.. this allows for not being on the latest update, that way you can bake updates and test systems and prevent bad updates from being deployed.
3. Align your organization to leverage pilot, alpha, beta, and different deployment groups for your organization. this allows updates to be controlled and leveraged for implementing changes, especially if it's a critical system.
4. This all comes down to basic operational maintenance and hygiene.. if your systems are expected to update all at once, re-think your strategy and break that up into smaller deployment groups.
5. If you have a patching cadence, leverage that process and update your security tools with similar processes. if you don't, spend time defining one.
Amazing stuff, Drata team! Super stoked to see all these enhancements, especially the ISO 27001 Control Mapping!