Metraipolis › archive › dc_2365d6780cf2
Using LLMs to Elicit Security Requirements for Service-Oriented Cyber Ranges — arXiv:2609.00886
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.00886
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-17T06:46:43.748Z
- SHA-256 of the archived text
57719764f493594129993974a2ca7987fa4b6d677dbd9caa636dddb0f34ce6ff- Stable URL of this page
https://metraipolis.com/documento/dc_2365d6780cf2
How to cite
Using LLMs to Elicit Security Requirements for Service-Oriented Cyber Ranges — arXiv:2609.00886 — arXiv (en), https://arxiv.org/abs/2609.00886 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_2365d6780cf2 (Metraipolis archive dc_2365d6780cf2, sha256 57719764f493594129993974a2ca7987fa4b6d677dbd9caa636dddb0f34ce6ff)
BibTeX
@misc{dc2365d6780cf2,
title = {Using LLMs to Elicit Security Requirements for Service-Oriented Cyber Ranges — arXiv:2609.00886},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.00886},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_2365d6780cf2; sha256 57719764f493594129993974a2ca7987fa4b6d677dbd9caa636dddb0f34ce6ff},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.00886. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Cyber ranges are complex environments comprising many interacting components and stakeholders with different security concerns. The Service-Oriented Cyber Range (SOR) is no exception, particularly when it comes to training scenarios targeting critical infrastructure. Security concerns are translated into security requirements, the elicitation of which is usually difficult and time-consuming. This work examines how large language models can assist in eliciting security requirements for a service-oriented range and help produce a useful baseline for designers and developers. The approach follows a SEBoK-guided process in which security mission objectives and stakeholder needs were first identified and then provided as a prompt context along with architectural guidelines to five LLMs: GPT-5.2, Gemini 3.1 Pro, Grok 4.1, Sonar, and Kimi K2.5. The models generated 84 security requirements in total, which were consolidated into a comprehensive set of 27 requirements and then mapped to the architectural layers of the service-oriented range. The final set was evaluated by five cybersecurity experts against the criteria of necessity, clarity, completeness, feasibility, and testability, with an additional rejection option. The results showed a high acceptance rate, specifically for necessity with 98.5%, clarity with 87.4%, completeness with 85.2%, feasibility with 78.5%, and rejection with 0.7%. Testability was lower at 44.4%, indicating a slight lack of information on how these requirements could be tested. These findings show that LLMs can support early stages of the elicitation of security requirements, although human review is still needed, especially to improve or adjust certain aspects of the requirements. Tema degli esploratori: fiducia digitale e crittografia (retro-catalogo arXiv: annunci del 2026-09-02 in cs.CR). Categorie arXiv: Cryptography and Security (cs.CR). Pagina del lavoro: https://arxiv.org/abs/2609.00886 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-17T06:38:14.366Z dalla pagina https://arxiv.org/catchup/cs.CR/2026-09-02?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).