The compromise-resilient principal: a protocol for keeping control
CB-292 argued that a principal's information will keep escaping through institutions the principal does not control. This annex asks how a principal's team keeps control when that happens: who decides, what must be verified, and how each protection is proven rather than promised. Built from federal incident response and authentication guidance and joint Five Eyes guidance on AI agents. For family offices, security leads and the principals who authorize them.
Unlock this Command Brief.
Get this assessment, the full subscription collection, and new intelligence as it is published.
For your first year, then $100/month. Or $750 for the first year, then $1,000 annually.
- The CORGI Morning Brief, each morning
- This brief and the subscription collection, 90+ briefs
- New Command Briefs as they are released
- Principal and Analyst briefs, as PDF
Secure checkout through Substack. Substack asks for your email first.
How it happens
Account takeover
An attacker gains control of an account through phished codes, PINs, help-desk resets, SIM swaps or rogue linked devices.
More on access and compromise →- Mechanism · Breach and custodyVendor-chain breach. Data escapes through a vendor, fulfillment provider or institution the person relies on but does not control.
- Defender failureWarning path failure. Warning signs reach people who cannot act, or monitoring watches the wrong signals, so a threat is missed before it acts.