What happened
Incident overview / Beacon CRM and its charity customers
- 1
A stolen key grants access
July 27, 2026Beacon says a static AWS key allowed an unauthorized user into its cloud environment. It considers accidental exposure in application code the probable cause.
- 2
The customer database is copied
July 27–28, 2026Beacon confirmed a copy of the full customer database. Higher outbound traffic suggested a download, but file-level records were unavailable.
Impact
Someone copied the database holding all Beacon customer data. A rise in outbound transfers suggested a substantial download, but available records could not establish what left.
Could this have been prevented?
Require temporary AWS credentials for deployments
Beacon replaced static deployment keys with federation and disabled the compromised key. If deployments in a covered AWS member account use only temporary credentials, a service control policy can also refuse direct requests signed with long-lived keys.
Incident control assessments
- 0
- Prevented
- 1
- Contained
- 1
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Incident overview / Beacon CRM and its charity customers
1 · A stolen key grants access
1 Contained2 · The customer database is copied
1 Not coveredKey facts
- Beacon dates the first unauthorized access to July 27, 2026.
- Beacon identified accidental exposure of the key in application code as the probable cause.
- An independent reviewer verified that the credential was disabled on July 29.
- Beacon moved its deployment process to identity federation and stopped using static AWS deployment keys.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.Beacon Cyber Security Incident Final Report, including CYFOR Secure’s independent attestationBeacon CRM and CYFOR Secure · Sep 3, 2026 · Vendor reportPages 5–6 and 12 cover the database copy, probable source and deployment keys. Appendix 2 verifies the credential was disabled and explains why removal of data cannot be proven.
- 2.Cyber-security Incident UpdateBeacon CRM · Sep 3, 2026 · Status pageCustomer communications and chronology, including the August 3 notice and later investigation findings.
- 3.Guidance for charities affected by the Beacon cyber security incidentCharity Commission for England and Wales · undated · AdvisoryConfirms the response for affected charities and sets out their reporting responsibilities.
- 4.Security best practices in IAMAWS · undated · AdvisoryAWS recommends temporary credentials and workload roles for access to AWS.
- 5.AWS global condition context keysAWS · undated · AdvisoryThe issue-time key is present for temporary credentials and absent when using long-lived access keys.
- 6.Service control policies (SCPs)AWS · undated · AdvisoryDescribes policy scope in member accounts and excluded entities.
The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.