本文說明 Security Command Center Enterprise 層級的案件概念,以及如何處理案件。
總覽
在 Security Command Center 中,您可以透過案件取得發現項目的詳細資料、將應對手冊附加至發現項目快訊、套用自動威脅回應,以及追蹤安全問題的修復情況。
「發現項目」是偵測服務產生的安全性問題記錄。在案件中,調查結果和其他安全問題會以快訊形式呈現,並透過應對手冊收集額外資訊,Security Command Center 會盡可能將新快訊新增至現有案件,並與其他相關快訊歸類在一起。如要進一步瞭解案件,請參閱 Google SecOps 說明文件中的「案件總覽」。
發現項目流程
在 Security Command Center Enterprise 中,發現項目有兩種流程:
Security Command Center 威脅發現項目會經過安全資訊與事件管理 (SIEM) 模組。內部 SIEM 規則觸發後,調查結果會變成快訊。
[[["容易理解","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-08-19 (世界標準時間)。"],[],[],null,["# Cases overview\n\n| Enterprise [service tier](/security-command-center/docs/service-tiers)\n\nThis document covers the concepts of cases in the Enterprise tier of\nSecurity Command Center and explains how to work with them.\n\nOverview\n--------\n\nIn Security Command Center, you use cases to obtain details about findings, attach\nplaybooks to finding alerts, apply automatic threat responses, and track the\nremediation of security issues.\n\nA *finding* is a record of a security issue that is generated by one of the\n[detection\nservices](/security-command-center/docs/concepts-security-sources).\nIn a case, findings and other security issues are presented as alerts, which are\nenriched using a playbook that collects additional information. Whenever\npossible, Security Command Center adds new alerts to existing cases, where they are\ngrouped with other related alerts.\nFor more details about cases, see [Case\noverview](/chronicle/docs/soar/investigate/working-with-cases/cases-overview) in\nthe Google SecOps documentation.\n\nFindings flow\n-------------\n\nIn Security Command Center Enterprise, there are two flows for findings:\n\n1. Security Command Center threat findings go through the security information and\n event management (SIEM) module. After triggering the internal SIEM rules,\n findings turn into alerts.\n\n The connector collects the alerts and ingests them into the security\n orchestration, automation, and response (SOAR) module where the playbooks\n process and enrich the alerts that are grouped into cases.\n2. Toxic combination findings and any related vulnerability and\n misconfiguration findings go directly to the SOAR module. After the **SCC\n Enterprise - Urgent Posture Findings Connector** ingests and groups the\n findings as alerts into cases, the playbooks process and enrich alerts.\n\nIn Security Command Center Enterprise, the Security Command Center finding becomes a *case\nalert*.\n\nInvestigate cases\n-----------------\n\nDuring ingestion, findings are grouped into cases to let the security\nspecialists know what to triage.\n\nMultiple findings with the same parameters are grouped into one case. To learn\nmore about the finding grouping mechanism, see [Group findings in cases](/security-command-center/docs/group-findings-in-cases). If you are using a ticketing system,\nsuch as Jira or ServiceNow, a ticket is created based on a case, meaning that\nthere is one ticket for all findings in a case.\n\n### Finding status\n\nA finding can possess any of the following statuses:\n\n- **Active**: The finding is active.\n\n- **Muted** : The finding is active and muted. If all findings in a case are\n muted, the case is closed. To learn more about muting findings in cases, see\n [Mute findings in cases](/security-command-center/docs/mute-findings-in-cases).\n\n- **Closed**: The finding is inactive.\n\nThe finding status is displayed in the **Finding state** widget of the **Case\noverview** tab and the **Finding Summary** widget of an alert.\n\nIf you [integrate with ticketing\nsystems](/security-command-center/docs/integrate-ticketing-systems), enable synchronization\njobs to keep the information about findings and their statuses up to date\nautomatically and synchronize case data with relevant tickets. To learn more\nabout case data synchronization, see [Enable case data synchronization](/security-command-center/docs/synchronize-case-data).\n\n### Finding severity versus case priority\n\nBy default, all findings contained in a case possess the same `severity`\n[property](/security-command-center/docs/finding-severity-classifications). You can\n[configure the grouping\nsettings](/security-command-center/docs/group-findings-in-cases#configure-settings) to\ninclude findings with different severities into one case.\n\nCase priority is based on the highest finding severity. When the finding\nseverity changes, Security Command Center automatically updates the case priority to\nmatch the highest severity property among all findings in a case. Muting\nfindings has no impact on the case priority---if a muted finding possesses\nthe highest severity, it defines the priority of the case.\n\nIn the following example, the priority for Case 1 is Critical because the\nseverity of Finding 3 (though muted) is set to Critical:\n\n- Case 1: Priority: `CRITICAL`\n - Finding 1, active. Severity: `HIGH`\n - Finding 2, active. Severity: `HIGH`\n - Finding 3, muted. Severity: `CRITICAL`\n\nIn the next example, the priority for Case 2 is High because the highest\nseverity for all the findings is High:\n\n- Case 2: Priority: `HIGH`\n - Finding 1, active. Severity: `HIGH`\n - Finding 2, active. Severity: `HIGH`\n - Finding 3, muted. Severity: `HIGH`\n\n### Review cases\n\nTo review a case, take the following steps:\n\n1. In the Google Cloud console, go to **Risk \\\u003e Cases** . The **Cases list** opens.\n2. Select a case to review. The **Case View** opens, where you can find a finding summary along with all information about an alert or the collection of alerts grouped into a selected case.\n3. Check the **Case Wall** tab for details about the activity performed on the case and included alerts.\n4. Go to the **Alert** tab to get an overview of a finding.\n\n The **Alert** tab contains the following information:\n - List of alert events.\n - Playbooks attached to the alert.\n - A finding overview.\n - Information about the impacted asset.\n - Optional: ticket details.\n\nIntegrate with ticketing systems\n--------------------------------\n\nBy default, no ticketing system is integrated with Security Command Center\nEnterprise.\n\nCases containing vulnerability and misconfiguration findings have related\ntickets only when you integrate and configure the ticketing system. If you\n[integrate a ticketing system](/security-command-center/docs/integrate-ticketing-systems),\nSecurity Command Center Enterprise creates tickets based on posture cases and\nforwards all information collected by playbooks to the ticketing system using\nthe synchronization job.\n\nBy default, cases containing threat findings have no related tickets even when\nyou integrate the ticketing system with your Security Command Center Enterprise\ninstance. To use tickets for your threat cases, customize available playbooks by\n[adding an action](/chronicle/docs/soar/respond/working-with-playbooks/using-actions-in-playbooks#adding-an-action)\nor create new playbooks.\n\n### Case assignee versus ticket assignee\n\nEvery finding has a single resource owner at any given time. The resource owner\nis defined using Google Cloud tags, Essential Contacts, or the\n**Fallback Owner** parameter value configured in the **SCC Enterprise - Urgent\nPosture Findings Connector**.\n\nIf you integrate a ticketing system, the resource owner is the ticket assignee\nby default. To learn more about automatic and manual ticket assignment, refer to\n[Assign tickets based on posture cases](/security-command-center/docs/assign-itsm-tickets).\n\nThe *ticket assignee* works with findings to remediate them.\n\nThe *case assignee* works with cases in Security Command Center Enterprise and\ndoesn't triage or mitigate findings.\n\nFor example, a case assignee can be a Threat Manager or other Security\nSpecialist who collaborates with an engineer (ticket assignee) and verifies that\nall alerts in a case are addressed. The case assignee never works with ticketing\nsystems.\n\nWhat's next\n-----------\n\nTo learn more about cases, refer to the following resources in the\nGoogle SecOps documentation:\n\n- [Cases overview tab](/chronicle/docs/soar/investigate/working-with-cases/whats-on-the-case-overview-tab)\n- [What's on the Cases page?](/chronicle/docs/soar/investigate/working-with-cases/whats-on-the-cases-screen)\n- [How to perform a manual action on a case](/chronicle/docs/soar/investigate/working-with-cases/perform-a-manual-action)\n- [How to simulate cases](/chronicle/docs/soar/investigate/working-with-cases/simulate-cases)\n- [Work with playbook blocks](/chronicle/docs/soar/respond/working-with-playbooks/working-with-playbook-blocks)"]]