Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Temuan dapat memiliki salah satu dari dua status: Active atau Inactive.
Saat temuan pertama kali dibuat, layanan deteksi bawaan menetapkan properti
state temuan ke Active. Secara umum, Anda dapat menganggap
Active berarti masalah keamanan yang mendasarinya masih ada; namun,
seperti yang dijelaskan di bagian ini, hal itu tidak selalu terjadi.
Status temuan dapat menjadi Inactive jika layanan deteksi tertentu mendeteksi bahwa masalah keamanan telah diperbaiki atau resource yang terpengaruh telah dihapus. Anda juga dapat mengubah statusnya secara manual menjadi Inactive. Secara umum, Inactive berarti masalah keamanan yang mendasarinya tidak
ada lagi; namun, seperti yang dijelaskan di bagian ini, hal itu tidak
selalu terjadi.
Kapan saja, state temuan mungkin tidak mencerminkan
status masalah keamanan yang terdeteksi saat ini. Daftar berikut menunjukkan beberapa alasan terjadinya ketidakcocokan:
Beberapa layanan deteksi tidak memperbarui temuan mereka secara otomatis setelah masalah yang terdeteksi diperbaiki.
Status temuan ancaman tidak pernah diubah secara otomatis.
Untuk layanan deteksi yang memperbarui temuan secara otomatis, biasanya ada jeda sebelum perbaikan terdeteksi dan temuan diperbarui.
Untuk beberapa layanan deteksi, status temuan dapat diubah secara manual ke status yang tidak sesuai dengan status masalah yang terdeteksi.
Hanya layanan deteksi kerentanan dan kesalahan konfigurasi berikut yang secara otomatis mengubah status temuan dari Active menjadi Inactive setelah mendeteksi bahwa masalah terkait telah diperbaiki:
Security Health Analytics, termasuk saat detektor di Security Health Analytics dinonaktifkan. Lihat Penonaktifan otomatis temuan untuk mengetahui informasi tentang semua peristiwa yang dapat menyebabkan Security Health Analytics mengubah status temuannya secara otomatis. + VM Manager
Mendowngrade ke tingkat Standard juga mengubah status temuan Premium atau Enterprise menjadi Inactive. Pelajari lebih lanjut Tingkatan layanan.
Untuk mengetahui informasi tentang cara mengubah status temuan secara manual di
Google Cloud konsol, lihat
Mengubah status temuan.
[[["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-08-19 UTC."],[],[],null,["# Finding states\n\n| Standard, Premium, and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nA finding can have one of two states: `Active` or `Inactive`.\n\nWhen a finding is first created, the built-in detection services set the\n`state` property of the finding to `Active`. Generally, you can consider\n`Active` to mean that the underlying security issue still exists; however,\nas explained later in this section, that is not always the case.\n\nThe state of a finding can become `Inactive` if certain detection services\ndetect that the security issue was remediated or that the affected resource\nwas deleted. You can also manually change the state to `Inactive`. Generally, `Inactive` means that the underlying security issue no\nlonger exists; however, as explained later in this section, that is\nnot always the case.\n\nAt any point in time, the `state` of a finding might not reflect the\ncurrent state of the detected security issue. The following list shows some\nof the reasons a mismatch might occur:\n\n- Some detection services do not update their findings automatically\n after the detected issue is remediated.\n\n The state of threat findings are never changed automatically.\n- For the detection services that do update their findings automatically,\n there is usually a delay before the remediation is detected and the finding\n is updated.\n\n- For some detection services, the state of a finding might be changed manually to a state that does\n not match the state of the detected issue.\n\nOnly the following vulnerability and misconfiguration detection services\nautomatically change the state of a finding from `Active` to `Inactive` upon\ndetecting that the corresponding issue is remediated:\n\n- Security Health Analytics, including when a detector in Security Health Analytics is disabled. See [Automatic deactivation of\n findings](/security-command-center/docs/how-to-remediate-security-health-analytics-findings#finding-deactivation) for information about all the events that might cause Security Health Analytics to automatically change the state of their finding. + VM Manager\n\nDowngrading to the Standard tier also changes the state of Premium or Enterprise\nfindings to `Inactive`. Learn more about [Service\ntiers](/security-command-center/docs/service-tiers).\n\nFor information about manually changing the state of a finding in the\nGoogle Cloud console, see\n[Changing the state of a finding](/security-command-center/docs/how-to-work-with-findings-in-the-dashboard#change_the_state_of_a_finding)."]]
