MétaCan
Menu
Back to cohort
Record W2074457927 · doi:10.1109/hpcc.and.euc.2013.223

On Dynamic & Subjective Trust for Privacy Policy Enforcement in Cloud Computing

2013· article· en· W2074457927 on OpenAlexaff
Karthick Ramachandran, Hanan Lutfiyya, Mark Perry

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicCloud Data Security Solutions
Canadian institutionsWestern University
Fundersnot available
KeywordsCloud computingComputer scienceEnforcementService providerComputer securityComputational trustService (business)Trusted ComputingInternet privacyBusinessReputation

Abstract

fetched live from OpenAlex

Trust relationships are subjective and dynamic. One entity's trust over a subject is completely independent of some other entity's trust: trust is subjective. Trust also evolves dynamically over time. The growth of cloud computing over the last few years has created an environment where clients need to transact with cloud service providers even though the cloud service clients may or may not completely trust the provider at any given time. There is a need for the provider to acknowledge this dynamic and subjective trust assessment by each client by providing and modifying services individually for each client based on the trust assessment. This paper proposes a policy based approach to the implementation of subjective and dynamic trust so as to enable privacy policy enforcement in a cloud computing environment. We present an abstract model containing computational, storage and monitoring unit with configurable elements and describe algorithms that reflect how a change of trust influences the configuration of these elements. We prototype a system based on the abstract model with benchmarks.

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.007
metaresearch head score (Gemma)0.026
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: Empirical · Consensus signal: none
Teacher disagreement score0.008
Threshold uncertainty score0.039

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0070.026
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0020.005
Scholarly communication0.0060.011
Open science0.0020.004
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0020.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.029
GPT teacher head0.313
Teacher spread0.284 · 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
GenreEmpirical

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

Citations0
Published2013
Admission routes1
Has abstractyes

Explore more

Same topicCloud Data Security SolutionsFrench-language works237,207