MétaCan
Menu
Back to cohort
Record W4285088927 · doi:10.1049/ise2.12079

The poor usability of OpenLDAP Access Control Lists

2022· article· en· W4285088927 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

VenueIET Information Security · 2022
Typearticle
Languageen
FieldSocial Sciences
TopicAccess Control and Trust
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsUsabilityComputer scienceWeb usabilityWorld Wide WebCognitive walkthroughPluralistic walkthroughAccess controlUsability goalsComputer securityKnowledge managementHuman–computer interaction

Abstract

fetched live from OpenAlex

Abstract The usability of Access Control Lists (ACLs) of a widely used enterprise software for directory information services called OpenLDAP is addressed. A directory service is used to store a variety of data such as employee information and passwords, and can be seen as a critical infrastructure component of an enterprise. Security and in particular, access control of such data is of paramount importance, and OpenLDAP provides ACLs for this purpose that an administrator can configure. The usability, that is, the ease with which a human administrator can express a policy in an ACL, is then an important issue because misconfigurations are known to be a major cause of security vulnerabilities. Motivated by public pronouncements regarding the poor usability of OpenLDAP ACLs, a systematic study towards evaluating their usability is carried out. The authors begin with a cognitive walkthrough, which identifies the broad issues, which then informs the design of an ethics‐approved study of 50 human participants. This study reveals that indeed, even with a limited syntax, adequate training and a focus only on devising a policy from scratch, OpenLDAP ACLs suffer from poor usability. The data gathered from this study is analysed further, and more detailed observations are made such as those regarding the difference in difficulty for different kinds of policy goals, and the nature of errors human participants make with OpenLDAP ACLs. As such, this work makes an important contribution to enterprise security and provides important insights for a (re)design of ACLs, in particular for OpenLDAP.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.920
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0020.000
Scholarly communication0.0000.002
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.015
GPT teacher head0.319
Teacher spread0.304 · 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