Sumo Logic (2023): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Sumo Logic disclosed the incident on 7 Nov 2023. What was exposed, as the sources state it: The company stated that, after investigation by its teams and third-party forensic experts, it found no proof of customer data impact. It advised customers to rotate API access keys and stored third-party credentials.
Open the ledger · Report a correction
- Disclosed
- 7 Nov 2023
- Incident window
- Discovered November 3, 2023
- Cloud or provider
- AWS
- What was exposed
- The company stated that, after investigation by its teams and third-party forensic experts, it found no proof of customer data impact. It advised customers to rotate API access keys and stored third-party credentials.
- How access was gained
- The customer notice says the activity used a compromised credential to access a Sumo Logic AWS account. How the credential was compromised is not public.
- Access path
- Leaked access keys and secrets
- Kind of control that addresses it
- replace long-lived credentials for cloud accounts with short-lived role credentials and alert on their use from new locations
In the words of the source
“The activity identified used a compromised credential to access a Sumo Logic AWS account.” (company statement, Security response center (Sumo Logic), archived copy with the November 2023 incident notices)
Primary sources
- company statement: Security response center (Sumo Logic), archived copy with the November 2023 incident notices, dated 7 Nov 2023
If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.
Related pages
Sources
- Security response center (Sumo Logic), archived copy with the November 2023 incident notices, read 16 Nov 2026
Last reviewed 16 Nov 2026.