Anatomy of an Asymmetric Persistence Mechanism
Persistence is an asymmetry problem: the defender has to find everything, while the attacker only has to leave one thing behind.
A persistent WordPress infection, a cron job that undid my cleanup on its next run, and what the same pattern means for a model running across many devices: how to detect it, contain it, remove it everywhere at once, and measure the capability before it exists.
- 01 Detect
- 02 Contain
- 03 Eradicate
- 04 Evaluate the step a website never needed