Bayangin satu hari urusan pemerintah nggak lagi begini:
buat akun baru.
Upload KTP lagi.
Isi nama lagi.
Masukkan alamat lagi.
Foto selfie lagi.
Datang kantor lagi.
Layanan A sudah tahu identitas yang sama seperti layanan B.
Warga cukup membuktikan: “ini gue.”
Lalu sistem mengambil data yang memang dibutuhkan.
Itu janji identitas digital nasional.
Indonesia sedang membangun ke arah sana.
Pada Mei 2026, Kementerian PANRB menyebut Identitas Kependudukan Digital atau IKD sebagai salah satu fondasi identitas digital nasional dalam ekosistem Digital Public Infrastructure.
Per 19 Mei 2026, pengguna IKD yang telah melakukan aktivasi disebut mencapai 19,35 juta orang, dengan target awal penguatan menuju sekitar 50 juta pengguna.
Pemerintah juga mengembangkan onboarding digital berbasis face recognition dan liveness detection.
Di ekosistem yang sama ada pertukaran data pemerintah, pembayaran digital, dan portal INAku untuk integrasi layanan publik.
Potensinya besar.
Tapi semakin identitas digital menjadi kunci banyak layanan, satu pertanyaan menjadi semakin penting:
siapa yang menjaga datanya?
Identitas digital adalah infrastructure, bukan aplikasi biasa
Kalau aplikasi resep makanan down, annoyance.
Kalau digital identity down, banyak layanan bisa berhenti.
Kalau akun streaming dibajak, kerugiannya terbatas.
Kalau identitas digital dibajak, attacker bisa impersonate.
Risk profile beda.
Maka digital identity harus diperlakukan seperti critical public infrastructure.
Security.
Availability.
Recovery.
Audit.
Governance.
Bukan hanya UX bagus.
Convenience harus dibangun di atas trust.
Single sign-on mengurangi friksi, tapi juga concentration risk
Satu identitas untuk banyak layanan sangat convenient.
Tidak perlu password 20.
Tidak perlu upload KTP berulang.
Bagus.
Tapi jika credential utama compromised, blast radius lebih besar.
Attacker mungkin mendapat akses ke banyak service.
Jadi authentication harus kuat.
Multi-factor.
Device binding maybe.
Risk-based authentication.
Session management.
Suspicious login detection.
Recovery process.
User perlu tahu kalau ada login aneh.
Digital identity tanpa strong recovery berbahaya.
Karena password lupa adalah hal normal.
NIK tidak boleh menjadi password
Indonesia historically menggunakan NIK di banyak proses.
Tapi identifier bukan secret.
NIK bisa muncul di dokumen.
Form.
Data breach.
Jangan jadikan nomor identitas sebagai authentication factor.
Identity = siapa user.
Authentication = bukti bahwa yang datang benar user itu.
Different.
IKD dan digital identity architecture harus menjaga distinction.
Biometric bisa membantu.
Device key.
PIN.
Cryptographic credential.
Layer.
Jangan satu data statis.
Face recognition juga punya risk
Pemerintah menargetkan onboarding IKD lebih luas menggunakan face recognition dan liveness detection.
Ini bisa mengurangi kebutuhan datang ke kantor.
Great.
Tapi biometric sensitive.
Wajah tidak bisa diganti kalau bocor.
System perlu: anti-spoof, accuracy, fairness, secure template, minimal retention.
Jangan simpan selfie mentah kalau tidak perlu.
Kalau matching dilakukan ke data Dukcapil, access harus controlled.
Who queries?
Log.
Purpose.
High security.
Biometric convenience must not create new database risk.
Data minimization tetap berlaku
Digital identity yang baik tidak selalu mengirim full profile.
Untuk beli tiket dengan diskon warga tertentu, mungkin layanan hanya perlu tahu: eligible atau tidak.
Tidak perlu NIK.
Alamat.
Tanggal lahir lengkap.
Konsep verifiable credential memungkinkan user membuktikan attribute tanpa membagikan seluruh identitas.
Kementerian PANRB pada Mei 2026 menyebut INAku dikembangkan dengan dukungan verifiable credential.
Ini direction penting.
Identity should reveal minimum necessary.
“18+.”
“Resident.”
“Eligible.”
Bukan dump database.
Semakin banyak service menarik full data, semakin besar privacy risk.
Data exchange harus purpose-based.
DPI Indonesia juga mengembangkan pertukaran data antarinstansi.
Pemerintah pada 2026 menyebut sistem penghubung layanan telah menghubungkan ratusan instansi.
Integrasi bagus.
Tapi jangan artikan: semua instansi boleh lihat semua data.
Interoperability bukan open access.
Need: purpose. authorization. data owner. audit log.
Instansi A hanya dapat field yang dibutuhkan.
Time-limited.
Role-based.
Every query logged.
Citizen maybe can see access history.
“Siapa mengakses data saya?”
This could build trust.
Data sharing invisible creates fear.
Transparency helps.
Digitalisasi bansos menunjukkan manfaat nyata
Pada Mei 2026, pemerintah memperluas pilot digitalisasi bansos ke 42 kabupaten/kota.
Ekosistemnya menghubungkan data lintas instansi, dengan Kemendagri memperkuat identitas kependudukan digital, Komdigi memfasilitasi pertukaran data, BSSN menjaga keamanan, dan pemilik data sektoral menyediakan data pendukung.
Tujuannya: verifikasi lebih cepat, transparan, tepat sasaran.
Ini contoh nilai digital identity.
Warga tidak harus membuktikan dirinya berulang.
System can verify.
But bansos also high impact.
If identity or data wrong, someone can miss benefit.
So correction mechanism critical.
Digital identity must allow: this is me, but data about me is wrong.
Authentication and data accuracy are different.
Jangan campur.
Siapa data owner?
Dukcapil punya data kependudukan.
Health agency punya health.
Tax punya tax.
Digital identity layer seharusnya tidak otomatis menjadi owner semua.
Federated governance.
Data stays with authoritative source.
Identity helps connect.
This reduces superdatabase temptation.
Centralizing all data into one giant lake can increase risk.
Interoperability can happen without full centralization.
Indonesia needs clear architecture.
Who controls what.
Who can revoke.
Who audits.
BSSN punya peran security, tapi security bukan satu lembaga
Dalam digitalisasi bansos 2026, pemerintah menyebut BSSN menjaga keamanan data.
Bagus.
Tapi security daily tetap tanggung jawab setiap operator.
Ministry.
GovTech.
Vendor.
Cloud.
App.
Identity provider.
Supply chain.
No one agency can “guard all data.”
Defense in depth.
BSSN standard and oversight.
Operator implementation.
Audit.
Incident response.
Shared responsibility.
Privacy authority also matters
UU PDP already applies.
Indonesia sedang membangun enforcement infrastructure privacy.
Digital identity is exactly area where strong data protection matters.
Purpose limitation.
Access.
Correction.
Security.
Data subject rights.
Public sector should not assume state data exempt from privacy principle.
Government holds some of most sensitive data.
Higher responsibility.
Not lower.
Citizen needs recovery if phone lost
IKD on smartphone creates practical issue.
Phone hilang.
SIM swapped.
Device broken.
What happens?
Recovery should be secure but not impossible.
If recovery only requires easy personal data, attacker can hijack.
If too hard, citizen locked out services.
Need layered recovery.
In-person option.
Alternative credential.
Trusted device.
Cooling period for sensitive change.
This is product design.
Identity system security often fails at recovery, not login.
Social engineering attacks weakest link.
Account recovery is critical.
Citizen should be able to revoke device
Phone stolen.
Open another channel.
Revoke.
Session terminated.
Device removed.
Simple.
Digital identity needs emergency control.
Bank apps already have similar concept.
Government identity should too.
Don’t force citizen wait office hours if credential compromised.
Maybe hotline or portal.
Secure process.
Availability 24/7 for revocation.
Again, infrastructure mindset.
Vendor access must be limited
Government systems use contractor.
Cloud.
Integrator.
Support.
Do vendor engineers see identity data?
Need contract.
Least privilege.
Privileged access management.
Log.
Time-limited support account.
No shared admin.
Background checks where appropriate.
Exit.
When contract ends, access revoked.
Data returned/deleted.
Digital identity cannot rely on trust alone.
Technical controls.
Interoperability increases attack surface
More connected services, more entry points.
A weak agency could become gateway.
Zero trust.
Each request authenticated.
Service identity.
Mutual authentication.
Rate limit.
Anomaly.
Don’t assume government network safe.
Connection itself is risk.
This is cybersecurity 101.
DPI needs it.
Offline inclusion matters
19.35 million active IKD users is significant, but Indonesia has far more residents.
Not everyone has compatible smartphone.
Connectivity.
Literacy.
Disability.
Digital identity should not make physical identity useless overnight.
Alternative channel.
Assisted service.
Transition long.
Digital transformation should increase access.
Not create digital-only gate.
Kementerian PANRB repeatedly frames government digital as inclusive and citizen-centered.
Implementation must prove.
People who cannot use app still deserve service.
Digital identity must avoid function creep
Today: public service login.
Tomorrow: age verification.
Then: private shopping.
Then: social media.
Potential.
Every expansion needs legal basis and risk assessment.
Do not turn national ID into universal tracking key.
Sector-specific pseudonymous identifiers may be safer.
Purpose.
Consent where relevant.
Governance.
Function creep is easy because infrastructure already exists.
Strong institutions must say no when use not justified.
Audit log should be citizen-facing eventually
Imagine IKD app shows: “BPJS accessed identity status at 09:12 for service X.”
“Agency Y verified residency.”
This empowers citizens.
If access unknown: report.
Transparency becomes security sensor.
Millions of users can detect anomaly.
Not every access detail possible.
But high-level history valuable.
Banking shows transaction history.
Identity could show verification history.
This can build trust dramatically.
Data breach response must be planned
Question is not if attack attempted.
It will.
Need incident plan.
Credential revoke.
Notification.
Forensic.
Fallback.
If biometric template compromised, what then?
Cannot change face.
Architecture must avoid storing reusable raw biometric.
Use protected template.
System redesign.
Security before scale.
Target 50 million means threat surface increases.
Growth metric should be paired with security metric.
How many fraud?
Takeover?
Failed liveness?
Recovery time?
No growth-only dashboard.
Identity is trust product.
Who should guard the data?
Not one person.
Not one ministry.
Governance needs layers.
Dukcapil as authoritative identity source.
Digital government operator.
BSSN security.
Data protection oversight.
Sector data owners.
Auditor.
Vendor control.
Citizen rights.
This is ecosystem.
If responsibility vague, everyone says: “bukan sistem kami.”
Need RACI.
Incident owner.
Data owner.
System owner.
Identitas Digital Nasional Bisa Membantu Layanan Publik, Tapi Siapa yang Menjaga Datanya?
The answer should not be: “trust the system.”
Trust must be engineered.
Access control.
Minimal data.
Encryption.
Audit.
Citizen visibility.
Recovery.
Independent oversight.
Clear accountability.
Digital identity can eliminate repetitive bureaucracy and make public service dramatically easier.
But the same infrastructure can become dangerous if too much data concentrates around one credential without controls.
The more important the key, the stronger the lock must be.
Indonesia is building that key now.
Its success will depend not only on how many millions activate it.
But on whether citizens feel safe using it for the most important parts of their lives.
Bacaan terkait
Artikel ini berada dalam Digital Policy dan mengikuti metodologi editorial Undercover.id. Format terkait tersedia di Reports dan analisis mendalam.