Data Storage Management
- Last UpdatedApr 20, 2025
- 4 minute read
The Imperva service provides regional data isolation and control for storing events and network layer data. Data can be isolated per region, per site, in accordance with data privacy requirements.
Regional data storage
The data stored for your account includes:
-
Events, as displayed on the Security Events page in the Cloud Security Console, and the associated threat alerts based on the events.
Threat alerts are generated by the Imperva Cloud Security Console and are also stored temporarily in the selected region. For more details on threat alerts, see Web Protection - WAF Settings, Website Notification Settings, and Notifications.
-
SIEM integration
Note: If log integration is enabled for a site, and you do not want data stored in the US, you must use the push method (SFTP or Amazon S3). When using the pull method (Imperva Cloud Application Security API), Imperva logs are temporarily stored in the Imperva cloud repository located in the US. For more details on log integration, see Cloud WAF Log Integration.
- Network layer 3/4 headers, which contain IP addresses.
View or change the data storage region
You can select a default data region for storing events and network layer data. The available regions are APAC, AU, EU, and US.
The account administrator or a user with the appropriate permissions can set the default data storage region for new sites created in the account, and also change the region for individual sites.
Account-level settings
The account-level data region setting sets the default storage region for new sites created in your account, and also determines where network layer data is stored.
By default, network layer data collected for your account by Imperva is stored in the US. You can select an alternative data storage region.
In the Cloud Security Console, open the Account Settings page and scroll to the Data Management section.
Setting | Description |
---|---|
Default data storage region |
Sets the default data storage region for new sites created in your account. This setting also determines where network layer data is stored. |
Override site event data region by origin geolocation |
Overrides the default setting and enables the system to automatically select the WAF event storage location for each website independently. |
For more details, see Account Settings.
Site-level setting
The site-level data region setting determines the geographical region for storing your Layer 7 (application layer) Imperva data.
By default, data that is collected for a site (events, logs) is assigned to its designated regional PoPs (data centers). Imperva assigns a region to a site based on geolocation of the origin server registered for the site. You can override the default storage region defined for your account.
On the Website General Settings page, scroll to the Data Storage section.
Setting | Description |
---|---|
Region |
Sets the region for storing Layer 7 (application layer) data for a specific site. For more details, see Website General Settings. |
Data storage regions
APAC
- Auckland, New Zealand (AKL)
- Bangkok, Thailand (BKK)
- Dubai, United Arab Emirates (DXB)
- Hong Kong (HKG)
- Johannesburg, South Africa (JNB)
- Seoul, South Korea (KOR)
- Mumbai, India (BOM)
- New Delhi, India (NDL)
- Osaka, Japan (OSK)
- Singapore (SIN)
- Taipei, Taiwan (TPE)
- Tel Aviv, Israel (MED)
- Tokyo, Japan (TKO)
EU
- Amsterdam, Netherlands (AMS)
- Copenhagen, Denmark (CPH)
- Frankfurt, Germany (FRA)
- London, United Kingdom (LON)
- Madrid, Spain (MAD)
- Milan, Italy (MXP)
- Paris, France (CDG)
- Stockholm, Sweden (STO)
- Vienna, Austria (VIE)
- Warsaw, Poland (WAR)
- Zürich, Switzerland (ZRH)
US
- Ashburn, VA, United States (IAD)
- Atlanta, GA, United States (ATL)
- Chicago, IL, United States (ORD)
- Dallas, TX, United States (DFW)
- Los Angeles, CA, United States (LAX)
- Miami, FL, United States (MIA)
- Newark, NJ, United States (NYC)
- San Jose, CA, United States (SJC)
- São Paulo, Brazil (GRU)
- Seattle, WA, United States (SEA)
- Toronto, ON, Canada (TOR)
- Vancouver, BC, Canada (VAN)
AU
- Melbourne, VIC, Australia (MEL)
- Sydney, NSW, Australia (SYD)
Data masking
You can choose to enable the hashing method for masking fields in your sites' logs and in the Security Events page, instead of the default (XXX) data masking. For details, see Website General Settings.
Delete stored data
You can permanently delete the data stored for your account. This enables you to remove all potentially sensitive or personal data that is stored in our systems, such as IP addresses.
Note: Available for account admins only.
- You can delete the data in your account at any time.
- Stored data is deleted from the account and from all sites and sub accounts under the account.
- Data that has been stored up until the time you begin the process is deleted. New data continues to be stored from this point forward.
- No account or site settings are deleted or changed in any way.
What to expect after the data is deleted:
To delete stored data:
On the Cloud Security Console sidebar, select Management and navigate to Account Settings > Data Management > Delete sites’ security and access event data and click Delete.
After you click to confirm the deletion, the process begins and an email confirmation is sent to you.
Note: Email notifications are sent to the email addresses listed under E-mail for notifications in your account settings. For details, see Account Settings.
During the deletion process, a notification banner is displayed when you log in to your Imperva account, indicating that the deletion is underway. Data is permanently deleted within 30 days.
When the process is complete, another email notification is sent.