Preserving and Sharing Knowledge – Extending the UAF Security Views with Libraries, Patterns and Profiles
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Abstract Knowledge and experience are gained during the execution of every project. This knowledge remains in the heads of the engineers, but often is not distributed more widely. In Model‐Based Systems Engineering (MBSE) projects, this knowledge can include problem solving techniques, algorithms, libraries of types, patterns, interfaces, components, etc. One of the ways to preserve this knowledge is by creating libraries of these reusable assets. For example, the newest version of Unified Architecture Framework (UAF) included a library developed by Mitre of 1200 different security controls defined in National Institute of Standards and Technology (NIST) standard 800‐53r5. These controls can be referenced on projects to mitigate many common security risks. Each defined control can be integrated with the corresponding risks, security metrics, mitigating elements, solutions, and so forth. All these elements could then be used to construct Security Patterns showing risks that the security controls can mitigate as well as abstract solutions that can satisfy these controls. Patterns publicly provided as a curated, searchable, solution set library could be leveraged by projects and augmented over time, preserving their Intellectual Property (IP) and knowledge assets. This paper discusses these concepts and methods and demonstrates how they can be applied to improve system security.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it