10.46243/jst.2022.v7.i05.pp148-159 registered
On Making Cloud More Secure and Trustworthy
Resolves to https://www.jst.org.in/index.php/pub/article/view/513
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i05.pp148-159
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 744349d1a1484552…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
On Making Cloud More Secure and Trustworthy (PrincipalTitle)
Published 2023-07-18
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 5 · pages 148–159
Agents
- Tanmaya Kumar Das Tanmaya Kumar Das (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i05.pp148-159
Abstract
Cloud computing has grown in popularity as a result of recent advancements in technology. Academics and businesses alike place a high value on computing because of the abundance of data and the emergence of new AI paradigms. The problems of sca lability and availability were quickly solved by cloud computing. However difficult it has been, cloud service providers have managed to provide low -cost options. Although servers may delete rarely viewed files to save space, certain cloud firms protect da ta integrity. However, they can't control server and network difficulties, thus they can't guarantee data availability. Customer data integrity, availability and exposure are feared by customers. Amazon S3 and Amazon EC2, Gmail email deletion, and the Side kick cloud disaster validated customers' concerns. – Amazon.com A customer's primary concern is the safety of their personal information. Trust and security are handled by cloud companies. Proof and data are difficult to obtain. This paper describes the se curity principles and security measures of the cloud environments and presents some of the security assessment criteria based upon the deployment aspects of the cloud based application services in the autonomous environment
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2022.v7.i05.pp148-159 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | On Making Cloud More Secure and Trustworthy (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Tanmaya Kumar Das Tanmaya Kumar Das publisher: Longman Publishers published: 2023-07-18 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 5 · pp. 148–159 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 115 fields set · sha256 7126e88cf036… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
