← Latest papers
💻 computer science

An End-to-End Framework for Functionality-Embedded Provenance Graph Construction and Threat Interpretation

This paper introduces Auto-Prov, an end-to-end framework that leverages large language models to automatically construct enriched provenance graphs from heterogeneous logs, thereby enhancing the performance and interpretability of anomaly detection systems while supporting analyst investigation through natural language attack summaries.

Original authors: Kushankur Ghosh, Mehar Klair, Kian Kyars, Euijin Choo, Jörg Sander

Published 2026-03-19
📖 5 min read🧠 Deep dive

Original authors: Kushankur Ghosh, Mehar Klair, Kian Kyars, Euijin Choo, Jörg Sander

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 your computer is a bustling city. Every time a program runs, a file opens, or a connection is made, it's like a citizen walking down a street, entering a building, or talking to a neighbor. In cybersecurity, we call these interactions logs.

The problem? A city generates millions of these "footsteps" every day. Most are normal (a baker buying flour), but some are part of a secret plot (a spy stealing blueprints). Security experts (analysts) try to find the spies by looking at these logs, but the logs are messy, written in different languages, and full of confusing details like "Thread ID 404" instead of "The Baker."

Currently, experts have to manually write complex rulebooks to translate these messy logs into a clear map of who did what to whom. This is slow, brittle, and breaks whenever the city changes its layout.

Enter Auto-Prov: The "Smart City Planner"

The paper introduces Auto-Prov, a new system that acts like an intelligent, adaptive city planner. Instead of needing a human to write the rulebook, Auto-Prov uses a super-smart AI (called a Large Language Model or LLM) to do the heavy lifting.

Here is how it works, broken down into four simple steps:

1. The Detective Who Learns on the Fly (Log Clustering)

Imagine a detective walking into a city where the street signs keep changing. One day, a log looks like a JSON file; the next, it looks like a text message.

  • Old Way: The detective stops and asks a human, "What does this new sign mean?"
  • Auto-Prov Way: The detective looks at the shape of the signs. "Ah, these three signs look similar; they must be the same type of street." It automatically groups similar logs together without needing a manual instruction manual. It figures out the "language" of the logs as it goes.

2. The Translator (Building the Map)

Once the logs are grouped, Auto-Prov needs to turn them into a Provenance Graph. Think of this graph as a giant family tree or a subway map showing who influenced whom.

  • The Challenge: Raw logs are like a jumbled pile of receipts. "Process 123 wrote to File 456 at 5:00 PM." It doesn't say why or what those things actually are.
  • The Solution: Auto-Prov uses a powerful AI (like GPT-4) to read a few sample logs and say, "Okay, this 'Process 123' is actually the 'Web Browser,' and it's 'downloading' a file."
  • The Magic: Once the AI figures out the pattern, it writes a simple, reusable rule (like a recipe) that can process millions of logs instantly, turning the messy pile into a clean, connected map.

3. The "Job Title" Badge (Functional Context)

This is the paper's biggest innovation.

  • The Problem: In a normal map, a node might just say "File A." But is File A a harmless calculator or a dangerous virus? Without knowing its job, it's hard to tell.
  • The Solution: Auto-Prov gives every node on the map a Job Title Badge.
    • Instead of just "Process X," it says "Word Processor."
    • Instead of "Connection Y," it says "Web Browser."
    • Why it matters: If a "Word Processor" suddenly tries to "send a secret email" to a stranger, that's suspicious! But if a "Web Browser" does it, that's normal. By understanding the function of the entity, the system can spot weird behavior much faster. If it sees a new, unknown entity, it looks at what it's doing (its behavior) and guesses its job title based on that.

4. The Storyteller (Attack Summarization)

When the system spots a threat, it doesn't just scream "ALERT!" and show a giant, confusing graph.

  • The Old Way: "Here is a graph with 5,000 nodes. Good luck finding the bad guy."
  • Auto-Prov Way: It acts like a Storyteller. It takes the complex graph and writes a short, plain-English story for the human analyst.
    • Example: "The attacker started by tricking the Web Browser (Initial Access), then used it to download a hidden tool (Execution), and finally tried to steal files from the Document Editor (Exfiltration)."
    • It even guesses the attacker's goal (e.g., "This looks like a 'Data Theft' tactic") so the analyst knows exactly what to look for.

Why This Matters

Think of the old way as trying to find a needle in a haystack by manually checking every single piece of straw with a magnifying glass. Auto-Prov is like a metal detector that not only finds the needle but also tells you, "This needle is likely part of a pirate's treasure map," and draws a picture of the pirate's ship for you.

The Results:
The researchers tested this on real-world data with different types of computers and different types of hackers. They found that:

  1. It works better: It catches more attacks and misses fewer.
  2. It adapts: When the computer system changes or new software is installed, Auto-Prov figures it out automatically without needing a human to rewrite the rules.
  3. It helps humans: The summaries it generates are clear and helpful, making the analyst's job much easier.

In short, Auto-Prov turns a chaotic, confusing pile of digital noise into a clear, understandable story of what's happening in your computer, helping you spot the bad guys before they cause trouble.

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 →