Attacks · By business pattern
How attack families show up across product and ops patterns. Each pattern page names which families matter and links into Channel, Credentials, and Replay — mechanism-first, no residual-risk sidebars.
~5 min readContinue: APIs & workloads
Patterns are lenses, not separate cryptosystems. Buyers arrive with an estate — API keys, agents, human login, certificates, air-gaps, content backends, regulated reviews — and need to know which attack families dominate that context.
Ambient estates teach the wrong lesson: every pattern looks like “protect the secret store.” ENI6MA patterns instead point at conversion trays — ambient bearers, replay, relay, tamper, phish — and deep-link the family pages that deny them.
Use the hub plate to pick a context, then read the linked families for dual-plate teaching. Residual Limits essays stay deferred; keep honesty language on Technology Claims when reviewers ask for walls.
Patterns hub
How to read: each pattern card names the families that dominate that estate. Takeaway: patterns are lenses, not new cryptosystems.
Each card is a buyer context — not a new protocol — naming the families that matter there.
Attack family map
How to read: scan Channel, Credentials, Replay/relay columns then mechanism badges. Takeaway: family-level mechanism denial, not a stage dump.
Return to the family map when you need mechanism detail instead of estate language.
Phish, keylog, ambient harvest.
Ambient keys, replay, tamper, revocation.
Tool-call blast radius without reusable secrets.
Keep certs; fix request authorization.
Mint and enforce without a path out.
News/poll teaching surface behind a gate.
Mechanism-first review language.