Imperva WAF

Collect Imperva Cloud WAF site inventory and status/WAF-mode posture through the documented Imperva Cloud Security API. Customer supplies the account's API ID/key as the Authorization header value; site-specific security-rule evidence requires a documented site ID and is left customer-configured.

Connect Imperva WAF All integrations

Network security · WAF

Tier 2 generic template — runs on the HTTP / REST endpoint connector

Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

Protected site (domain) inventory
Site status and WAF security mode/posture
Customer-supplied site-scoped security-rule endpoint (optional)

Read-only calls

Endpoints this template queries

The exact Imperva WAF API endpoints called once connected. All read-only GET requests unless noted.

POST/sites/list
POST/sites/status

Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

Base URL(prefilled: https://my.imperva.com/api/prov/v1)
Endpoints (JSON)(prefilled: [ { "id": "sites-list", "name": "Protected sites", "path": "/sites/list", "method": "POST" }, { "id": "sites-status", "name": "Site status", "path": "/sites/status", "method": "POST" } ])

Optional

Auth header name(prefilled: Authorization)
Auth header value(secret credential)

Where this evidence goes

Which frameworks this evidence supports

Imperva WAF evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in Imperva WAF evidence

Get a guided demo, or start by scanning any domain for free.

Connect Imperva WAF Browse all integrations