Cloud WAF & CDN

Versus manages cloud WAF and CDN edges the same way it manages on-prem ADCs — as devices in your inventory — so your F5, NetScaler, and cloud edges all live in one place. A dedicated Cloud Traffic view surfaces the cloud side of your estate: the properties, policies, and certificates that live at the provider rather than on a box in your data center.

Supported providers

Versus supports six cloud WAF / CDN providers:

Each provider is added as a device with its API credential stored in the Versus Vault. Once connected, its properties and policies appear in inventory next to your physical devices.

What you can do

• Discover & inventory — pull the provider's sites/properties, WAF policies, and certificates into Versus so they're searchable and reportable alongside everything else.
• Push certificates — deploy a managed certificate to a cloud edge as part of certificate lifecycle, so renewals reach cloud properties the same way they reach an F5 virtual server. See Certificates.
• Sync WAF policies — import a provider's WAF policy so its rules and managed rulesets are visible and versioned in Versus.
• Reconcile WAF exceptions — add or remove a WAF exception (a rule allow-list entry) through a provider-agnostic adapter, so the same action works across providers that support it.

WAF exception adapters

WAF exceptions are applied through a small adapter per provider, so a single Versus action maps to each provider's own API. Support depends on the provider's capabilities:

• F5 Distributed Cloud and Cloudflare apply exceptions directly through their APIs.
• Other providers are recorded in Versus (so the intent and audit trail are captured) and applied according to that provider's supported workflow.

This keeps the operator experience consistent — you request the exception once in Versus — while honoring what each provider's API actually allows.

How it fits together

1. Add the provider as a device with its API token in the vault.
2. Import its properties, WAF policies, and certificates into inventory.
3. Operate from the Cloud Traffic view: push certificates on renewal, review imported policies, and manage WAF exceptions.
4. Report across cloud and on-prem together — the cloud edges are ordinary inventory, so they show up in the same dashboards and searches.

Related

• Certificates — deploy and renew certificates, including to cloud edges.
• F5 BIG-IP Integration — the on-prem ADC counterpart.
• Secret Vault — where cloud provider API credentials are stored.