Centralized identity governance, policy lifecycle management, dan automation memastikan akses di seluruh organisasi terkontrol dan compliant

Setelah di episode 20 kita membahas compliance & audit, pada episode ini kita masuk ke Identity Governance Administration (IGA) — disiplin yang mengelola kebijakan akses secara terpusat di seluruh organisasi. IGA menghubungkan business needs dengan technical controls.
Mengapa IGA penting? Karena tanpa governance terpusat, setiap departemen mengelola akses dengan cara sendiri — menghasilkan inkonsistensi, over-privileged access, dan compliance gap. IGA membawa standarisasi.
| Fase | Aktivitas |
|---|---|
| Design | Buat kebijakan berdasarkan business needs |
| Implementation | Deploy ke systems |
| Monitoring | Enforce dan audit compliance |
| Review | Evaluate effectiveness |
| Update | Modify berdasarkan temuan |
SoD Rules:
1. User tidak boleh memiliki: "requester" DAN "approver"
2. User tidak boleh memiliki: "developer" DAN "deployer" ke production
3. User tidak boleh memiliki: "finance-create" DAN "finance-approve"| Fitur | Fungsi |
|---|---|
| Access request | Self-service access request workflow |
| Access certification | Periodic review and certification |
| Role management | Role mining, optimization, lifecycle |
| Policy enforcement | Automated policy compliance |
| Audit reporting | Comprehensive audit trails |
| Platform | Tipe | Fitur Utama |
|---|---|---|
| SailPoint | Commercial | Enterprise IGA leader |
| Saviynt | Cloud-native | Cloud IGA |
| One Identity | Commercial | Hybrid IGA |
| Keycloak + custom | Open-source | Basic governance |
def evaluate_access(user, access, policy):
# Check SoD
if has_conflicting_access(user, access):
return {'decision': 'deny', 'reason': 'SoD violation'}
# Check least privilege
if not is_least_privilege(user, access):
return {'decision': 'require_approval', 'reason': 'Excessive access'}
# Check compliance
if not meets_compliance(access, policy):
return {'decision': 'deny', 'reason': 'Compliance violation'}
return {'decision': 'approve'}Role mining menganalisis akses yang ada untuk menemukan role optimal:
Current: 500 users, 2000 role assignments, 150 unique permission combinations
Mining: Identify patterns → Suggest 25 standard roles
Result: Reduce from 150 ad-hoc roles to 25 managed rolesNote
IGA implementation membutuhkan waktu berbulan-bulan. Mulailah dengan access certification untuk application yang paling kritis, lalu expand ke governance penuh secara bertahap.
| Metric | Target | Frequency |
|---|---|---|
| Access review completion | 100% | Quarterly |
| Time to provision | <24 hours | Monthly |
| Time to deprovision | <4 hours | Monthly |
| SoD violations | 0 | Continuous |
| Orphan accounts | 0 | Monthly |
Inti yang harus dibawa pulang:
Di episode 22 selanjutnya kita akan membahas AI-assisted IAM — AI untuk access decisions, anomaly detection, dan intelligent provisioning. Siapkan AI untuk IAM kalian!