Research

Paper

TESTING March 24, 2026

Towards Leveraging LLMs to Generate Abstract Penetration Test Cases from Software Architecture

Authors

Mahdi Jafari, Rahul Sharma, Sami Naim, Christopher Gerking, Ralf Reussner

Abstract

Software architecture models capture early design decisions that strongly influence system quality attributes, including security. However, architecture-level security assessment and feedback are often absent in practice, allowing security weaknesses to propagate into later phases of the software development lifecycle and, in some cases, to remain undiscovered, ultimately leading to vulnerable systems. In this paper, we bridge this gap by proposing the generation of Abstract Penetration Test Cases (APTCs) from software architecture models as an input to support architecture-level security assessment. We first introduce a metamodel that defines the APTC concept, and then investigate the use of large language models with different prompting strategies to generate meaningful APTCs from architecture models. To design the APTC metamodel, we analyze relevant standards and state of the art using two criteria: (i) derivability from software architecture, and (ii) usability for both architecture security assessment and subsequent penetration testing. Building on this metamodel, we then proceed to generate APTCs from software architecture models. Our evaluation shows promising results, achieving up to 93\% usefulness and 86\% correctness, indicating that the generated APTCs can substantially support both architects (by highlighting security-critical design decisions) and penetration testers (by providing actionable testing guidance).

Metadata

arXiv ID: 2603.23698
Provider: ARXIV
Primary Category: cs.SE
Published: 2026-03-24
Fetched: 2026-03-26 06:02

Related papers

Raw Data (Debug)
{
  "raw_xml": "<entry>\n    <id>http://arxiv.org/abs/2603.23698v1</id>\n    <title>Towards Leveraging LLMs to Generate Abstract Penetration Test Cases from Software Architecture</title>\n    <updated>2026-03-24T20:32:18Z</updated>\n    <link href='https://arxiv.org/abs/2603.23698v1' rel='alternate' type='text/html'/>\n    <link href='https://arxiv.org/pdf/2603.23698v1' rel='related' title='pdf' type='application/pdf'/>\n    <summary>Software architecture models capture early design decisions that strongly influence system quality attributes, including security. However, architecture-level security assessment and feedback are often absent in practice, allowing security weaknesses to propagate into later phases of the software development lifecycle and, in some cases, to remain undiscovered, ultimately leading to vulnerable systems. In this paper, we bridge this gap by proposing the generation of Abstract Penetration Test Cases (APTCs) from software architecture models as an input to support architecture-level security assessment. We first introduce a metamodel that defines the APTC concept, and then investigate the use of large language models with different prompting strategies to generate meaningful APTCs from architecture models. To design the APTC metamodel, we analyze relevant standards and state of the art using two criteria: (i) derivability from software architecture, and (ii) usability for both architecture security assessment and subsequent penetration testing. Building on this metamodel, we then proceed to generate APTCs from software architecture models. Our evaluation shows promising results, achieving up to 93\\% usefulness and 86\\% correctness, indicating that the generated APTCs can substantially support both architects (by highlighting security-critical design decisions) and penetration testers (by providing actionable testing guidance).</summary>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.SE'/>\n    <published>2026-03-24T20:32:18Z</published>\n    <arxiv:comment>8 pages</arxiv:comment>\n    <arxiv:primary_category term='cs.SE'/>\n    <author>\n      <name>Mahdi Jafari</name>\n    </author>\n    <author>\n      <name>Rahul Sharma</name>\n    </author>\n    <author>\n      <name>Sami Naim</name>\n    </author>\n    <author>\n      <name>Christopher Gerking</name>\n    </author>\n    <author>\n      <name>Ralf Reussner</name>\n    </author>\n  </entry>"
}