MétaCan
Menu
Back to cohort

Hardware-based DLAS: Achieving geo-location guarantees for cloud data using TPM and Provable Data Possession

2014· article· en· W2032515484 on OpenAlexafffund
Ali Noman, Carlisle Adams

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicCloud Data Security Solutions
Canadian institutionsUniversity of Ottawa
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceCloud computingCloud storageServerTrusted Platform ModuleComputer securityComputer networkDatabaseCryptographyTrusted ComputingOperating system

Abstract

fetched live from OpenAlex

Recently the lack of geo-location assurance of data in cloud storage has been identified as one of the main reasons why organizations that deal with sensitive data (e.g., financial data, health related data) cannot adopt a cloud storage solution even if they want to. In this paper, we present a Hardware-based Data geo-Location Assurance Solution (HDLAS), which is suitable for almost all cloud storage applications available today. Trusted Platform Module (TPM) and a cryptographic scheme called Provable Data Possession (PDP) are the basis of our solution. We define a new attack model for HDLAS which seems to be a realistic attack model for the existing cloud storage applications. With the combination of a GPS receiver and TPM, HDLAS is able to offer its clients not only the accurate geo-location of their data but also a hardware-based root of trust for that. Unlike many existing solutions, HDLAS works even if a piece of data is replicated into different storage servers. Furthermore we also illustrate how easily HDLAS can be adopted in existing Cloud Storage Providers such as Microsoft Azure.

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.003
metaresearch head score (Gemma)0.011
Version: metacan-v3-hybrid-931329e0061cValidation 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: Empirical · Consensus signal: none
Teacher disagreement score0.003
Threshold uncertainty score0.016

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.011
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0010.003
Scholarly communication0.0030.006
Open science0.0020.007
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0020.001

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.103
GPT teacher head0.334
Teacher spread0.231 · 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 designSimulation or modeling
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

Citations5
Published2014
Admission routes2
Has abstractyes

Explore more

Same topicCloud Data Security SolutionsFrench-language works237,207