MétaCan
Menu
Back to cohort
Record W4313121388 · doi:10.1109/dsa56465.2022.00059

Security Pattern Detection Through Diagonally Distributed Matrix Matching

2022· article· en· W4313121388 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

Venue2022 9th International Conference on Dependable Systems and Their Applications (DSA) · 2022
Typearticle
Languageen
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsQueen's University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceSoftware security assuranceSecurity testingComputer security modelDiagonalSoftwareData miningMatching (statistics)Security serviceSecurity information and event managementComputer securityCloud computing securityInformation securityStatisticsMathematicsOperating system

Abstract

fetched live from OpenAlex

Security requirements should be realized in the design phase of a secure software system. Security patterns are artifacts used to implement security requirements as to security controls and features. The strength in the security of software systems is directly proportional to the number of security patterns used. We can use the number of existing security patterns to measure the security strength of software systems. Therefore, early detection of the absence of security patterns or non-standard security features will tremendously reduce development and maintenance costs. We first convert the security patterns and the software system model into graphs and store them as matrices in the security pattern detection process. Then, we explore and detect security patterns inside the software system using a matching technique. Finally, we remove false positives with the help of a semantic analysis technique. This paper proposes a diagonally distributed matrix matching (DDMM) technique for detecting security patterns. The detection technique uses a standard security pattern matrix (SPM). It selects the main diagonal of the SPM. Then compares it for matching with the diagonals of the target system matrix (TSM) using all possible combinations of diagonal elements. A security pattern detection tool is implemented based on the proposed DDMM technique. The experimental results show sufficient detection accuracy and reasonable time consumption for five java-based software projects with zero false positives.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
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.969
Threshold uncertainty score0.881

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.017
GPT teacher head0.268
Teacher spread0.250 · 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