← Latest papers
🤖 AI

CVE-TTP KG: Knowledge Graph Linking Software Vulnerabilities to Attack Behaviors

This paper introduces CVE-TTP, a Knowledge Graph that bridges the gap between software vulnerabilities and attacker behaviors by linking CVEs to MITRE ATT&CK tactics and techniques using transformer-based models and a Neo4j visualization framework.

Original authors: Basant Agarwal, Dincy R. Arikkat, Swati Yadav, Serena Nicolazzo, Antonino Nocera, Vinod P

Published 2026-07-01
📖 5 min read🧠 Deep dive

Original authors: Basant Agarwal, Dincy R. Arikkat, Swati Yadav, Serena Nicolazzo, Antonino Nocera, Vinod P

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine the world of cybersecurity as a massive, chaotic library. On one shelf, you have the CVE (Common Vulnerabilities and Exposures) section. This is a giant catalog of every known "broken lock" or "cracked window" in software. It tells you what is broken and where it is, but it doesn't tell you who is trying to break in or how they plan to do it.

On another shelf, you have the MITRE ATT&CK section. This is a playbook of criminal behaviors. It details the "Tactics" (the criminal's goal, like "steal the keys") and the "Techniques" (the specific method, like "picking the lock" or "smashing the glass").

The Problem:
For a long time, these two shelves didn't talk to each other. Security teams had a list of broken locks but no idea which ones criminals were actually targeting or how they were planning to exploit them. It's like knowing a window is cracked but not knowing if the burglar is planning to climb in, smash it, or just use it to throw a rock.

The Solution: The CVE-TTP Knowledge Graph
The authors of this paper built a "super-librarian" system called the CVE-TTP Knowledge Graph. Think of this as a giant, intelligent map that draws direct lines between the broken locks (CVEs) and the criminal playbooks (Tactics and Techniques).

Here is how they built it, using simple analogies:

1. The Detective's Training (Data Collection)

First, the team gathered a massive library of 276,000 vulnerability reports. To teach their system how to connect the dots, they manually traced the path from a broken lock to a criminal method.

  • The Chain: They linked a Vulnerability (the broken lock) \rightarrow a Weakness (the type of flaw) \rightarrow an Attack Pattern (the criminal's plan) \rightarrow a Technique (the specific move) \rightarrow a Tactic (the ultimate goal).
  • The Result: They created a "Gold Standard" dataset of 1,080 examples where humans had already drawn these lines perfectly. This served as the teacher for their AI.

2. The Two Detective Styles (The AI Models)

The team built two different types of AI "detectives" to read the vulnerability reports and draw the lines automatically.

  • Detective A (The Pipeline Approach): This detective works in two steps. First, it reads the text and highlights the important words (like "Microsoft," "Windows," or "Denial of Service"). Then, a second detective looks at those highlighted words and decides how they are connected.

    • Analogy: It's like a team where one person highlights the suspects, and a second person draws the lines between them.
    • Performance: Very good at finding the words (99% accuracy) and connecting them (99% accuracy), but sometimes the second detective misses the nuance because they didn't see the whole picture at once.
  • Detective B (The Joint Approach): This detective reads the text and draws the lines all at the same time. It looks at the whole sentence and decides, "This word is a suspect, that word is a location, and they are connected by this specific crime."

    • Analogy: This is a single detective who sees the whole crime scene instantly and draws the map in one go.
    • Performance: It was slightly less perfect at finding every single word (78% accuracy) compared to the two-step team, but it was much better at understanding the context and avoiding mistakes where one step ruins the next.

3. The "Brain" of the System (The Models)

To make these detectives smart, the team used a special type of AI brain called CySecBERT.

  • Imagine a normal brain that reads news and understands "cat" and "dog."
  • CySecBERT is a brain that has read millions of cybersecurity blogs, reports, and tweets. It already understands that "SQL Injection" isn't just a database error, but a specific type of attack.
  • The team taught this brain to look at a vulnerability report and say, "Ah, this specific broken lock is likely to be used by a criminal trying to steal credentials (Tactic) using Network Sniffing (Technique)."

4. The Results: A Clearer Map

When they tested their system:

  • The Brain's Skill: The CySecBERT model was incredibly good at guessing the criminal's plan. It correctly identified the "Tactics" (goals) 96% of the time and the "Techniques" (methods) 87% of the time.
  • The Map: They fed all this data into a database called Neo4j (think of it as a digital spiderweb).
    • The Pipeline Map: Showed the connections but sometimes used vague lines like "associated with" instead of specific ones like "achieved through." It was a bit messy.
    • The Joint Map: Created a cleaner, more focused web. It correctly linked the vulnerability to the weakness and the impact, though it sometimes missed the specific "vendor" names.

The Bottom Line

The paper claims that by building this CVE-TTP Knowledge Graph, they have successfully bridged the gap between "what is broken" and "how it gets attacked."

Instead of security teams staring at a long list of broken locks, they now have a visual map that shows: "This specific lock is likely to be picked by a thief using this specific tool to achieve this specific goal." This helps defenders prioritize which locks to fix first and understand the criminal's intent, rather than just reacting to the damage.

The authors note that while their system is a huge step forward, it still struggles with ambiguous words (like not knowing if "service" means a software service or a repair service) and references (like "it" or "this issue"), which they hope to fix in the future.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →