[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["| 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)."]]
