MétaCan
Menu
Back to cohort
Record W2141794726 · doi:10.17722/ijme.v3i2.259

An Overview of Public Cloud Security Issues

2014· article· en· W2141794726 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueInternational Journal of Management Excellence · 2014
Typearticle
Languageen
FieldComputer Science
TopicCloud Data Security Solutions
Canadian institutionsnot available
Fundersnot available
KeywordsCloud computingCloud computing securityOutsourcingComputer scienceComputer securityOrder (exchange)PurchasingThe InternetScale (ratio)Risk analysis (engineering)BusinessMarketingWorld Wide Web

Abstract

fetched live from OpenAlex

Traditionally, computational needs of organizations were alleviated by purchasing, updating and maintaining required equipments. Beside expensive devices, physical space to hold them, technical staffs to maintain them and many other side costs were essential prerequisites of this matter. Nowadays with the development of cloud computing services, a huge number of peoples and organizations are served in terms of computational needs by large scale computing platforms. Offering enormous amounts of economical compute resources on-demand motivates organizations to outsource their computational needs incrementally. Public cloud computing vendors offer their infrastructure to the customers via the internet. It means that the control of customers’ data is not in their hands anymore. Unfortunately various security issues are emerged from this subject. In this paper the security issues of public cloud computing are overviewed. More destructive security issues are highlighted in order to be used by organizations in making better decisions for moving to cloud.

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.001
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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.924
Threshold uncertainty score0.710

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0040.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.052
GPT teacher head0.339
Teacher spread0.286 · 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