vRx

Prevent runtime exploitation of known software vulnerabilities

Known vulnerabilities in applications and third‑party components can be exploited before a validated fix is available. Patching is often delayed by change control, testing needs or unavailable updates, leaving an operational exposure.

vRx applies runtime virtual patches and mitigation rules to block exploit attempts without modifying application source code, reducing exposure and giving teams time to test and deploy permanent fixes.

Where vRx is used

Typical use cases include protecting legacy or third‑party applications that cannot be patched immediately, enforcing compensating controls when fixes are unavailable, and reducing immediate exploit risk by blocking runtime attack techniques.

Fits within these solutions

Patch & Vulnerability Management

Delivery & deployment

On-Premises Software

Suitable environments

Fits organisations with strict change control or limited maintenance windows, large enterprises with heterogeneous on‑premises and cloud infrastructure, regulated sectors, businesses running legacy or third‑party applications that are hard to patch, and MSSPs protecting multiple client environments.

Benefits

Reduced exposure

Lowers the risk of successful exploitation by blocking attack techniques at runtime.

Time to patch

Buys time for teams to develop, test and deploy permanent fixes without immediate emergency changes.

Avoid code changes

Enables mitigations without modifying application source code or binaries.

Protect legacy systems

Offers protection for legacy or hard‑to‑patch applications that would otherwise remain exposed.

Reduce emergency patching

Reduces pressure to apply immediate disruptive patches by providing runtime controls.

Maintain availability

Helps keep services running by avoiding disruptive code changes while mitigations are in place.

Capabilities

Runtime virtual patches

Applies virtual patches at runtime to prevent exploitation of known vulnerabilities in applications and third‑party components.

Mitigation rule enforcement

Enforces runtime mitigation rules to limit access to vulnerable APIs and code paths without source changes.

Exploit blocking

Detects and blocks exploit attempts against known vulnerabilities before they reach application logic.

Third‑party protection

Protects vulnerable third‑party libraries and components at runtime without requiring code modifications.

Non‑invasive deployment

Deploys mitigations without modifying application source code or binaries.

Temporary compensating control

Provides temporary protection until validated patches or code fixes can be applied.

Exposure reduction

Reduces the exposure window to known vulnerabilities by stopping exploit activity at runtime.

Applications

Strict change control

Used where governance prevents quick code or configuration changes, providing a non‑invasive mitigation alternative.

Limited maintenance windows

Suitable when maintenance windows are tight and immediate patching would disrupt operations.

Heterogeneous estates

Deployed in large environments that mix on‑premises and cloud systems where patching consistency is hard.

Regulated industries

Adopted in sectors with strict operational controls where rapid code changes are constrained.

Legacy & third‑party apps

Protects applications and third‑party components that are difficult to patch or update promptly.

MSSP client protection

Useful for service providers protecting multiple client environments where rapid patching varies across estates.