Halcyon's key capture works when ransomware runs on a protected endpoint. When the encryption happens somewhere else (a server without an agent, stolen cloud credentials, an unmanaged host) there is no key to capture and no rollback to run.
Codefinger (January 2025)
Attackers used compromised AWS credentials to encrypt S3 bucket data using AWS's own SSE-C encryption with an attacker-held key. No ransomware binary executed. No endpoint was involved. Data was encrypted and marked for deletion in seven days. There was no key for any endpoint agent to capture.
Source: Reported by Halcyon RISE Team, January 13 2025. Confirmed by AWS Security Blog, January 2025.
How Elastio covers this
Elastio inspects the data directly, not the process that encrypted it. Whether encryption happened on the endpoint, in the cloud, via stolen credentials, or by an insider, Elastio detects the corruption inside the files. The source of the attack is irrelevant.
- Encrypted S3 objects detected regardless of how encryption was initiated
- Backup data corruption identified before it reaches a recovery point
- Last Known Clean confirmed across all data surfaces