[[["容易理解","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,["| 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\n\nIf you share your Google Workspace logs with Cloud Logging,\nEvent Threat Detection generates findings for several Google Workspace\nthreats. Because Google Workspace logs are at the organization level,\nEvent Threat Detection can only scan them if you activate Security Command Center\nat the organization level.\n\n\nEvent Threat Detection enriches log events and writes findings to\nSecurity Command Center. The following table describes a Google Workspace\nthreat finding type, the [MITRE ATT\\&CK framework](https://attack.mitre.org/)\nentry related to this finding, and details about the\nevents that trigger this finding. You can also check logs using specific filters,\nand combine all of the information that you gather to respond to this finding.\n\n\u003cbr /\u003e\n\nThis finding isn't available if you activate Security Command Center at the project\nlevel.\n\n| Description | Actions ||\n|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2-step verification was disabled for the organization. | 2-step verification is no longer required for your organization. Find out if this was an intentional policy change by an administrator, or if this is an attempt by an adversary to make account hijacking easier. | **Check logs using the following filters:** `protopayload.resource.labels.service=\"admin.googleapis.com\"` `logName=\"organizations/`\u003cvar class=\"edit\" translate=\"no\"\u003eORGANIZATION_ID\u003c/var\u003e`/logs/cloudaudit.googleapis.com%2Factivity` Replace `ORGANIZATION_ID` with your organization ID. |\n| 2-step verification was disabled for the organization. | 2-step verification is no longer required for your organization. Find out if this was an intentional policy change by an administrator, or if this is an attempt by an adversary to make account hijacking easier. | **Research events that trigger this finding:** - **MITRE:** \u003chttps://attack.mitre.org/techniques/T1556/\u003e - **Workspace event details:** \u003chttps://developers.google.com/admin-sdk/reports/v1/appendix/activity/admin-security-settings#ENFORCE_STRONG_AUTHENTICATION\u003e |\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)."]]
