Challenges Cybersecurity Architects Are Facing in a Cloud Computing Environment
Bibliographic record
Abstract
In the past decade, cloud computing has become an integral part of many companies’ business strategies and<br> IT architecture. Companies look to seek and adopt new business models, increase efficiency in handling massive amount of<br> data, handle fluctuations in computing workloads for customers and stakeholders, and gain a competitive advantage in<br> their industry. All these concepts have to be considered while also trying to deliver a product or service, and not disrupt<br> existing operations for the company. This paper will address the multilevel challenges and threats in cloud computing and<br> their potential solutions.<br> Cloud adoption has introduced the three types of cloud computing service models. The first is the Infrastructure as a<br> Service (IaaS) model, which is defined as an instant computing infrastructure that is provisioned and managed over the<br> internet. The second is the Platform as a Service (PaaS) model, in which companies essentially rent everything they need to<br> build an application and rely on the cloud provider for development tools, infrastructure, and operating systems. The third<br> is Software as a Service (SaaS) model, which is a software distribution model in which a cloud service provider will host<br> applications for customers and makes them available over the internet.<br> Many companies have developed a new approach called hybrid cloud computing. The growth of the hybrid cloud model<br> has allowed companies to use a mix of the three models with public and private clouds to create the best environment for<br> their company’s infrastructure. The top benefits of this approach include: Better security, Operating cost, improvements,<br> and Speed and agility increase.<br> A hybrid cloud model can eliminate or greatly reduce trade-offs and offer the best solutions for the company.<br> Implementation and management can still be challenging for a hybrid cloud model. Having different management tools for<br> a private or public cloud, introduces a fragmented IT infrastructure that strongly lacks interoperability and visibly for the<br> company.<br> Keywords-component; cybersecurity; cloud computing; hybrid 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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.015 | 0.017 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.008 | 0.011 |
| Scholarly communication | 0.023 | 0.025 |
| Open science | 0.002 | 0.012 |
| Research integrity | 0.007 | 0.012 |
| Insufficient payload (model declined to judge) | 0.006 | 0.003 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".