> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/q-z-integrations/thales-imperva/thales-imperva-cloud-web-application-firewall-formerly-imperva-cloud-setup-for-workbench.md).

# Thales Imperva Cloud Web Application Firewall (formerly Imperva Cloud) Setup for Workbench

{% hint style="info" %}
These instructions include setup for Imperva's **cloud** version of the Web Application Firewall (WAF). If you wish to use the on-prem version, go to [Thales Imperva Web Application Firewall Setup for Workbench](/connect-your-technology/q-z-integrations/thales-imperva/thales-imperva-web-application-firewall-formerly-imperva-securesphere-setup-for-workbench.md).
{% endhint %}

## Step 1: Create an Expel SOC Account in the Imperva Cloud Security Console <a href="#h_01hye6h2wk8ysamta9hcb8raqj" id="h_01hye6h2wk8ysamta9hcb8raqj"></a>

Expel needs console access to your device to allow our SOC analysts to dig deeper during incident investigations. Additionally, our engineering teams use this access to investigate potential health issues. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).

1. Log into your Imperva Cloud Security Console as an Administrator.
2. Navigate to **Account > Account Management**.

   <div align="left"><figure><img src="/files/eJj0uxZK98jpqlxnnshp" alt="In Thales Imperva, Account Management is available under the Account menu." width="188"><figcaption></figcaption></figure></div>
3. On the left side, click **Users**.
4. Click **Add User**.
5. Complete the fields as follows:
   * **Name** - enter "Expel SOC".
   * **Email** - enter “soc+<**Your Organization Name**>@expel.io”.
     * For example, if your organization were Acme Corp, the format would be "<soc+acme_corp@expel.io>".
   * **Role** - assign the **Reader** role to the account.

     <div align="left"><figure><img src="/files/boaxKhlsnl4BdUUUUi4u" alt="Enter Expel SOC for username, the email address as directed, and select Reader for the role." width="306"><figcaption></figcaption></figure></div>
6. Select **Save**.

Expel will receive the email invitation and complete console access configuration in Workbench on your behalf.

## Step 2: Generate an API Key for the Expel SOC User <a href="#h_01hye6h2wkzfcn09y9rrh3zjs5" id="h_01hye6h2wkzfcn09y9rrh3zjs5"></a>

1. Click the new user you just created, a **Settings** menu will appear on the right.

   Click the **API keys** drop-down, then select **Add API key**.<br>

   <div align="left"><figure><img src="/files/S7R1YfDXKduLvuN6aYsL" alt="Select the Add API key button in the API keys dropdown." width="273"><figcaption></figcaption></figure></div>
2. Add a Name and Description for the API Key.
3. Select the **Never** **expire** option.
4. Move the Status slider to **Enabled**.
5. Select **Save**.

   <div align="left"><figure><img src="/files/pnsOO3Zdxp2DRXD0OWwh" alt="For Name, enter Expel SOC, for Description, enter User for integration with Expel, and choose Never expire." width="316"><figcaption></figcaption></figure></div>
6. Your **API ID** and **API Key** will show on the screen. Copy and store the **API ID** and **API Key** to a secure location. *Be sure to do this, as this is the only time these values are shown.*<br>

   <div align="left"><figure><img src="/files/HhfB7E4TDTWYNJOyoTnz" alt="API ID and API Key are generated with warning Once you close this window, you&#x27;ll no longer be able to access the key." width="375"><figcaption></figcaption></figure></div>

## Step 3: Add Imperva as a Security Device in Workbench <a href="#h_01hye6h2wk6qxdpcfkfzgxrz7j" id="h_01hye6h2wk6qxdpcfkfzgxrz7j"></a>

1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. In the search box, type “Imperva” and then select the **Thales Imperva Cloud Web Application Firewall** integration.
5. A configuration pane displays. Complete the fields as follows:
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Imperva WAF”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
   * **Location** - enter the location of your integration, for example, “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
   * **Connection Settings** - provide the appropriate information:
     * **Expel Imperva API ID** - enter the API ID you generated in [Step 2](#h_01hye6h2wkzfcn09y9rrh3zjs5).
     * **API key for Expel Imperva email** - enter the API key you generated in [Step 2](#h_01hye6h2wkzfcn09y9rrh3zjs5).
6. Select **Save**.
7. On the console access screen, select **Set up later**. Expel will complete configuration with the user you created in [Step 1](#h_01hye6h2wk8ysamta9hcb8raqj).
8. Select **Save**.

Your device should be created successfully within a few seconds. A few reminders:

* After your connection is healthy, it will take some time for your device to begin polling.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* If your device does not begin polling within 15 minutes, [contact our support team](/support/how-to-reach-us.md) for help. You must refresh the page to see updates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.expel.io/connect-your-technology/q-z-integrations/thales-imperva/thales-imperva-cloud-web-application-firewall-formerly-imperva-cloud-setup-for-workbench.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.