Attack Vector
Pronunciation: uh-TAK VEHK-tur
Definition
An attack vector is the method or route an attacker uses to reach a target and attempt exploitation or unauthorized influence. Defenses against Attack Vector combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Overview
Meaning and scope
An attack vector is the method or route an attacker uses to reach a target and attempt exploitation or unauthorized influence. Defenses against Attack Vector combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Mechanism and operation
An attack vector is the channel through which an adversary approaches a system, user, or process. Examples include phishing messages, exposed APIs, vulnerable software, malicious dependencies, stolen credentials, insecure wireless access, compromised vendors, or deceptive blockchain transactions. The vector describes the route or method, while the vulnerability is the weakness that permits harmful effect. One vector may exploit several weaknesses, and one weakness may be reachable through multiple vectors. Defenders identify likely vectors through threat intelligence, architecture review, asset inventories, and incident history. Controls should reduce exposure, prevent exploitation, detect attempts, and limit impact because completely eliminating every route is rarely practical.
Practical payment example
An exposed admin endpoint gives an attacker a possible route into payout controls even when the customer-facing checkout is secure.
Operational checks
Dependencies can weaken Attack Vector even when the primary component behaves correctly. Attack vectors describe how threats reach a target, helping teams place layered controls along the most plausible and damaging routes. Assessment of Attack Vector should trace the use of to reach a target and attempt exploitation or unauthorized influence from prerequisite and entry point through observable impact on the affected service.
Distinctions and limits
A theoretical weakness or scanner result involving unauthorized influence should not be reported as exploitation without corroborating logs, transactions, or configuration evidence. Prevention, detection, containment, and recovery for the Attack Vector context should be tested against the architecture associated with unauthorized influence.
Related reading
Related definitions: blockchain, vulnerability.
Example
An exposed admin endpoint gives an attacker a possible route into payout controls even when the customer-facing checkout is secure.
Comparison
A theoretical weakness or scanner result involving unauthorized influence should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Key Takeaway
Attack vectors describe how threats reach a target, helping teams place layered controls along the most plausible and damaging routes.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)