When to Use Compensating Controls
You'll learn when compensating controls become your best (or only) option for managing risk when traditional remediation isn't possible.
Understanding the Right Scenarios
Compensating controls aren't a first choice—they're a strategic fallback when direct vulnerability remediation is blocked. Think of them as detour signs when the main road is closed: you still reach security, just via a different route.
You should deploy compensating controls in four primary situations:
1. Legacy Systems
Older systems that cannot be upgraded or replaced due to compatibility requirements with critical business processes. The mainframe running payroll that's been humming since 1985? Compensating controls are your friend.
2. Unsupported Software
Vendors who've ended support, leaving you with known vulnerabilities and no patches coming. When your SCADA system vendor went out of business but the production line depends on it, you compensate rather than accept raw risk.
3. Business-Critical Applications
Systems so essential that any downtime for patching would cause unacceptable business impact. That trading platform that processes millions per minute? You can't just take it offline for a three-hour patch window during market hours.
4. Patch Delays
Situations where patches exist but can't be immediately applied—perhaps they need extensive regression testing, or a maintenance window is months away. The gap between vulnerability disclosure and your ability to patch is exactly where compensating controls shine.
The Decision Framework
Ask yourself: "Can I fix this vulnerability directly right now?" If no, and the risk is unacceptable, you need compensating controls. They bridge the gap between "vulnerable" and "remediated."
Key Takeaway: Use compensating controls when direct remediation is technically impossible, operationally disruptive, or temporally delayed—but never as a permanent substitute for fixing the root cause when feasible.