Attacks · Overview
Browse attack families by what they try to convert: channel observations, stolen credentials, or replayed and relayed authority. Each family points to a mechanism denial — not an NDA stage dump.
~5 min readContinue: Prove it
Orient here when you know the incident class but not the ENI6MA page name. The map is three public columns — Channel & cryptanalysis, Credentials & humans, Replay, relay & forgery — plus a patterns lens for buyer context. It is deliberately not a stage matrix and not a residual-risk essay.
Ambient security catalogs often bury buyers in CVE lists and control checklists. This map answers a narrower question: which conversion tray are you worried about, and which mechanism family denies it? Frequency and correlation live with empty-channel theory; vault and phish live with one-shot credentials; replay and relay live with gate ordering and binding.
Use the plate to scan families, then deep-link into a family page for the dual surface/denial teaching. Patterns pages reuse those families with business framing. Limits residual content stays deferred from public nav — honesty walls live under Technology Claims when you need scoped language.
Attack family map
How to read: scan Channel, Credentials, Replay/relay columns then mechanism badges. Takeaway: family-level mechanism denial, not a stage dump.
Three columns, mechanism badges — family-level denial without a Limits residual strip.
Attacks catalog wedge
How to read: follow see/steal → conversion → authority? → denied. Takeaway: catalog framing, not an NDA stage dump.
The catalog wedge restates the conversion question: see or steal, convert, authority?, denied.
Frequency, correlation, archive unicity, quantum.
Vault, keylog, phish, ambient.
Replay, relay, stale, forgery, tamper, revocation.
Which families matter for APIs, agents, PKI, and more.