> For the complete documentation index, see [llms.txt](https://breachtrace.gitbook.io/vulnkeeper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://breachtrace.gitbook.io/vulnkeeper/chapter-c/07-7-cwe-capec-attandck-atlas-and-weakness-to-attack-mapping.md). # 7. CWE, CAPEC, ATT\&CK, ATLAS & weakness-to-attack mapping ## 7.1 CWE - Common Weakness Enumeration

Sl. #	Source Title	Notes
1	CWE home `Link(s)`: cwe.mitre.org `Access / Cost`: Free public	`Relevance`: Common Weakness Enumeration root. Provides standardized weakness taxonomy. `Notes & POIs`: CVE-to-CWE mappings are sometimes missing, broad, or imprecise.
2	CWE downloads `Link(s)`: cwe.mitre.org/data/downloads.html `Access / Cost`: Free public downloads	`Relevance`: XML, CSV, archive bundles, & views for machine ingestion. `Notes & POIs`: Use downloadable structured data for robust taxonomy ingestion.
3	CWE latest PDF `Link(s)`: cwe.mitre.org/data/published/cwe_latest.pdf `Access / Cost`: Free public PDF	`Relevance`: PDF publication of latest CWE content. `Notes & POIs`: Better for manual reference than automated ingestion.
4	CWE reports `Link(s)`: cwe.mitre.org/data/reports.html `Access / Cost`: Free public	`Relevance`: Reports & curated views of CWE data. `Notes & POIs`: Useful for understanding categories, views, & prioritization.
5	CWE chains & composites `Link(s)`: cwe.mitre.org/data/reports/chains_and_composites.html `Access / Cost`: Free public	`Relevance`: Describes weakness chains & composite weaknesses. `Notes & POIs`: Important for modeling multi-step root causes & compound vulnerabilities.
6	CWE schema docs `Link(s)`: cwe.mitre.org/documents/schema/index.html `Access / Cost`: Free public	`Relevance`: Schema documentation for CWE data. `Notes & POIs`: Use for parser validation & taxonomy consistency.
7	CWE data definitions	cwe.mitre.org/data/definitions/1000.html
8	CWE Top 25	cwe.mitre.org/top25
9	CWE AI/ML category - CWE-1448	cwe.mitre.org/data/definitions/1448.html
10	CWE AI Working Group	cwe.mitre.org/community/working_groups.html

## 7.2 CAPEC - attack patterns

Sl. #	Source Title	Notes
1	CAPEC home `Link(s)`: capec.mitre.org `Access / Cost`: Free public	`Relevance`: Catalog of attack patterns used to exploit weaknesses. `Notes & POIs`: CAPEC bridges weakness taxonomy & attacker behavior patterns.
2	CAPEC downloads `Link(s)`: capec.mitre.org/data/downloads.html `Access / Cost`: Free public downloads	`Relevance`: XML/CSV attack-pattern bundles. `Notes & POIs`: Prefer structured downloads for ingestion.
3	CAPEC schema docs `Link(s)`: capec.mitre.org/documents/schema/index.html `Access / Cost`: Free public	`Relevance`: Schema docs for CAPEC data. `Notes & POIs`: Important for parser validation.
4	CAPEC data index `Link(s)`: capec.mitre.org/data/index.html `Access / Cost`: Free public	`Relevance`: Browsable CAPEC entries & views. `Notes & POIs`: Useful for manual mapping & explanation.
5	MITRE CTI repository - ATT&CK & CAPEC in STIX `Link(s)`: github.com/mitre/cti `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: MITRE ATT&CK & CAPEC datasets expressed in STIX 2.0. `Notes & POIs`: Useful for graph-based relationships. May differ from newer ATT&CK-specific STIX repo content.

## 7.3 MITRE ATT\&CK

Sl. #	Source Title	Notes
1	ATT&CK Enterprise Matrix `Link(s)`: attack.mitre.org/matrices/enterprise `Access / Cost`: Free public	`Relevance`: Enterprise adversary tactics & techniques. `Notes & POIs`: More relevant for adversary behavior after exploitation than raw CVE severity.
2	ATT&CK Matrices `Link(s)`: attack.mitre.org/matrices `Access / Cost`: Free public	`Relevance`: ATT&CK matrices across domains. `Notes & POIs`: Useful for selecting enterprise, mobile, ICS, or other domain views.
3	ATT&CK Data & Tools `Link(s)`: attack.mitre.org/resources/attack-data-and-tools `Access / Cost`: Free public	`Relevance`: ATT&CK Navigator, STIX/TAXII, Workbench, & tooling references. `Notes & POIs`: Prefer machine-readable STIX/TAXII for ingestion.
4	ATT&CK STIX data repo `Link(s)`: github.com/mitre-attack/attack-stix-data `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Machine-readable ATT&CK STIX data. `Notes & POIs`: Best source for automated technique/tactic ingestion.
5	MITRE CTI repository `Link(s)`: github.com/mitre/cti `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: MITRE CTI STIX datasets. `Notes & POIs`: Keep for historical/related STIX content.
6	ATT&CK Navigator `Link(s)`: mitre-attack.github.io/attack-navigator `Access / Cost`: Free / open-source web tool	`Relevance`: Visual mapping of techniques to campaigns, risks, or controls. `Notes & POIs`: Useful for reporting & matrix visualization, not raw vuln ingestion.
7	ATT&CK Workbench `Link(s)`: github.com/center-for-threat-informed-defense/attack-workbench-frontend `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Tooling for ATT&CK customization & management. `Notes & POIs`: Useful for internal technique mapping workflows.
8	ATT&CK TAXII server docs `Link(s)`: attack.mitre.org/resources/attack-data-and-tools `Access / Cost`: Free public	`Relevance`: TAXII/STIX access docs. `Notes & POIs`: Same source as ATT&CK Data & Tools; retained to preserve the explicit TAXII reference.
9	ATT&CK Sync `Link(s)`: github.com/center-for-threat-informed-defense/attack-sync `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Tooling for consuming MITRE ATT&CK version updates into internal systems & processes. `Notes & POIs`: Useful for keeping local ATT&CK technique mappings current.
10	MITRE ATT&CK Python `Link(s)`: github.com/mitre-attack/mitreattack-python `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Python module for working with ATT&CK datasets. `Notes & POIs`: Useful for programmatic ATT&CK ingestion, transformation, & analysis.
11	ATT&CK Navigator GitHub repo `Link(s)`: github.com/mitre-attack/attack-navigator `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Source repository for the ATT&CK Navigator web app. `Notes & POIs`: Complements the hosted Navigator URL; useful for local customization & offline visualization workflows.

## 7.4 AI/ML-specific adversary frameworks

Sl. #	Source Title	Notes
1	MITRE ATLAS `Link(s)`: atlas.mitre.org `Access / Cost`: Free public	`Relevance`: Living knowledge base of adversary tactics & techniques against AI-enabled systems. `Notes & POIs`: More directly relevant to AI systems than ATT&CK Enterprise alone.
2	MITRE ATLAS matrix `Link(s)`: atlas.mitre.org/matrices/ATLAS `Access / Cost`: Free public	`Relevance`: Matrix view of AI adversary tactics & techniques. `Notes & POIs`: Useful for AI threat modeling & impact mapping.
3	MITRE ATLAS techniques `Link(s)`: atlas.mitre.org/techniques `Access / Cost`: Free public	`Relevance`: Technique-level ATLAS entries. `Notes & POIs`: Use for structured AI attack technique mapping.
4	MITRE ATLAS case studies `Link(s)`: atlas.mitre.org/studies `Access / Cost`: Free public	`Relevance`: Case studies of AI attacks & failures. `Notes & POIs`: Helpful for real-world analogs & model training examples.
5	MITRE ATLAS data repository / case-study data `Link(s)`: github.com/mitre-atlas/atlas-data, case studies `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Structured ATLAS data, including case-study material. `Notes & POIs`: Prefer this for machine-readable ATLAS case-study ingestion.
6	MITRE ATLAS GitHub / Adversarial ML Threat Matrix `Link(s)`: github.com/mitre/advmlthreatmatrix `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Historical & structured project data for adversarial ML threat matrix. `Notes & POIs`: May not be the most current ATLAS view; keep for lineage.
7	MITRE SAFE-AI report `Link(s)`: atlas.mitre.org/pdf-files/SAFEAI_Full_Report.pdf `Access / Cost`: Free public PDF	`Relevance`: AI system risk mapping across model, data, platform, & environment layers. `Notes & POIs`: Useful for AI-specific control mapping & architecture risk analysis.
8	OWASP Top 10 for LLM Applications `Link(s)`: owasp.org/www-project-top-10-for-large-language-model-applications `Access / Cost`: Free / open-source community project	`Relevance`: Practical LLM application vulnerability taxonomy. `Notes & POIs`: Useful for AI appsec detection categories beyond CVE.
9	OWASP Top 10 for Machine Learning Security `Link(s)`: owasp.org/www-project-machine-learning-security-top-10 `Access / Cost`: Free / open-source community project	`Relevance`: ML-specific application/security risk taxonomy. `Notes & POIs`: Complements ATLAS with appsec-oriented framing.
10	OWASP AI Exchange `Link(s)`: owaspai.org `Access / Cost`: Free public community resource	`Relevance`: AI security risks, controls, & threat modeling references. `Notes & POIs`: Useful for governance & risk mapping.
11	NIST AI Risk Management Framework `Link(s)`: www.nist.gov/itl/ai-risk-management-framework `Access / Cost`: Free public	`Relevance`: AI risk management framework. `Notes & POIs`: Useful for risk controls, governance, & impact framing.
12	NIST AI RMF 1.0 PDF `Link(s)`: nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf `Access / Cost`: Free public PDF	`Relevance`: AI RMF 1.0 document. `Notes & POIs`: PDF reference; not a vulnerability feed.
13	NIST AI 600-1 - Generative AI Profile `Link(s)`: www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence `Access / Cost`: Free public	`Relevance`: GenAI risk profile companion to AI RMF. `Notes & POIs`: Useful for LLM/generative AI-specific risk categories.
14	NIST adversarial machine learning taxonomy `Link(s)`: www.nist.gov/publications/adversarial-machine-learning-taxonomy-and-terminology-attacks-and-mitigations `Access / Cost`: Free public	`Relevance`: Taxonomy & terminology for adversarial ML attacks & mitigations. `Notes & POIs`: Good for consistent AI vulnerability vocabulary.
15	MLCommons AI Safety `Link(s)`: mlcommons.org/working-groups/ai-safety `Access / Cost`: Free public community resource	`Relevance`: AI safety benchmarks & working group context. `Notes & POIs`: Useful for AI system risk evaluation, not direct CVE matching.
16	MITRE ATLAS AI Risk Database `Link(s)`: github.com/mitre-atlas/ai-risk-database `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: AI supply-chain risk database associated with MITRE ATLAS ecosystem work. `Notes & POIs`: Useful for AI-specific supply-chain risk analysis & case-study style enrichment.
17	Cisco AI Defense Skill Scanner `Link(s)`: github.com/cisco-ai-defense/skill-scanner `Access / Cost`: Free / open-source public GitHub repo	`Relevance`: Security scanner for agent skills. `Notes & POIs`: Useful for AI-agent/tooling security review, prompt/tool-surface assessment, & skill-level exposure analysis.

## Discussion This chapter section keeps the latest table structure, source titles, access/cost fields, relevance notes, & operational notes from the source inventory. Review the table entries as ingestion candidates, then validate source freshness, licensing, authentication requirements, & link-check behavior before production use. *** #### [Back to Index](/vulnkeeper/index.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://breachtrace.gitbook.io/vulnkeeper/chapter-c/07-7-cwe-capec-attandck-atlas-and-weakness-to-attack-mapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.