Skip to content
#software testing Open access

R+R: TTP-WorkBench: A Reproducibility Framework and Benchmark for TTP Extraction from Cyber Threat Reports

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

TTP-WorkBench Artifact TTP-WorkBench is a framework and benchmark for executing and comparing ten tools from prior work that extract MITRE ATT&CK tactics, techniques, and procedures from cyber threat reports. The artifact contains standardized tool adapters, container build specifications, curated prior-work data, and 281 new threat reports for benchmarking the tools. Provided scripts automate the container builds, dataset compilation, functionality tests, reproduction experiments, and capacity-aware analysis. The artifact documentation gives a setup procedure and three evaluation exercises to demonstrate that the artifact is functional and reproducible. Paper Abstract In cybersecurity operations, threat reports are a valuable resource to understand emerging threats, with MITRE ATT&CK serving as a common framework for interpreting the attacker’s tactics, techniques, and procedures (TTPs) described in the reports. Manually inferring TTPs from textual reports is difficult and time-consuming, which has motivated dozens of prior studies in automated extraction and labeling approaches. However, there has been no comprehensive comparison across tools, perhaps because many open-source implementations are difficult to run, lack experimental artifacts, or do not perform well on new data. While others have pointed out these systemic obstacles to reproducibility in the broader security research community, we practically analyze and address them in the field of automated TTP extraction. In this paper, we first analyze the TTP extraction literature through the lens of artifact reusability and then develop a reproducibility framework that directly addresses key challenges discovered while reviewing previous work. Furthermore, we create a benchmark dataset that curates existing data and adds 281 new threat reports with 4,732 TTP ground-truth labels. We demonstrate the usefulness of our reproducibility framework and benchmark dataset by adapting ten previously proposed tools. We then use the framework to reproduce key experiments published in prior work and test the tools on never-before-seen data. Our work advances the automated TTP extraction field by facilitating the reproducibility of past research and by making it easier to systematically compare future TTP extraction tools on a new benchmark dataset. Release - Version: `acsac26-ae-v1` - Publication date: `2026-09-20` - Zenodo DOI: `10.5281/zenodo.22839412` - GitHub release/tag: `https://github.com/stfran/ttp-workbench/tree/acsac26-ae-v1` - Git commit: `512b2749fe30612dfcc021cb962d4e7901b3f69f` Files and Integrity File Purpose Size (Bytes) Sha1 ttp-workbench-artifact.zip Artifact evaluation package and clean TTP-WorkBench source snapshot 4900909 333f2b5b0cb10732c81832aaf581bef3fd2a246f models.zip Models and other large reproduction assets used by the installer 37714873848 c905bf913b0b915ae1f324b69987fcb58de5524a` Download both ZIP files into the same directory. Extract `ttp-workbench-artifact.zip`; its `install.sh` locates the adjacent `models.zip`. Setup, evaluation, expected results, and teardown instructions are in `README.txt` and `use.txt` inside the extracted artifact directory. Licenses Project-authored software is released under the Apache License 2.0. Project-authored data is released under the Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0). Third-party software, models, datasets, report text, and MITRE ATT&CK material remain under their respective licenses or terms, as documented inside the artifact. `models.zip` contains checkpoints based on Llama 3.1 and the archive retains the Llama 3.1 Community License and required attribution notice. Built with Llama.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.