Imperva WAF Cloud

Connection Requirements

1 - Domain

The Imperva Cloud API host (default: api.imperva.com).

2 - API ID

The API ID component of an Imperva API key pair, generated in the Cloud Security Console under Account Management → API Keys. Sent in the x-API-Id request header.

3 - API Key

The API Key component paired with the API ID above. Sent in the x-API-Key request header.

4 - Sub-account ID

Optional Imperva account ID (caid) to scope calls to a sub-account. Leave blank to use the account the API key was issued under (default: blank).

5 - Proxy

Optional proxy server in host:port format used to reach api.imperva.com.

6 - Timeout

The amount of time (in seconds) to wait for API responses (default: 30).

7 - Fetch users

When enabled, the adapter fetches IDM users from /v3/idm-users (default: enabled). Disable when the API key does not have permission on the Users endpoint.

8 - Fetch certificates

When enabled, the adapter fetches SSL/TLS certificate metadata from /v3/certificates (default: disabled). Enable when the API key has permission on the Certificates endpoint. At least one of Fetch users or Fetch certificates must remain enabled.

Permissions Required

The API key pair must be issued to an Imperva user with read access to Account Settings → Users (for IDM users) and Websites → SSL Certificates (for certificates). Permissions are inherited from the user/role that created the key pair.

Attention

Please perform a connection test to ensure there is a valid connection to the Imperva Cloud API. When the discovery operation is finalized you will be able to see the details on the Assets page.