Metraipolis › archive › dc_7bf7f0151075
What Must Be Done Here? Using a Bounded Application-Security Ontology at the Point of Change — arXiv:2611.01127
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2611.01127
- License (as archived)
- CC0-1.0
- Archived
- 2026-11-03T18:33:00.076Z
- SHA-256 of the archived text
93ee30ecc7ef0abd73f00db7f4f265acb9549fdd485ff88740d2ba1fdee70e23- Stable URL of this page
https://metraipolis.com/documento/dc_7bf7f0151075
How to cite
What Must Be Done Here? Using a Bounded Application-Security Ontology at the Point of Change — arXiv:2611.01127 — arXiv (en), https://arxiv.org/abs/2611.01127 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_7bf7f0151075 (Metraipolis archive dc_7bf7f0151075, sha256 93ee30ecc7ef0abd73f00db7f4f265acb9549fdd485ff88740d2ba1fdee70e23)
BibTeX
@misc{dc7bf7f0151075,
title = {What Must Be Done Here? Using a Bounded Application-Security Ontology at the Point of Change — arXiv:2611.01127},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2611.01127},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_7bf7f0151075; sha256 93ee30ecc7ef0abd73f00db7f4f265acb9549fdd485ff88740d2ba1fdee70e23},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2611.01127. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
The security guidance that bears on code is real but scattered. It lives across secure-development frameworks, verification standards, controls catalogues, threat taxonomies, and, increasingly, normative regimes such as the EU's NIS2 -- and most of it is written for readers other than the engineer, or the AI assistant, at a point of change. Existing cybersecurity ontologies largely model attacks, indicators, and risk for detection and analysis, not the engineering-practice substance one must act on. This paper presents a use case for an existing bounded application-security ontology, AppSec Core, whose construction and validation are reported separately. We show how it is used. It makes the engineering-actionable fraction of those authorities addressable as a typed working set: the control objectives that apply, the practices that realize them, the mechanisms that implement them, and the evidence artifacts they expect, each traceable to the sources that justify it. We reach that working set from two entry points that recur in practice. Forward, from a code change: a change to authentication middleware scopes to its governing domain slice and returns the obligations the change must satisfy. Inverse, from a normative obligation: "make this NIS2-compliant" resolves a generic legal duty into the concrete engineering obligations it implies across slices, surfacing precisely the fraction of a mostly-governance regulation that lands in code. The same working set is what a human engineer reads and what an LLM-grounded assistant is handed as grounding. The use turns "read every applicable authority" into "satisfy this typed working set", for a code change or a compliance duty alike. The contribution is the demonstrated use; the artefact, its validation, and its governance are companion work. Tema degli esploratori: fiducia digitale e crittografia (elenco arXiv cs.CR, nuovi lavori del giorno). Categorie arXiv: Cryptography and Security (cs.CR) ; Software Engineering (cs.SE). Pagina del lavoro: https://arxiv.org/abs/2611.01127 — 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-11-03T18:12:23.781Z dalla pagina https://arxiv.org/list/cs.CR/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).