MétaCan
Menu
Back to cohort
Record W2294525553

Evolutionary analysis of access control models: a formal concept analysis method

2015· article· en· W2294525553 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

VenueComputer Science and Software Engineering · 2015
Typearticle
Languageen
FieldSocial Sciences
TopicAccess Control and Trust
Canadian institutionsUniversity of AlbertaPolytechnique Montréal
Fundersnot available
KeywordsRole-based access controlComputer scienceAccess controlFormal concept analysisPairwise comparisonSuiteSoftware engineeringDatabaseDistributed computingComputer securityArtificial intelligence
DOInot available

Abstract

fetched live from OpenAlex

Access control is an essential feature of most software systems security mechanisms. Role-Based Access Control (RBAC), likely the most popular access control technique, specifies user roles and associates each role with permissions to access distinct system data and functionalities. The types of system users, i.e., the roles, the sensitive system functionalities accessed through permissions, as well as the roles-permissions assignment rules evolve over time. In this paper, we discuss a methodology for analyzing and understanding the RBAC-evolution process and its relation to the overall evolutionary lifecycle of the system, motivated by the hypothesis that it may impact the overall system security. Our methodology relies on Formal Concept Analysis (FCA). First, we extract the roles-permissions matrix of each system version and we compute the implicit concept lattice. Next, we apply a suite of distance metrics to pairwise compare the matrices and concept lattices of subsequent system versions. By examining the evolution of these distance metrics, developers can easily notice which versions involve more, and more complex, RBAC changes that may indicate higher security risks. We demonstrate our methodology with a study of the MediaWiki platform.

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.003
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.930
Threshold uncertainty score0.417

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.005
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0010.000
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.037
GPT teacher head0.311
Teacher spread0.274 · 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