Skip to content
Exposure Management FinderExposure Finder

LESSON 05 · ACT ON IT

How do compensating controls buy time while a fix is planned?

SHORT ANSWER

A compensating control reduces the risk of an exposure without fixing it: a WAF rule that blocks exploitation, an edge rule pushed to a CDN, or a playbook that takes a service offline. For stretched teams it is often the fastest way to act. It must be tracked as temporary, and the real fix stays on the list.

2 min read

By The Exposure Desk · Exposure Management Finder · Published 2026-10-05

Desk research from public vendor pages read in September 2026, updated 2026-10-11. Profiles follow our published method; we did not run the products.

Why not just patch?

Patching internet-facing applications takes time: testing, change windows, vendor fixes that do not exist yet. Meanwhile a newly published vulnerability can be exploited within days. A compensating control closes that gap.

What kinds are there?

  • WAF rules (virtual patching). A rule on the WAF in front of the application blocks requests that exploit the vulnerability. IONIX describes turning a CVE into a deployable WAF rule within 12 hours of publication, across 50+ WAF vendors.
  • Edge rules. Rules pushed to a CDN or edge provider. watchTowr describes Active Defense deploying mitigation rules through Cloudflare, Akamai, Imperva, F5, Fortinet, Check Point and Citrix.
  • Response playbooks. Automated actions such as isolating a service or opening an urgent change. Palo Alto Networks describes Active Response playbooks in Cortex Xpanse.
  • Claiming an abandoned resource. IONIX describes Active Protection buying expired domains and claiming abandoned cloud buckets on the customer's behalf, which removes the takeover risk outright.

What can go wrong?

A rule can be deployed in monitoring mode and block nothing. It can sit on a WAF that does not front the affected application. It can be bypassed by a variant of the attack. And once the pressure is off, the real fix can be forgotten. Each of these is a reason to retest the control and keep the underlying fix tracked.

When should you rely on them?

When your team's capacity to fix is the bottleneck, compensating controls are worth more than a longer list. The finder adds points to WAF posture and CTEM programme support when you say you need controls applied through tools you already own.

What should you ask a vendor?

  1. Which of our WAF or edge vendors can you produce rules for, by name?
  2. Who deploys the rule: you, us, or a workflow we approve?
  3. How do you confirm the rule is enforced and blocking?
  4. How do you keep the real fix on our list?

What next?

Read WAF posture and compare the mitigation line in the vendor notes.

Sources

Source: IONIX WAF Posture Management · Read 27 Sep 2026

Source: IONIX Active Protection · Read 27 Sep 2026

Source: watchTowr platform · Read 27 Sep 2026

Source: Cortex Xpanse · Read 27 Sep 2026