MétaCan
Menu
Back to cohort

AppArmor For Health Data Access Control: Assessing Risks and Benefits

2020· article· en· W3126782213 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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSecurity and Verification in Computing
Canadian institutionsUniversité de Sherbrooke
Fundersnot available
KeywordsMandatory access controlComputer scienceComputer securityAccess controlConfidentialityIsolation (microbiology)Linux kernelEnforcementOperating systemRole-based access control

Abstract

fetched live from OpenAlex

The AppArmor Linux Security Module (LSM) is widely used on Linux operating systems as it, among other things, provides mandatory access control (MAC) and isolates processes. This isolation helps meet the privacy requirements for critical applications. These application security policies are defined with profiles loaded into the Linux system kernel. However, these access control mechanisms are far from covering all the rising demands for confidentiality enforcement regarding critical applications. This paper conducts a risks and benefits analysis to assess whether a healthcare infrastructure can safely rely on the AppArmor LSM to protect its sensitive data. Thus, the general architecture of AppAmor comes to be detailed. Then, a static code analysis is performed to study the data structures found in the LSM. Finally, the outbreak of would-be side-channel attacks from userspace is discussed while offering mitigation methods. The result of this analysis shows that the AppArmor LSM is susceptible to side-channel attacks and should be used as part of a more comprehensive defense-in-depth strategy.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.982
Threshold uncertainty score0.750

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.0010.001
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.458
GPT teacher head0.448
Teacher spread0.010 · 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

Quick stats

Citations7
Published2020
Admission routes1
Has abstractyes

Explore more

Same topicSecurity and Verification in ComputingFrench-language works237,207