Dampak: Host Pencadangan dan DR Google Cloud dihapus
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan jenis temuan ancaman di Security Command Center. Temuan ancaman dibuat oleh
pendeteksi ancaman saat mendeteksi
potensi ancaman di resource cloud Anda. Untuk daftar lengkap temuan ancaman yang tersedia, lihat Indeks temuan ancaman.
Ringkasan
Event Threat Detection memeriksa log audit untuk mendeteksi penghapusan host yang menjalankan aplikasi yang dilindungi oleh Layanan Backup dan DR. Setelah host dihapus,
aplikasi yang terkait dengan host tidak dapat dicadangkan.
Cara merespons
Untuk menanggapi temuan ini, lakukan hal berikut:
Langkah 1: Tinjau detail temuan
Buka temuan Impact: Deleted Google Cloud Backup and DR host
seperti yang dijelaskan dalam Meninjau temuan. Panel detail untuk temuan akan terbuka di tab Ringkasan.
Di tab Summary, tinjau informasi di bagian berikut:
Apa yang terdeteksi, terutama kolom berikut:
Nama aplikasi: nama database atau VM yang terhubung ke Backup and DR
Nama host: nama host yang terhubung ke Backup dan DR
Subjek utama: pengguna yang telah berhasil menjalankan tindakan
Resource yang terpengaruh
Nama tampilan resource: project tempat host dihapus
Link terkait, terutama kolom berikut:
Metode MITRE ATT&CK: link ke dokumentasi MITRE ATT&CK
URI Logging: link untuk membuka Logs Explorer
Langkah 2: Meneliti metode serangan dan respons
Hubungi pemilik akun layanan di kolom Principal email.
Konfirmasi apakah pemilik yang sah melakukan tindakan tersebut.
Langkah 3: Terapkan respons Anda
Rencana respons berikut mungkin sesuai untuk temuan ini, tetapi juga dapat memengaruhi operasi.
Evaluasi dengan cermat informasi yang Anda kumpulkan dalam penyelidikan untuk menentukan cara terbaik dalam menyelesaikan temuan.
Di project tempat tindakan dilakukan, buka konsol pengelolaan.
Pastikan host yang dihapus tidak lagi ada dalam daftar host Pencadangan dan DR.
Pilih opsi Tambahkan Host untuk menambahkan kembali host yang dihapus.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[],[],null,["| Premium and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThis document describes a threat finding type in Security Command Center. Threat findings are generated by\n[threat detectors](/security-command-center/docs/concepts-security-sources#threats) when they detect\na potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](/security-command-center/docs/threat-findings-index).\n\nOverview\n\nEvent Threat Detection examines audit logs to detect the deletion of hosts that are\nrunning applications protected by the Backup and DR Service. After a host is deleted,\napplications that are associated with the host cannot be backed up.\n\nHow to respond\n\nTo respond to this finding, do the following:\n\nStep 1: Review finding details\n\n1. Open the `Impact: Deleted Google Cloud Backup and DR host` finding, as detailed in [Reviewing findings](/security-command-center/docs/how-to-investigate-threats#reviewing_findings). The details panel for the finding opens to the **Summary** tab.\n2. On the **Summary** tab, review the information in the following sections:\n - **What was detected** , especially the following fields:\n - **Application name**: the name of a database or VM connected to Backup and DR\n - **Host name**: the name of a host connected to Backup and DR\n - **Principal subject**: a user that has successfully executed an action\n - **Affected resource**\n - **Resource display name**: the project in which the host was deleted\n - **Related links** , especially the following fields:\n - **MITRE ATTACK method**: link to the MITRE ATT\\&CK documentation\n - **Logging URI** : link to open the **Logs Explorer**\n\nStep 2: Research attack and response methods\n\nContact the owner of the service account in the **Principal email** field.\nConfirm whether the legitimate owner conducted the action.\n\nStep 3: Implement your response\n\n\nThe following response plan might be appropriate for this finding, but might also impact operations.\nCarefully evaluate the information you gather in your investigation to determine the best way to\nresolve findings.\n\n1. In the project where the action was taken, navigate to the management console.\n2. Confirm that the deleted host is no longer in the list of Backup and DR hosts.\n3. Select the **Add Host** option to re-add the deleted host.\n\nWhat's next\n\n- Learn [how to work with threat\n findings in Security Command Center](/security-command-center/docs/how-to-investigate-threats).\n- Refer to the [Threat findings index](/security-command-center/docs/threat-findings-index).\n- Learn how to [review a\n finding](/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.\n- Learn about the [services that\n generate threat findings](/security-command-center/docs/concepts-security-sources#threats)."]]
