Skip to content

Provision certificates to Imperva WAF

Provision a certificate from Certificate Manager - SaaS to an existing site in your Imperva Cloud Web Application Firewall (WAF) account. Certificate Manager - SaaS uploads the certificate, its issuing chain, and its private key as the site's custom certificate. You identify the site by its numeric Site ID.

Before you begin

  • An Imperva WAF machine that you created and whose status is Verified.
  • The certificate to provision in the Certificate Manager - SaaS inventory, with its private key.
  • The System Administrator or PKI Administrator role, or the Resource Owner role and membership in the machine's owning team.
  • The Site ID of the Imperva site where you want to install the certificate. You can find it in the Imperva Cloud Security Console. Certificate Manager - SaaS doesn't create sites, so the site must already exist.

To provision a certificate to Imperva WAF

  1. Sign in to Certificate Manager - SaaS.
  2. Click Installations > Machines.
  3. Click the more options button at the end of the machine's row, and then select Provision.

  4. In Search a certificate by name, expiration or fingerprint, enter part of the certificate's name, expiration date, or fingerprint, and then select the certificate from the results. Confirm that it's the right certificate by checking Subject DN, Validity, and Certificate SHA1 Fingerprint.

    The rest of the Provision a certificate dialog appears after you select a certificate.

  5. Under Certificate Information, in Site ID, enter the numeric ID of the Imperva site.

  6. (Optional) To save the installation without pushing the certificate now, disable Push certificate on save.
  7. Click Save. To save and then provision another certificate, click Save & New.

After you save, Certificate Manager - SaaS uploads the certificate to the site, which replaces the site's current custom certificate. If Imperva reports that the upload failed, Certificate Manager - SaaS tries it up to three times in total. It then waits about 45 seconds for Imperva to bind the certificate to the site before it reports success, and an installation appears on the machine's Installations tab. To provision on a schedule instead of right away, set up a machine provisioning schedule.