10.46243/jst.2025.v10.i02.pp15-22 registered
Integrating azure network rules for storage account through terraform in CI/CD pipelines: automating storage account access restrictions to public IP
Resolves to https://www.jst.org.in/index.php/pub/article/view/1147
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2025.v10.i02.pp15-22
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 5209d5bad88140cf…
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
Integrating azure network rules for storage account through terraform in CI/CD pipelines: automating storage account access restrictions to public IP (PrincipalTitle)
Published 2025-02-07
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 10 · issue 2 · pages 15–22
Agents
- Banda Saikumar (author) · ORCID 0009-0003-5098-4765
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2025.v10.i02.pp15-22
Abstract
The research discusses the automation of the Azure storage account network rule through Terraform. Itadvocates for security enhancements like the inclusion of MFA in the case of a storage account and migrationtoward a zero-trust security model, automation of vulnerability scanning and compliance checks through the CI/CDpipelines, shifting left of security risk detection. Emphasis can also be laid on logging and monitoring activitiesregarding changes in network rules and attempts to access storage accounts. Advanced security coupled withautomation improves the management, security and operational efficiency of Azure storage accounts multiple.
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.2025.v10.i02.pp15-22 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Integrating azure network rules for storage account through terraform in CI/CD pipelines: automating storage account access restrictions to public IP (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Banda Saikumar publisher: Longman Publishers published: 2025-02-07 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 10 · no. 2 · pp. 15–22 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 | 2025-05-10 | 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) | 112 fields set · sha256 619c8b6dae2f… |
| 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.
