The Kaseya ransomware “double-embedded” outbreak: what does it mean for (re)insurers?