1. Pengenalan Security Audit
Security Audit adalah evaluasi sistematis dan terstruktur terhadap postur keamanan informasi suatu organisasi. Audit ini menilai sejauh mana kebijakan, prosedur, kontrol teknis, dan praktik keamanan organisasi sesuai dengan standar industri, regulasi, dan best practices. Security audit bukan sekadar "memindai kerentanan" β ini mencakup aspek people (manusia), process (proses), dan technology (teknologi).
Security audit berbeda dari penetration testing. Jika pentest berfokus pada eksploitasi teknis, security audit mencakup gambaran yang lebih luas: apakah kebijakan keamanan ada? Apakah karyawan sudah dilatih? Apakah ada prosedur backup yang teruji? Apakah akses diberikan berdasarkan least privilege? Audit memberikan gambaran komprehensif tentang kesiapan keamanan organisasi.
Jenis-Jenis Security Audit
| Jenis | Yang Diaudit | Dilakukan Oleh | Tujuan |
|---|---|---|---|
| Internal Audit | Kontrol keamanan internal organisasi | Tim internal (GRC/InfoSec) | Evaluasi mandiri, persiapan audit eksternal |
| External Audit | Kepatuhan terhadap standar/regulasi | Firma audit independen (KPMG, Deloitte, EY) | Sertifikasi, regulatory compliance |
| Compliance Audit | Kepatuhan terhadap regulasi spesifik | Auditor tersertifikasi | PCI-DSS, HIPAA, GDPR, POJK |
| Technical Audit | Konfigurasi sistem, infrastruktur, kode | Security engineer/consultant | Identifikasi kerentanan teknis |
| Social Engineering Audit | Kesadaran keamanan karyawan | Red team / consultant | Uji ketahanan terhadap phishing, pretexting |
| Supply Chain Audit | Keamanan vendor dan pihak ketiga | Tim vendor risk management | Evaluasi risiko dari pihak ketiga |
Siapa yang Membutuhkan Security Audit?
| Tipe Organisasi | Alasan Audit | Framework yang Umum |
|---|---|---|
| Perusahaan Finansial | Regulasi OJK/BI, perlindungan data nasabah | PCI-DSS, ISO 27001, POJK |
| E-commerce | Perlindungan data pembayaran pelanggan | PCI-DSS, SOC 2 |
| SaaS / Cloud Provider | Kepercayaan pelanggan, enterprise sales | SOC 2, ISO 27001, CSA STAR |
| Pemerintah | Regulasi keamanan informasi negara | ISO 27001, SNI, Peraturan BSSN |
| Healthcare | Perlindungan data pasien | HIPAA, ISO 27001 |
| Startup | Due diligence investor, customer trust | SOC 2, ISO 27001 |
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β SECURITY AUDIT ECOSYSTEM β β β β ββββββββββββ ββββββββββββββββ ββββββββββββββ β β β People β β Process β β Technology β β β β β β β β β β β β Training β β Policies β β Firewalls β β β β Awarenessβ β Procedures β β SIEM β β β β Roles β β Incident Planβ β Encryption β β β β Access β β Backup β β EDR β β β ββββββ¬ββββββ ββββββββ¬ββββββββ βββββββ¬βββββββ β β β β β β β βββββββββββββββββββΌβββββββββββββββββββ β β βΌ β β ββββββββββββββββββββ β β β SECURITY AUDIT β β β β & COMPLIANCE β β β ββββββββββ¬ββββββββββ β β βΌ β β βββββββββββββββββΌββββββββββββββββ β β βΌ βΌ βΌ β β βββββββββββ βββββββββββββ βββββββββββββββββ β β β ISO β β SOC 2 β β PCI-DSS β β β β 27001 β β β β β β β βββββββββββ βββββββββββββ βββββββββββββββββ β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2. Proses Audit Keamanan
Security audit yang profesional mengikuti proses yang terstruktur dan terdokumentasi. Berikut adalah tahapan umum yang dilakukan dalam security audit:
Tahapan Security Audit
| Fase | Aktivitas | Durasi | Output |
|---|---|---|---|
| 1. Planning & Scoping | Definisikan ruang lingkup, target, metode, timeline | 1-2 minggu | Audit plan, scope document |
| 2. Information Gathering | Kumpulkan dokumen kebijakan, arsitektur, asset inventory | 1 minggu | Asset register, policy documents |
| 3. Risk Assessment | Identifikasi aset, ancaman, kerentanan, dan dampak | 1-2 minggu | Risk register |
| 4. Control Evaluation | Uji efektivitas kontrol keamanan yang ada | 2-4 minggu | Control assessment results |
| 5. Technical Testing | Vulnerability assessment, config review, code review | 1-3 minggu | Technical findings |
| 6. Analysis & Reporting | Analisis temuan, buat rekomendasi, susun laporan | 1-2 minggu | Final audit report |
| 7. Remediation Follow-up | Pantau implementasi rekomendasi | Ongoing | Remediation tracker |
Audit Checklist β Control Areas
SECURITY AUDIT CONTROL ASSESSMENT CHECKLIST ============================================= 1. GOVERNANCE & POLICY β Information Security Policy β ada, up-to-date, disetujui manajemen β Security roles & responsibilities β terdefinisi dengan jelas β Risk management framework β proses identifikasi dan mitigasi risiko β Security awareness program β training karyawan rutin β Acceptable use policy β pedoman penggunaan aset IT β Data classification policy β klasifikasi data (public, internal, confidential) 2. ACCESS CONTROL β Principle of least privilege β akses minimal yang diperlukan β Multi-factor authentication (MFA) β aktif untuk akses kritis β Password policy β minimal 12 karakter, kompleksitas, rotasi β Account lifecycle management β provisioning & deprovisioning β Privileged access management (PAM) β akses admin terkontrol β Review akses berkala β quarterly access review β Separation of duties β tidak ada satu orang kontrol semua 3. NETWORK SECURITY β Firewall rules β reviewed, documented, least privilege β Network segmentation β isolasi segment kritis β Intrusion Detection/Prevention (IDS/IPS) β aktif dan dimonitor β VPN untuk remote access β enkripsi semua koneksi remote β Wireless security β WPA3, guest network terpisah β DNS security β DNSSEC, DNS filtering β DDoS protection β mitigation strategy 4. DATA PROTECTION β Encryption at rest β data sensitif dienkripsi di storage β Encryption in transit β TLS 1.2+ untuk semua komunikasi β Key management β prosedur generate, store, rotate keys β Data loss prevention (DLP) β monitor data exfiltration β Backup & recovery β 3-2-1 rule, tested restoration β Data retention & disposal β policy penghapusan data 5. ENDPOINT SECURITY β Endpoint Detection & Response (EDR) β deployed di semua endpoint β Patch management β OS dan aplikasi up-to-date β Anti-malware β terinstall dan terupdate β Device encryption β full disk encryption (BitLocker/FileVault) β Mobile device management (MDM) β kontrol perangkat mobile β USB/removable media control β pembatasan penggunaan 6. APPLICATION SECURITY β Secure SDLC β security di setiap tahap development β Code review β static analysis (SAST), dynamic analysis (DAST) β Dependency scanning β cek vulnerability di library/package β Input validation β semua input user divalidasi β Error handling β tidak ekspos informasi internal β API security β authentication, rate limiting, input validation 7. INCIDENT RESPONSE β IR plan β didokumentasikan, di-test, up-to-date β IR team β terbentuk dengan peran jelas β Communication plan β siapa yang dihubungi, kapan, bagaimana β Logging & monitoring β SIEM aktif, log di-retention minimal 1 tahun β Forensic readiness β tools dan prosedur siap β Tabletop exercise β dilakukan minimal 2x setahun 8. BUSINESS CONTINUITY β Business Continuity Plan (BCP) β didokumentasikan β Disaster Recovery Plan (DRP) β prosedur pemulihan β RTO/RPO β Recovery Time/Point Objective terdefinisi β Backup testing β restore test dilakukan berkala β Failover testing β test switching ke DR site
Risk Assessment Matrix
| Impact β / Likelihood β | Rendah | Sedang | Tinggi | Sangat Tinggi |
|---|---|---|---|---|
| Kritis | π Tinggi | π΄ Kritis | π΄ Kritis | π΄ Kritis |
| Tinggi | π‘ Sedang | π Tinggi | π΄ Kritis | π΄ Kritis |
| Sedang | π’ Rendah | π‘ Sedang | π Tinggi | π΄ Kritis |
| Rendah | π’ Rendah | π’ Rendah | π‘ Sedang | π Tinggi |
3. Vulnerability Assessment
Vulnerability Assessment adalah proses identifikasi, klasifikasi, dan prioritisasi kerentanan keamanan dalam sistem, jaringan, dan aplikasi. Berbeda dengan penetration testing yang mencoba mengeksploitasi, vulnerability assessment berfokus pada identifikasi dan pelaporan β memberikan gambaran lengkap tentang celah keamanan yang perlu ditutup.
Tahapan Vulnerability Assessment
# ============================================= # VULNERABILITY ASSESSMENT WORKFLOW # ============================================= # STEP 1: Asset Discovery β Temukan semua aset di jaringan nmap -sn 192.168.1.0/24 -oN network_discovery.txt # Hasil: daftar semua host aktif di jaringan # STEP 2: Port Scanning β Identifikasi service yang berjalan nmap -sV -sC -O -p- 192.168.1.0/24 -oA full_port_scan # Hasil: port terbuka, versi service, OS detection # STEP 3: Vulnerability Scanning dengan Nmap NSE nmap --script vuln 192.168.1.0/24 -oA vuln_scan # Scripts: vuln, exploit, auth, brute # STEP 4: Vulnerability Scanning dengan Nuclei # Install nuclei: go install -v github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest nuclei -l targets.txt -t cves/ -t vulnerabilities/ -t misconfiguration/ \ -severity critical,high,medium -o nuclei_results.txt # STEP 5: Web Application Scanning dengan Nikto nikto -h https://webapp.target.com -output nikto_report.html # Mengecek: outdated software, dangerous files, misconfigurations # STEP 6: SSL/TLS Assessment testssl.sh https://webapp.target.com # Cek: cipher suites, certificate validity, protocol support # STEP 7: Configuration Audit # CIS Benchmark β Automated dengan Lynis (Linux) sudo lynis audit system # Hasil: hardening suggestions berdasarkan CIS benchmarks # STEP 8: Dependency Scanning (Software Composition Analysis) # Untuk Node.js project: npm audit # Untuk Python: pip-audit # Untuk Java (Maven): dependency-check --project "MyApp" --scan ./src # STEP 9: Container Security Scanning trivy image myapp:latest grype myapp:latest # Scan Docker image untuk known vulnerabilities # STEP 10: Cloud Security Posture # AWS: prowler aws --compliance cis_2.0 # Azure: az ad sp create-for-rbac --name security-audit # Multi-cloud: ScoutSuite scout aws # atau scout azure, scout gcp
Vulnerability Severity Rating β CVSS
CVSS (Common Vulnerability Scoring System) adalah standar industri untuk menilai keparahan kerentanan. Skor berkisar dari 0.0 hingga 10.0.
| CVSS Score | Severity | Warna | Response Time | Contoh |
|---|---|---|---|---|
| 9.0 - 10.0 | Critical | π΄ | 24 jam | Log4Shell (CVE-2021-44228), EternalBlue |
| 7.0 - 8.9 | High | π | 7 hari | SQL Injection, RCE tanpa autentikasi |
| 4.0 - 6.9 | Medium | π‘ | 30 hari | XSS, CSRF, information disclosure |
| 0.1 - 3.9 | Low | π’ | 90 hari | Missing headers, verbose errors |
| 0.0 | None | βͺ | Best practice | Informational findings |
Vulnerability Assessment bertujuan menemukan sebanyak mungkin kerentanan β breadth over depth. Penetration Testing bertujuan membuktikan dampak eksploitasi β depth over breadth. Keduanya saling melengkapi: vulnerability assessment sebagai rutin (bulanan/quarterly), penetration testing sebagai deep-dive (tahunan atau setelah perubahan signifikan).
4. Compliance Frameworks
Compliance berarti memenuhi persyaratan yang ditetapkan oleh standar, regulasi, atau kerangka kerja keamanan tertentu. Berbagai industri dan negara memiliki regulasi yang berbeda-beda, tetapi banyak yang saling tumpang tindih. Memahami framework ini sangat penting agar organisasi tidak hanya aman secara teknis, tetapi juga memenuhi kewajiban hukum dan regulasi.
ISO/IEC 27001
| Aspek | Detail |
|---|---|
| Apa itu | Standar internasional untuk Information Security Management System (ISMS) |
| Tujuan | Menyediakan kerangka kerja sistematis untuk mengelola risiko keamanan informasi |
| Cakupan | 114 kontrol keamanan dalam Annex A, mencakup people, process, technology |
| Proses Sertifikasi | Gap analysis β Implementasi β Stage 1 Audit β Stage 2 Audit β Sertifikasi |
| Berlaku untuk | Semua jenis dan ukuran organisasi |
| Masa berlaku | 3 tahun dengan surveillance audit tahunan |
| Diakui oleh | Global β standar ISMS paling diakui di dunia |
Perbandingan Framework Compliance
| Framework | Industri | Sifat | Fokus Utama | Kontrol |
|---|---|---|---|---|
| ISO 27001 | Semua | Sukarela (standar) | ISMS β manajemen keamanan | 114 kontrol Annex A |
| SOC 2 Type II | Service providers / SaaS | Sukarela (audit) | 5 Trust Service Criteria | Custom controls |
| PCI-DSS v4.0 | Pembayaran kartu | Wajib | Protect cardholder data | ~300+ requirements |
| HIPAA | Healthcare (US) | Wajib | Protect health information (PHI) | Administrative, physical, technical |
| GDPR | Yang memproses data warga EU | Wajib | Data privacy & protection | Privacy by design, rights |
| NIST CSF | Semua (US) | Sukarela | Cybersecurity framework | 5 functions: ID, PR, DE, RS, RC |
| CIS Controls v8 | Semua | Sukarela | Prioritized security controls | 18 control groups |
ISO 27001 Implementation Roadmap
ISO 27001 IMPLEMENTATION ROADMAP ================================== PHASE 1: PREPARATION (Bulan 1-2) βββββββββββββββββββββββββββββββββ β Dapatkan commitment manajemen (top management support) β Tentukan scope ISMS β unit bisnis mana yang dicakup β Bentuk tim implementasi ISMS β Gap analysis β bandingkan kondisi saat ini dengan ISO 27001 β Buat project plan dengan timeline dan milestone PHASE 2: RISK ASSESSMENT (Bulan 2-4) ββββββββββββββββββββββββββββββββββββ β Buat asset inventory β identifikasi semua aset informasi β Identifikasi ancaman dan kerentanan untuk setiap aset β Hitung risiko: Risk = Likelihood Γ Impact β Tentukan risk treatment plan: mitigate, accept, transfer, avoid β Buat Statement of Applicability (SoA) β kontrol mana yang diterapkan PHASE 3: IMPLEMENTATION (Bulan 4-8) ββββββββββββββββββββββββββββββββββ β Kembangkan kebijakan keamanan informasi β Implementasikan kontrol dari Annex A yang dipilih: - A.5: Organizational controls (policies, roles, segregation) - A.6: People controls (training, screening, NDAs) - A.7: Physical controls (physical security, equipment) - A.8: Technology controls (access control, crypto, logging) β Bangun awareness program untuk semua karyawan β Implementasikan incident management process β Setup monitoring, logging, dan internal audit process PHASE 4: INTERNAL AUDIT & REVIEW (Bulan 8-10) ββββββββββββββββββββββββββββββββββββββββββββββ β Lakukan internal audit β apakah kontrol berjalan efektif? β Management review β evaluasi efektivitas ISMS β Perbaiki temuan dari internal audit (corrective actions) β Pastikan semua dokumentasi lengkap dan up-to-date PHASE 5: CERTIFICATION AUDIT (Bulan 10-12) ββββββββββββββββββββββββββββββββββββββββββ β Pilih certification body (accredited registrar) β Stage 1 Audit (Documentation Review): - Auditor meninjau dokumentasi ISMS - Identifikasi area yang perlu perbaikan β Stage 2 Audit (Implementation Audit): - Auditor memverifikasi implementasi di lapangan - Wawancara karyawan, cek evidence - Temukan ketidaksesuaian (non-conformities) β Corrective actions untuk temuan auditor β Sertifikasi diterbitkan! π PHASE 6: CONTINUOUS IMPROVEMENT (Ongoing) ββββββββββββββββββββββββββββββββββββββββ β Surveillance audit tahunan (setiap 12 bulan) β Perbaikan berkelanjutan (PDCA cycle) β Re-certification audit di tahun ke-3 β Update ISMS sesuai perubahan bisnis dan ancaman
SOC 2 β 5 Trust Service Criteria
| Kriteria | Deskripsi | Contoh Kontrol |
|---|---|---|
| π Security | Sistem dilindungi dari akses tidak sah | Firewall, MFA, encryption, security monitoring |
| β‘ Availability | Sistem tersedia untuk dioperasikan | Uptime SLA, DDoS protection, DR plan, monitoring |
| π Processing Integrity | Processing data lengkap, valid, dan akurat | Input validation, error handling, QA testing |
| π Confidentiality | Data rahasia dilindungi sesuai komitmen | Encryption, access control, data classification |
| π Privacy | Data pribadi ditangani sesuai kebijakan privasi | Consent management, data retention, deletion policy |
5. Reporting & Remediation
Laporan audit yang baik adalah jembatan antara temuan teknis dan aksi perbaikan. Tanpa laporan yang jelas dan actionable, temuan audit hanya menjadi "kertas kosong" yang tidak menghasilkan perubahan. Laporan harus bisa dipahami oleh berbagai audiens: dari tim teknis yang akan melakukan perbaikan, hingga manajemen C-level yang perlu membuat keputusan strategis.
Struktur Laporan Security Audit
LAPORAN SECURITY AUDIT
=======================
BAGIAN 1: EXECUTIVE SUMMARY (Untuk Manajemen C-Level)
βββββββββββββββββββββββββββββββββββββββββββββββββββββ
Ringkasan Eksekutif:
- Total area yang diaudit: 8 kontrol domain
- Total temuan: 47 finding
- Status keseluruhan: PERLU PERBAIKAN SIGNIFIKAN
Temuan per Severity:
π΄ Critical: 3 (harus diselesaikan dalam 30 hari)
π High: 8 (harus diselesaikan dalam 60 hari)
π‘ Medium: 15 (harus diselesaikan dalam 90 hari)
π’ Low: 12 (rekomendasi perbaikan)
βͺ Info: 9 (observasi dan best practices)
Top 3 Risiko:
1. [CRITICAL] Tidak ada MFA untuk akses VPN β risiko credential theft
2. [CRITICAL] Backup tidak pernah di-test β risiko data loss
3. [HIGH] Tidak ada security awareness training β risiko phishing success
BAGIAN 2: SCOPE & METHODOLOGY
ββββββββββββββββββββββββββββββ
- Ruang lingkup: Divisi IT, infrastruktur jaringan, aplikasi web
- Framework acuan: ISO 27001:2022 Annex A, CIS Controls v8
- Metode: Document review, interview, technical testing, configuration audit
- Tanggal audit: 1-15 Juli 2026
- Auditor: Tim Security BeebaneLabs
BAGIAN 3: DETAILED FINDINGS
ββββββββββββββββββββββββββ
Finding #001: Tidak Ada Multi-Factor Authentication (MFA) pada VPN
Severity : CRITICAL
Control : A.8.5 β Secure Authentication
Status : NON-COMPLIANT
Deskripsi:
Saat ini, akses VPN ke jaringan perusahaan hanya menggunakan
username dan password. Tidak ada faktor autentikasi kedua.
Evidence:
- Screenshot konfigurasi VPN (FortiGate) β MFA tidak aktif
- Interview dengan IT Manager β mengkonfirmasi belum ada MFA
- Log VPN menunjukkan 100% login hanya password-based
Risiko:
Jika credential karyawan bocor (phishing, credential stuffing),
attacker bisa langsung masuk ke jaringan internal perusahaan.
Rekomendasi:
1. Implementasikan MFA untuk semua akses VPN (prioritas: admin)
2. Gunakan authenticator app (Google Authenticator, Microsoft Auth)
3. Hindari SMS-based MFA (vulnerable ke SIM swapping)
4. Target: selesai dalam 30 hari
Finding #002: Backup Tidak Pernah Di-test Restore
Severity : CRITICAL
Control : A.8.13 β Information Backup
Status : NON-COMPLIANT
... (dst)
BAGIAN 4: COMPLIANCE GAP ANALYSIS
ββββββββββββββββββββββββββββββββ
ββββββββββββββββββ¬βββββββββββββ¬ββββββββββββ¬ββββββββββββ
β ISO 27001 Ctrl β Descriptionβ Status β Gap β
ββββββββββββββββββΌβββββββββββββΌββββββββββββΌββββββββββββ€
β A.5.1 β Policies β β
Comply β - β
β A.5.23 β Cloud β β οΈ Partialβ Missing β
β A.8.5 β MFA β β Gap β No MFA β
β A.8.13 β Backup β β Gap β Untested β
ββββββββββββββββββ΄βββββββββββββ΄ββββββββββββ΄ββββββββββββ
BAGIAN 5: REMEDIATION ROADMAP
βββββββββββββββββββββββββββββ
ββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββββ
β Timeline β Actions β
ββββββββββββββΌβββββββββββββββββββββββββββββββββββββββββ€
β 30 hari β Implement MFA, Test backup, Patch CVSS β
β β β₯9.0 vulnerabilities β
β 60 hari β Implement SIEM, Security awareness β
β β training, Network segmentation β
β 90 hari β Update all policies, Implement PAM, β
β β DLP deployment, Code review process β
ββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββββ
Remediation Tracking
REMEDIATION TRACKER =================== βββββββ¬βββββββββββββββββ¬βββββββββββ¬βββββββββ¬ββββββββββββ¬βββββββββββ¬ββββββββββββ β ID β Finding β Severity β Owner β Deadline β Status β Evidence β βββββββΌβββββββββββββββββΌβββββββββββΌβββββββββΌββββββββββββΌβββββββββββΌββββββββββββ€ β R01 β VPN MFA β Critical β IT Ops β 30 Jul β π‘ In β Ticket β β β β β β β Progress β #1234 β βββββββΌβββββββββββββββββΌβββββββββββΌβββββββββΌββββββββββββΌβββββββββββΌββββββββββββ€ β R02 β Backup Testing β Critical β DBA β 30 Jul β π΄ Not β - β β β β β β β Started β β βββββββΌβββββββββββββββββΌβββββββββββΌβββββββββΌββββββββββββΌβββββββββββΌββββββββββββ€ β R03 β Security β High β HR + β 15 Aug β π‘ In β LMS β β β Training β β InfoSecβ β Progress β setup β βββββββΌβββββββββββββββββΌβββββββββββΌβββββββββΌββββββββββββΌβββββββββββΌββββββββββββ€ β R04 β SIEM Deploy β High β SOC β 30 Aug β π΄ Not β - β β β β β β β Started β β βββββββΌβββββββββββββββββΌβββββββββββΌβββββββββΌββββββββββββΌβββββββββββΌββββββββββββ€ β R05 β Patch MS17-010 β Critical β IT Ops β 30 Jul β β Done β Scan β β β β β β β β report β βββββββ΄βββββββββββββββββ΄βββββββββββ΄βββββββββ΄ββββββββββββ΄βββββββββββ΄ββββββββββββ Status Legend: π΄ Not Started β Belum ada aksi π‘ In Progress β Sedang dikerjakan π’ Done β Selesai, menunggu verifikasi β Verified β Sudah di-verify oleh auditor β« Accepted β Risiko diterima oleh manajemen (dengan dokumentasi)
- Audit tanpa follow-up β Temuan tidak ditindaklanjuti, hanya jadi "kertas"
- Compliance β Security β Bisa compliant tapi tetap tidak aman (check-box mentality)
- Tidak ada accountability β Tidak jelas siapa yang bertanggung jawab atas remediation
- Scope terlalu sempit β Tidak mencakup cloud, remote workers, atau supply chain
- Audit hanya setahun sekali β Keamanan harus continuous, bukan point-in-time
- Mengabaikan temuan "low" β Banyak low findings yang bisa menjadi attack chain
- Open Source: Open-AudIT, Faraday, DefectDojo, ArcherySec
- Commercial: ServiceNow GRC, OneTrust, LogicGate, Drata, Vanta
- Free/Premium: SecurityScorecard (free tier), UpGuard
- Cloud-native: AWS Security Hub, Azure Security Center, GCP Security Command Center
6. Quiz: Uji Pemahamanmu!
Setelah membaca tutorial di atas, jawablah 5 pertanyaan berikut untuk menguji pemahamanmu tentang Security Audit & Compliance: