Skip to content

From Capability to Assurance in Autonomous Penetration-Testing Harnesses: A Framework and Reference Implementation

Sep 2026 · 1 citation · 37 references
Computer Science

TL;DR

This paper defines a framework of five assurance properties and claims an initial existence argument that the properties are realizable together, not a comparative performance result, and specifies the multi target, ablation, and adversarial evaluation protocol required to turn the framework obligations into measurements.

Abstract

Research on large language model agents for penetration testing is evaluated almost entirely by capability: whether the agent captures a flag or reproduces a proof of concept. That metric suits a benchmark but is silent on the properties that decide whether an autonomous agent can be used in an authorized engagement: whether a reported finding is true, whether the agent stayed inside its authorized scope, and whether an operator can audit what it did. We call these assurance properties and argue that they belong to the harness, the runtime wrapping the model, and can be enforced in code. This paper makes three contributions. First, we define a framework of five assurance properties (evidence grounding, non destructive claim reduction, computed severity, enforced authorization, and tamper evident accountability), each with a formal model and an explicit acceptance test, connected to prior work in capability based security, tamper evident logging, and software provenance. Second, we position representative systems (PentestGPT, the Cochise reference harness, MAPTA, and the trajectory judge PentestJudge) within the framework using published coding criteria, and identify a consistent assurance gap. Third, we study one open source implementation, NeuroSploit, pinned to an exact commit, reporting its architecture, its complexity cost, and a content addressed artifact bundle from a run against a public deliberately vulnerable target. We execute the deterministic authorization and audit acceptance tests directly and find and report a real enforcement gap, which we reflect by scoring both properties as partial. We therefore claim an initial existence argument that the properties are realizable together, not a comparative performance result, and we specify the multi target, ablation, and adversarial evaluation protocol required to turn the framework obligations into measurements.

View source

Similar papers

Book Open access Oct 2026

Making Vulnerability Proof-of-Concepts Trustworthy and Usable: From Empirical Diagnosis to Operational Validation

Vulnerability Proof-of-Concepts (PoCs) are the executable evidence that a disclosed vulnerability is real and reachable, the artifact defenders use to suppress false positives, verify patches, delimit affected versions, and judge exploitability. Their value hinges not on whether a PoC exists but on whether it is usable...

Wen-Jing Dang · 0 citations
#artificial intelligence Preprint Oct 2026

Beyond Maliciousness: Static and Runtime Attack-Surface Profiling of Agent Skills

Agent skills are Markdown documents that a tool-using agent reads as instructions and then acts on with the privileges of the session that loaded them. Installing one grants authority (the standing to direct the agent, not new privilege), and the size of that grant is what we measure. We present a two-phase attack-surf...

Ratnesh Pandey, Japneet Singh, Harsh Akshit et al. · 0 citations
Book Open access Oct 2026

Formal Runtime Verification for Tool-Using LLM Agents: An Offline Same-Benchmark Study on AgentDojo and STAC

Results show that formal temporal monitoring adds value exactly when the trace exposes trustworthy history, and quantify how far current benchmarks are from that point and propose a twelve-field enforcement-ready trace schema.

Nikolaos Kekatos, Stylianos Basagiannis, Marinelio Chintri et al. · 2 citations
#software testing Book Open access Oct 2026

Using LLM Agents for Security Testing of Compiled Mobile Applications: A Case Study on a Real-World Compiled iOS App

It is concluded that developers should use LLMs at the source-code level to counter adversaries applying the same techniques on decompiled code and research should advance decompilation support for the growing language diversity in the iOS ecosystem.

Fabian Scherf, Florian Magin · 0 citations

Related blog posts

Hugging Face Blog Oct 20, 2026

MPS in PyTorch 2.15

We’re on a journey to advance and democratize artificial intelligence through open source and open science.

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