MétaCan
Menu
Back to cohort
Record W4391937118 · doi:10.1109/qrs-c60940.2023.00054

A Security Compliance-by-Design Framework Utilizing Reusable Formal Models

2023· article· en· W4391937118 on OpenAlexaff
Quentin Rouland, Stojanche Gjorcheski, Jason Jaskolka

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicSafety Systems Engineering in Autonomy
Canadian institutionsCarleton University
Fundersnot available
KeywordsCompliance (psychology)Computer scienceFormal verificationFormal methodsSoftware engineeringComputer securityProgramming language

Abstract

fetched live from OpenAlex

In recent years, increasing concerns about the security of critical infrastructure have led to the development of various security standards, policies, and regulations. Consequently, it has become essential for any organization responsible for such infrastructure to ensure that their system software architecture complies with these security guidelines. As a result, in this paper we propose a methodology to enhance the security of software systems by incorporating compliance verification from the early stages of design, thereby proactively addressing potential flaws. Furthermore, we present a novel method for modeling a security compliance baseline based on the specification and reuse of analysis models targeting standards, policies, and regulations. This approach streamlines the compliance process, facilitating adherence to multiple security standards while promoting the reuse of security compliance analysis models. To demonstrate the practicality of the suggested framework and technique, we illustrate representative architecture compliance checks on a Supervisory Control and Data Acquisition (SCADA) system.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.027
metaresearch head score (Gemma)0.020
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.027
Threshold uncertainty score0.140

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0270.020
Meta-epidemiology (narrow)0.0020.003
Meta-epidemiology (broad)0.0010.004
Bibliometrics0.0050.002
Science and technology studies0.0020.007
Scholarly communication0.0060.009
Open science0.0050.006
Research integrity0.0040.006
Insufficient payload (model declined to judge)0.0030.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.056
GPT teacher head0.251
Teacher spread0.195 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations1
Published2023
Admission routes1
Has abstractyes

Explore more

Same topicSafety Systems Engineering in AutonomyFrench-language works237,207