> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zdlake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Attack patterns

> Understand CAPEC attacker techniques and their connections to weaknesses and vulnerabilities.

Attack patterns represent normalized Common Attack Pattern Enumeration and Classification (CAPEC) records. They describe ways an attacker may exploit a class of weakness, including prerequisites, execution steps, required skills, and mitigations.

Use attack patterns to understand adversary behavior behind a finding. A vulnerability explains what is exposed; an attack pattern helps explain how the underlying weakness may be exercised.

## When to use attack patterns

* Connect a weakness to concrete attacker techniques.
* Explain why a vulnerability class matters to security reviewers and engineers.
* Group findings by exploitation pattern instead of scanner, affected product, or CVE.
* Build prevention, detection, and security education workflows around recurring behavior.

Attack patterns provide conceptual context. A relationship does not prove that every connected vulnerability is exploitable in exactly the same way.

## Relationships

| Related concept | What the relationship explains |
| - | - |
| [Weakness](https://docs.zdlake.com/concepts/weaknesses.md) | The flaw class an attacker technique may exercise. |
| [Vulnerability](https://docs.zdlake.com/concepts/vulnerabilities.md) | Concrete security issues connected through supported evidence. |
| [Advisory](https://docs.zdlake.com/concepts/advisories.md) | Publisher context that links an issue to attacker behavior. |
| [Software](https://docs.zdlake.com/concepts/software.md) | Affected-product context inherited through supported security relationships. |

Use relationship source counts and provenance to understand how strongly a connection is supported. See [Security data model](https://docs.zdlake.com/concepts/security-data-model.md) for relationship cardinalities.

## Schema

Every attack-pattern detail response starts with these fields:

| Field | Meaning |
| - | - |
| `entity` | Always `attack-pattern`. |
| `entity_id` | Durable Zero identifier for the entity. |
| `id` | Preferred CAPEC identifier, such as `CAPEC-66`. |
| `aliases` | Alternate identifiers associated with the taxonomy record. |
| `title` | Attack-pattern name. |
| `summary` | Normalized attack-pattern description. |
| `state` | Current CAPEC lifecycle state. |
| `published_at` | Taxonomy publication time when available. |
| `source_updated_at` | Most recent relevant taxonomy update time. |
| `updated_at` | Time Zero last updated the entity. |
| `revision_id` | Identifier for the normalized revision returned by the request. |

Request optional projections when you need more detail:

| Projection | Contents |
| - | - |
| `overview` | Typical severity, likelihood, skill levels, prerequisites, execution flow, consequences, mitigations. |
| `execution_defenses` | Execution flow, skills, resources, indicators, examples, and mitigations. |
| `affected_targets` | Software targets connected through supporting source claims, when available. |
| `relationships` | Related entities grouped by type, including direction and supporting sources. |
| `provenance` | Field-level evidence keyed by JSON Pointer path. |

Search responses are intentionally more compact than detail responses. Use the API pages for the complete request and response schemas.

## API pages

| Page | Use it for |
| - | - |
| [Search attack patterns](https://docs.zdlake.com/attack-patterns/search.md) | Search and filter attack-pattern records. |
| [Get an attack pattern](https://docs.zdlake.com/attack-patterns/get.md) | Retrieve one attack pattern and request optional projections. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.