[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-05。"],[],[],null,["| Standard, Premium, and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThis page explains the finding classes that the Security Command Center\nservices use to report security issues in your environment.\n\nIn finding definitions, the finding class is stored in the `findingClass`\nfield. For more information about the `findingClass` field, see\n[`FindingClass`](/security-command-center/docs/reference/rest/v2/organizations.sources.findings#findingclass).\n\nSome findings don't include a finding class definition. Security Command Center\nclassifies these findings as `Finding class unspecified`.\n\nThe classes include the following:\n\n- [`Chokepoint`](#chokepoint)\n- [`Misconfiguration`](#misconfiguration)\n- [`Observation`](#observation)\n- [`Posture violation`](#posture-violation)\n- [`SCC Error`](#scc-error)\n- [`Threat`](#threat)\n- [`Toxic combination`](#toxic-combination)\n- [`Vulnerability`](#vulnerability)\n- [`Finding class unspecified`](#finding-unspecified)\n\n`Chokepoint` class\n\nFindings in the `Chokepoint` class identify a resource or resource group where high-risk attack paths converge, based on attack path simulations.\n\nRemediating a chokepoint finding might remediate multiple toxic combinations.\n\nFor more information about `Chokepoint` class findings, see [Toxic combinations and chokepoints overview](/security-command-center/docs/toxic-combinations-overview).\n\n`Misconfiguration` class\n\nFindings in the `Misconfiguration` class identify vulnerabilities caused by\nthe incorrect or suboptimal configuration of programs, assets, or other\nresources. In most cases, you can fix\nthe problem by updating the configuration that is indicated in the findings.\n\nMisconfigurations are a type of vulnerability. Most `Misconfiguration` findings\nfrom the built-in Security Command Center services are documented in\n[Vulnerability findings](/security-command-center/docs/concepts-vulnerabilities-findings).\n\n`Observation` class\n\n\nFindings in the `Observation` class describe an event, configuration\ndetail, or other issue in your environment that might not be a problem\nin itself, but could be if your environment were to be compromised.\n\nSecurity Command Center services that commonly generate observations include the\nfollowing:\n\n- [Sensitive Data Protection](/security-command-center/docs/concepts-security-sources#dlp)\n- [Sensitive Actions Service](/security-command-center/docs/concepts-sensitive-actions-overview)\n\n`Posture violation` class\n\nFindings in the `Posture violation` class describe resource configurations that\ndon't align with your organization's [security\nposture](/security-command-center/docs/security-posture-overview) or a\n[Compliance Manager cloud\ncontrol](/security-command-center/docs/compliance-manager-overview).\n\n`SCC error` class\n\nFindings in the `SCC error` class identify a problem in the configuration\nof Security Command Center or one of its services that prevents\nSecurity Command Center from detecting security issues in your\nGoogle Cloud environment.\n\nFor more information about findings in the `SCC error` class, see\n[Overview of Security Command Center errors](/security-command-center/docs/concepts-scc-errors).\n\n`Threat` class\n\nFindings in the `Threat` class identify a potential active attack\nor other unwanted or malicious activity.\n\nFindings in the `Threat` class should be investigated immediately.\n\nFor more information about findings in the `Threat` class, see\n[Remediating threats](/security-command-center/docs/how-to-investigate-threats#remediating_threats).\n\n`Toxic combination` class\n\nFindings in the `Toxic combination` class identify a group of security\nissues that, when they occur together, create a path to one or more of\nyour high-value resources that a determined attacker could potentially\nuse to reach and compromise those resources.\n\nFor more information about `Toxic combination` class findings, see\n[Toxic combinations and chokepoints overview](/security-command-center/docs/toxic-combinations-overview).\n\n`Vulnerability` class\n\nFindings in the `Vulnerability` class identify a flaw or weakness in software\nprograms that an attacker could use to gain access to or\notherwise compromise your Google Cloud environment.\n\nFor more information about findings in the `Vulnerability` class, see\n[Vulnerability findings](/security-command-center/docs/concepts-vulnerabilities-findings).\n\n`Finding class unspecified` class\n\nFindings in the `Finding class unspecified` class either don't have\na value specified on the `findingClass` property or don't include the\nproperty at all.\n\nTo determine whether the finding identifies a threat, vulnerability, or\nother class of security issue, you need to review the finding and\ninvestigate the issue that it identifies.\n\nTypically, the service that generates the finding determines the finding\nclass and sets the `findingClass` property. We recommend that integrated\nand third-party service providers set the `findingClass` property, but\ndoing so is not required."]]