V01 · Social engineering and trusted-person impersonation
The attacker exploits a trusted role, urgency or a routine business process to obtain information or a decision. Public business context can make the approach plausible.
Define a technique once. Each scenario references its version and supplies its own target, permission, resource and measurement parameters.
The attacker exploits a trusted role, urgency or a routine business process to obtain information or a decision. Public business context can make the approach plausible.
A deceptive email or SMS leads the recipient toward a harmful action or a false trust decision. This is a delivery technique that can be combined with V01.
An adversary interposes on a communication path or abuses a trust mistake to observe or alter traffic. Not every packet observation is a successful MITM.
A false access point or captive portal imitates trusted onboarding. It can be combined with social engineering but requires its own radio/network permission.
A file, attachment or peripheral is used to exploit software or induce execution; a lost unencrypted device can also expose data without a software exploit.
An attacker reaches a service and abuses a flaw in input handling or application logic to access data or functions outside the intended boundary.
An adversary uses a stolen, weak or wrongly privileged identity/session, or a defective recovery process, to cross an access boundary.
A trusted supplier account or remote-management path gives an adversary an entry point or wider reach. Legitimate administration software can be misused.
After an initial foothold, an adversary seeks more systems or privileges, copies valuable data or disrupts operation. This guide concerns validation of containment and impact, not deployment of destructive malware.
Untrusted content attempts to become an instruction or an authority for a model-connected action. The policy must be enforced outside the model.