arXiv (All)
open access
What Must Be Done Here? Using a Bounded Application-Security Ontology at the Point of Change
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,
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Cybersecurity Ontology for Dynamic Analysis of IT Systems#419041
- Cybersecurity Ontology for Dynamic Analysis of IT Systems#11161
- Structured Security Explanations for Learning-Based Vulnerability Detection#1488589
- Structured Security Explanations for Learning-Based Vulnerability Detection#1483101
- An IANA Registry for Level of Assurance (LoA) Profiles#420683
Record · ID 1536935
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive