Cited by 20E-Government and Public ServicesInformation and Cyber SecurityInformation Technology Governance and Strategy

The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index; none of the 9 sources its claims cite is checked for support yet.

Risiko Aset Teknologi Informasi: Studi kasus Implementasi Manajemen Risiko SPBE Dinas Komunikasi dan Informatika Pemerintah Kota Balikpapan

Open access
Bisma, Rahadian·2022·Journal of Information Engineering and Educational Technology

Abstract

Sistem Pemerintahan Berbasis Elektronik merupakan penyelenggaraan pemerintahan yang memanfaatkan teknologi informasi dan komunikasi untuk memberikan layanan kepada instansi yang menggunakan SPBE. Dari penelitian ditemukan 261 risiko yang diidentifikasi yang dapat dikaitkan dengan risiko SPBE. Implementasi Manajemen risiko peneliti menggunakan Cobit5 for risk, ISO 31000:2018 dan KemenPAN RI No 5 2020 untuk dijadikan pedoman dan analisa terhadap manajemen risiko SPBE. sehingga diharapkan penelitian ini dapat sesuai dengan peraturan dalam penerapan Manajemen Risiko SPBE. Seluruh temuan risiko diberikan rekomendasi dan sistem pengendalian risiko untuk memperkecil level risiko. Budaya atau penerapan manajemen risiko perlu di tingkatkan dan dioptimalkan terutama di bagian Komunikasi dan konsultasi, pencatatan dan pelaporan serta pemantauan dan review yang harus dilakukan secara berkala

Overview

AI snapshot

Written from the paper’s full text.

TL;DR

This case study applies PermenPANRB No. 5/2020, COBIT 5 for Risk, and ISO 31000:2018 to assess SPBE information-technology asset risks at Dinas Komunikasi dan Informatika Pemerintah Kota Balikpapan. It identifies 261 SPBE assets/risks, with most risks concentrated in data/information and infrastructure categories and two very high risks related to servers and AC.

Key findings

  • The study identified 261 SPBE assets: 157 data/information assets, 75 hardware assets, 9 physical assets, 6 business-activity assets, and 14 HR assets. The abstract and conclusion also refer to 261 identified risks that can be linked to SPBE risk.
  • Risk categorization produced 7 SPBE risk categories: Data dan Informasi 136, Infrastruktur SPBE 75, Proses Bisnis 20, Keamanan SPBE 2, Layanan SPBE 6, SDM SPBE 14, and Bencana Alam 8. Impact areas were Kinerja 24, Layanan Organisasi 11, and Operasional dan Aset TIK 226.
  • Risk levels found were 2 low risks, 59 medium risks, 23 high risks, and 2 very high risks. The two very high risks concerned Server and AC, in the Infrastruktur SPBE risk category and the Operasional Aset TIK impact area.
  • For risk action, 176 risks were accepted by the organization, 83 had mitigation plans, and 2 were transferred to another party. The average time needed for risk-handling action plans was 1 year, linked to the local government’s annual budgeting cycle.

Methods

  • Case study at Dinas Komunikasi dan Informatika Pemerintah Kota Balikpapan, using the SPBE risk-management framework in PermenPANRB No. 5/2020, COBIT 5 for Risk, and ISO 31000:2018. COBIT analysis used the APO domain, specifically APO12 (manage risk) and its subdomains APO12.01–APO12.06.
  • Data were collected through direct observation at the agency and interviews with employees, producing risk-identification data and risk assessment for information-technology asset security.
  • The paper states six stages but enumerates: literature study; data collection; risk identification and risk analysis; risk evaluation and risk-handling recommendations; and conclusion. Risk scoring used a matrix combining 5 likelihood levels and 5 impact levels, with risk as likelihood × impact.

Limitations

  • Stated in the paper: some assets may not have been identified because of the study’s limitations.
  • Stated in the paper: a risk-aware culture among ASN had not yet grown, so many organizational assets were not recognized as carrying risk.
  • Evident from the text: the single-case design at one agency limits generalizability, and reliance on observation and interviews may introduce subjectivity; the paper does not discuss these as limitations.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.26740/jieet.v6n2.p73-79

Cites

0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Verification

Claims the paper makes

14 Own result · 9 Sources not found · 5 Own interpretation · 1 Not checked yet · 1 Own method

Show all 11 claims

  • It may state two separate claims as one. 11
  • Probably not a substantial claim. 11
19 of 19
  • The paper relies on this without support.

    Pemerintah Kota Balikpapan has not implemented risk management for the problems that occur.

    “Pemerintah Kota Balikpapan belum memiliki penerapan manajemen risiko dalam permasalahan yang terjadi.”
  • The paper relies on this without support.

    IT assets are an important part of an institution.

    “Aset teknologi informasi merupakan bagian penting dari sebuah instansi.”
  • The paper relies on this without support.

    Threats and attacks on IT assets from inside and outside can create large risks in government institutions and can disrupt ongoing business processes or even stop them.

    “Jika aset TI mendapat ancaman dan serangan dari dalam dan luar, dapat menimbulkan risiko besar di instansi pemerintah itu sendiri dan dapat mengganggu proses bisnis yang sedang berjalan bahkan dapat dihentikan.”
  • The paper relies on this without support.

    The existence of risk management can minimize the occurrence of risks that can have a large impact on the institution.

    “Dengan adanya manajemen risiko dapat meminimalisir terjadinya risiko yang dapat berdampak besar bagi instansi.”
4 of 4

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

Each contradiction between two passages listed here was confirmed by an independent check.

3 of 3

Citations

Cites

The publisher hasn’t deposited this paper’s reference list.

Research works printed but not linked: 2

  1. IT Risk Management Based on COBIT 5 for Risk at Deutsche Telekom AG -ISACA (2018) [Online], https://www.isaca.org/resources/isaca- journal/issues/2018/volume-3/it-risk-management-based-on-cobit-5- for-risk-at-deutsche-telekom-ag
  2. Aprianto K., Endroyono, Supeno Mardi S.H. 2021. " E-Government Risk Management Analysis Using COBIT 5 For Risk and ISO 31000:2018 in Magetan Regency" Jurnal IPTEK-KOM (Jurnal Ilmu Pengetahuan dan Teknologi Komunikasi) eISSN 2527 -4902 Vol. 23 No. 2, Desember 2021: 107 - 123

Cited by

Sorted by citations

Metadata

Authors
Bisma, R.
Affiliations
Universitas Negeri Surabaya (ID)
Corresponding author
Bisma, Rahadian
Venue
Journal of Information Engineering and Educational Technology
Published
2022-12-24
Volume
6
Issue
2
Pages
73-79
ISSN
2549-869X (ISSN-L)
OpenAlex
W4312176348
Cited by
20
References
0
Citations by year
2026: 1 · 2025: 4 · 2024: 8 · 2023: 7
FWCI
10.14
Type
journal article
Language
id
Open access
Locations
Journal of Information Engineering and Educational Technology (publishedVersion, cc-by-nc-sa)
Topics
  • Social Sciences › Political Science and International Relations › E-Government and Public Services
  • Physical Sciences › Computer Science › Information Systems › Information and Cyber Security
  • Social Sciences › Business, Management and Accounting › Management Information Systems › Information Technology Governance and Strategy
Keywords
e-government, risk management, risk identification, risk control, ISO 31000, risk management guidelines, Balikpapan

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

A language model drew the claims from the paper on 2026-11-07, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).

A second model labelled each claim on 2026-11-07 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review