# Imperva (2019): what the sources say about the cloud incident

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Imperva disclosed the incident on 27 Aug 2019. What was exposed, as the sources state it: Elements of the Incapsula (Cloud WAF) customer database through September 15, 2017: email addresses and hashed and salted passwords, and for a subset of customers API keys and customer-provided SSL certificates. The company stated the exposure came from a database snapshot.

- **Disclosed:** 27 Aug 2019
- **Incident window:** October 2018 (unauthorized use of an administrative API key, per the company); the company received the data set on August 20, 2019
- **Cloud or provider:** AWS
- **What was exposed:** Elements of the Incapsula (Cloud WAF) customer database through September 15, 2017: email addresses and hashed and salted passwords, and for a subset of customers API keys and customer-provided SSL certificates. The company stated the exposure came from a database snapshot.
- **How access was gained:** The company's follow-up post says an unauthorized use of an administrative API key in one of its production AWS accounts led to exposure of a database snapshot. It lists the steps as a snapshot created for testing, an internal compute instance accessible from the outside world that contained an AWS API key, compromise of that instance and theft of the key, and use of the key to access the snapshot.
- **Access path:** [Leaked access keys and secrets](/access-paths/leaked-access-key/); also [Exposed network services and request paths](/access-paths/exposed-network-service/)
- **Kind of control that addresses it:** keep long-lived cloud administrative keys out of compute instances, place internal instances on a private network by default, and expire or rotate keys on a schedule

## In the words of the source

“Our investigation identified an unauthorized use of an administrative API key in one of our production AWS accounts in October 2018, which led to an exposure of a database snapshot containing emails and hashed & salted passwords.” (company statement, [Imperva Security Update (follow-up on the root cause), archived copy of the company blog](https://web.archive.org/web/20191101/https://www.imperva.com/blog/ceoblog/))

## Primary sources

- company statement: [Imperva Security Update (follow-up on the root cause), archived copy of the company blog](https://web.archive.org/web/20191101/https://www.imperva.com/blog/ceoblog/), dated 10 Oct 2019
- company statement: [Imperva Security Update (initial announcement), archived copy of the company blog](https://web.archive.org/web/20190901/https://www.imperva.com/blog/ceoblog/), dated 27 Aug 2019

If a field is wrong or a newer primary source exists, [write to the editor](mailto:editor@cloudsecuritybreaches.com?subject=Correction%3A%20Imperva%20(imperva-2019)) with the entry name in the subject.

## Related pages

- [Capital One 2019: exposed network services and request pat](/incidents/capital-one-2019/)
- [Online Buddies (Jack’d dating app) 2019: jackd s3](/incidents/online-buddies-jackd-s3-2018/)
- [Veradigm Inc. 2026: vendor api](/incidents/veradigm-vendor-api-2026/)

## Sources

- Imperva Security Update (follow-up on the root cause), archived copy of the company blog: https://web.archive.org/web/20191101/https://www.imperva.com/blog/ceoblog/ (read 16 Nov 2026)
- Imperva Security Update (initial announcement), archived copy of the company blog: https://web.archive.org/web/20190901/https://www.imperva.com/blog/ceoblog/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/imperva-2019/
