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.
Relationships
Use relationship source counts and provenance to understand how strongly a connection is supported. See Security data model for relationship cardinalities.
Schema
Every attack-pattern detail response starts with these fields:
Request optional projections when you need more detail:
Search responses are intentionally more compact than detail responses. Use the API pages for the complete request and response schemas.