Proven on a real cluster
04Platform / MTD Engine

Moving is an economic decision.

Phorvex prices every move and selects the provably optimal set under a hard availability and SLO budget. It never destroys state. When a workload is stateful, the feasibility model quarantines it instead of deleting it.

/01

Every move has a price

Each candidate move is valued by the attacker reconnaissance it erases, weighed against the disruption it costs and the kill-chain stage it preempts.

/02

Provably optimal selection

The selected move set is provably optimal under a hard availability and SLO budget. Not a heuristic, not a rule table, not hand-tuned.

/03

Harm-free by construction

Destructive rotations on stateful workloads are refused before selection. Phorvex quarantines instead, disrupting the attacker while the job survives.

02Proven

The numbers that matter.

~5.5s
Eviction dwell
Against ~15s for a blind timer. Reactive tools never acted.
20/20
Work preserved
The only approach that did no harm.
Not
learnable
By an adaptive attacker
Decoy-resistant by design.
0
False positives
Across the benchmark.

Real Kubernetes cluster, n=20, reproducible, controls clean.

03Why optimal beats clever

An attacker can learn a schedule. They cannot outwait an economist.

Clock-based rotation leaks its own pattern, and an adaptive attacker simply waits it out. Phorvex selections derive from the live state of the fleet and the attacker's kill-chain position. There is no schedule to learn, and no decoy cheap enough to drain the budget.

  • Proactive. Moves before any alert fires.
  • Decoy-resistant. Bait cannot bleed the move budget.
  • Budget-bounded. Availability and SLO limits are hard constraints, never suggestions.

Run the benchmark conversation.

Methodology, controls, and reproduction, engineer to engineer.