MétaCan
Menu
Back to cohort

Systems Security Engineering: What Every System Engineer Needs to Know

2017· article· en· W2750628123 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueINCOSE International Symposium · 2017
Typearticle
Languageen
FieldComputer Science
TopicInformation and Cyber Security
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsEngineering managementTrustworthinessRelevance (law)Perspective (graphical)EngineeringComputer scienceValue (mathematics)Engineering ethicsSystems engineeringComputer securityPolitical science

Abstract

fetched live from OpenAlex

Abstract This paper addresses System Security Engineering (SSE) roles and responsibilities in a framework concept. The framework is a tool to be used with existing guidance for SSE and System Engineering (SE); and, to demonstrate that program protection is not just the responsibility of any one engineer or discipline, it is the responsibility of an entire team. SSE is a specialty engineering discipline of SE. The SSE discipline provides the security approach to SE processes, activities, tasks, products, and artifacts for engineering trustworthy and resilient secure systems. The authors working this project for the INCOSE SSE working group have extensive international experience and exposure including the UK and Australia and have focused their efforts on the international perspective to ensure its relevance and value to the broader international SE community. The framework presented should be leveraged by SEs so they can better understand and integrate SSE into their overall SE processes.

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 imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.973
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0030.004
Open science0.0030.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

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.

Opus teacher head0.006
GPT teacher head0.221
Teacher spread0.215 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it