← Latest papers
💻 computer science

Enabling Transparent Cyber Threat Intelligence Combining Large Language Models and Domain Ontologies

This paper proposes a novel methodology that combines Large Language Models with domain ontologies and SHACL constraints to create an AI agent that significantly improves the accuracy and explainability of extracting structured, semantically valid information from cybersecurity logs, particularly for honeypot data.

Original authors: Luca Cotti, Anisa Rula, Devis Bianchini, Federico Cerutti

Published 2026-04-28
📖 4 min read☕ Coffee break read

Original authors: Luca Cotti, Anisa Rula, Devis Bianchini, Federico Cerutti

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 you are a detective trying to solve a crime, but instead of clear police reports, you are handed thousands of pages of messy, handwritten notes, scribbles, and half-finished sentences. This is what cybersecurity experts face when they try to read system logs. These logs are the "diaries" of computers, recording every action taken, but they are often unstructured, confusing, and full of jargon.

This paper introduces a new tool called OntoLogX to help detectives (cybersecurity analysts) make sense of this chaos. Here is how it works, broken down into simple concepts:

1. The Problem: The "Messy Room"

Traditional methods for reading these logs are like trying to find a specific toy in a messy room using only a flashlight and a fixed list of rules. If the toy is hidden under a pile of clothes or labeled with a weird name, the flashlight misses it.

  • The Issue: Computers generate logs that are unstructured and ambiguous. Old methods struggle to find the "bad guys" (malicious events) reliably.
  • The New Tool: The authors use Large Language Models (LLMs). Think of an LLM as a super-smart intern who has read almost everything on the internet and can understand natural language. However, this intern can be a bit "dreamy"—sometimes they make things up or get the facts slightly wrong because they aren't strictly bound by rules.

2. The Solution: The "Architect" and the "Inspector"

To fix the intern's tendency to dream, the authors built a system called OntoLogX that adds two crucial layers of control:

  • The Architect (The Ontology): Before the intern starts writing, the system gives them a strict blueprint called an Ontology. This is like a specific set of building blocks and a rulebook. It says, "You can only build a house using these specific bricks (classes) and you must connect them in this specific way (relationships)." It forces the AI to organize the messy log data into a neat, structured format called a Knowledge Graph.
  • The Inspector (SHACL Validation): Once the intern builds the structure, a strict inspector (using a tool called SHACL) checks the work. The inspector asks: "Did you use the right bricks? Did you connect the roof to the walls correctly? Is there a missing door?"
    • If the building is wrong, the inspector sends it back to the intern with a note: "Fix this."
    • The intern tries again. This loop continues until the building is perfect.

3. The Process: Learning from Examples

The system doesn't just ask the intern to guess. It uses a clever trick called Retrieval Augmented Generation.

  • Imagine the intern has a library of past successful cases. When a new messy log comes in, the system finds the most similar past cases (examples) and shows them to the intern.
  • It says, "Look at how we solved this similar puzzle before. Use that same style to solve this new one."
  • This helps the intern understand exactly what the "Architect" (the Ontology) wants, leading to much better results.

4. The Results: Better Accuracy, Not Speed

The authors tested this system against the "old way" (just asking the intern to write without the Architect or the Inspector).

  • The Outcome: The new method was significantly more accurate. It found more of the "bad guys" (higher Recall) and made fewer mistakes (higher Precision).
  • The Trade-off: The paper explicitly states they prioritized quality over speed. The new method takes a bit longer because it has to check the work, get feedback, and try again. But the final result is a much more reliable and trustworthy map of the cyber threats.
  • The Winner: Among the different AI models tested, Claude 3.5 Sonnet performed the best, though open-source models like Llama 3.3 also did very well.

Summary Analogy

If reading cybersecurity logs is like trying to translate a chaotic, handwritten diary into a formal legal document:

  • Old Method: You ask a smart translator to just "do their best." They might get the meaning, but the format will be messy and inconsistent.
  • OntoLogX: You give the translator a strict legal template (Ontology), show them examples of perfect legal documents (Few-shot examples), and have a strict lawyer (SHACL) review every draft. If the draft isn't perfect, the lawyer sends it back for corrections. The result is a flawless legal document every time, even if it takes a little longer to produce.

Key Takeaway: This paper proves that combining a "smart AI" with "strict rules" and "quality checks" creates a much more reliable system for turning messy computer logs into clear, actionable intelligence about cyber threats.

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 →