您可以使用 Security Command Center 根据各种监管框架评估您的 Google Cloud 环境。
Security Command Center 会监控您是否符合各种安全标准的控制项所对应的检测器。
对于每项受支持的安全标准,Security Command Center 会检查其中的一部分控制项。对于已检查的控制项,Security Command Center 会显示通过的控制项数量。对于未通过的控制,Security Command Center 会显示一列发现结果,其中描述了控制失败情况。
CIS 已审核并认证了 Security Command Center 检测器与 CIS Google Cloud Foundations Benchmark 的各个受支持版本的映射。
其他合规性映射仅供参考。
Security Command Center 会定期添加对新的基准版本和标准的支持。旧版本仍然受支持,但最终会被弃用。我们建议您使用当前受支持的最新基准或标准。
借助安全状况服务,您可以将组织政策和 Security Health Analytics 检测器映射到适用于您业务的标准和控制措施。创建安全状况后,您可以监控环境的任何更改,以确保不会影响贵组织的合规性。
[[["易于理解","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-08-19。"],[],[],null,["| Premium and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nYou can use Security Command Center to evaluate your Google Cloud environment against\nvarious regulatory frameworks.\n| **Note:** This document applies to compliance management if you haven't enable Compliance Manager ([Preview](/products#product-launch-stages)). For information about compliance with Compliance Manager, see [Compliance Manager\n| overview](/security-command-center/docs/compliance-manager-overview).\n\n\nSecurity Command Center monitors\nyour compliance with detectors that are mapped to the controls of a wide variety of security\nstandards.\n\nFor each supported security standard,\nSecurity Command Center checks a\nsubset of the controls. For the controls checked, Security Command Center shows you how many are\npassing. For the controls that are not passing, Security Command Center shows you a list of findings\nthat describe the control failures.\n\n\nCIS reviews and certifies the mappings of\nSecurity Command Center\ndetectors to each supported version of the CIS Google Cloud Foundations Benchmark.\nAdditional compliance mappings are included for reference purposes only.\n\n\nSecurity Command Center\nadds support for new benchmark versions and standards periodically. Older versions remain\nsupported, but are eventually deprecated. We recommend that you use the latest supported benchmark\nor standard available.\n\n\nWith the\n[security posture service](/security-command-center/docs/security-posture-overview),\nyou can map organization policies and Security Health Analytics detectors to the standards and controls\nthat apply to your business. After you create a security posture, you can monitor for any changes\nto the environment that could affect your business's compliance.\n\n\nWith [Compliance Manager](/security-command-center/docs/compliance-manager-overview)\n([Preview](/products#product-launch-stages)), you can deploy frameworks that map regulatory controls to cloud\ncontrols. After you create a framework, you can monitor for any changes to the environment that\nmight affect your business's compliance and audit your environment.\n\nSupported security standards **Note:** These standards are supported if you have't enabled Compliance Manager ([Preview](/products#product-launch-stages)). For information about the frameworks that you can use with Compliance Manager, see the [Compliance Manager overview](/security-command-center/docs/compliance-manager-overvew#built-in-frameworks).\n\nGoogle Cloud\n\n\nSecurity Command Center\nmaps detectors for Google Cloud to one or more of the following compliance\nstandards:\n\n- [Center for Information Security (CIS) Controls 8.0](https://www.cisecurity.org/controls/v8)\n- [CIS Google Cloud Computing Foundations Benchmark](https://www.cisecurity.org/benchmark/google_cloud_computing_platform) v2.0.0, v1.3.0, v1.2.0, v1.1.0, and v1.0.0\n- [CIS Kubernetes Benchmark v1.5.1](https://www.cisecurity.org/benchmark/kubernetes)\n- [Cloud Controls Matrix (CCM) 4](https://cloudsecurityalliance.org/artifacts/cloud-controls-matrix-v4)\n- [Health Insurance Portability and Accountability Act (HIPAA)](https://www.hhs.gov/hipaa/for-professionals/security/index.html)\n- [International Organization for Standardization (ISO) 27001, 2022 and 2013](https://www.iso.org/standard/27001)\n- [National Institute of Standards and Technology (NIST) 800-53 R5 and R4](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls/release-search#/)\n- [National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) 1.0](https://www.nist.gov/cyberframework/framework-version-10)\n- [Open Web Application Security Project (OWASP) Top Ten, 2021 and 2017](https://owasp.org/www-project-top-ten/)\n- [Payment Card Industry Data Security Standard (PCI DSS) 4.0 and 3.2.1](https://www.pcisecuritystandards.org/document_library/)\n- System and Organization Controls (SOC) 2 [2017 Trust Services Criteria (TSC)](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022)\n\nAWS\n| **Enterprise tier only:** This feature is available only with the\n| [Security Command Center Enterprise tier](/security-command-center/docs/service-tiers).\n\nSecurity Command Center\nmaps detectors for Amazon Web Services (AWS) to one or more of the following compliance\nstandards:\n\n- [CIS Amazon Web Services Foundations](https://www.cisecurity.org/benchmark/amazon_web_services) 2.0.0\n- [CIS Critical Security Controls Version 8.0](https://www.cisecurity.org/controls/v8)\n- [Cloud Controls Matrix (CCM) 4](https://cloudsecurityalliance.org/artifacts/cloud-controls-matrix-v4)\n- [Health Insurance Portability and Accountability Act (HIPAA)](https://www.hhs.gov/hipaa/for-professionals/security/index.html)\n- [International Organization for Standardization (ISO) 27001, 2022](https://www.iso.org/standard/27001)\n- [National\n Institute of Standards and Technology (NIST) 800-53 R5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls/release-search#/)\n- National Institute of Standards and Technology (NIST) [Cybersecurity Framework (CSF) 1.0](https://www.nist.gov/cyberframework/framework-version-10)\n- [Payment Card Industry Data Security Standard (PCI DSS) 4.0 and 3.2.1](https://www.pcisecuritystandards.org/document_library/)\n- System and Organization Controls (SOC) 2 [2017 Trusted Services Criteria (TSC)](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022)\n\nDetectors and findings as compliance controls\n\nSecurity Command Center detection services, like Security Health Analytics and\nWeb Security Scanner, use detection modules (detectors) to check for\nvulnerabilities and misconfigurations in your cloud environment.\n\nWhen a vulnerability is found, the detector generates a *finding*. A finding is\na record of a vulnerability or other security issue that includes information\nsuch as the following:\n\n- A description of the vulnerability\n\n- A recommendation to address the vulnerability that would bring the control\n into compliance\n\n- The numerical ID of the control that corresponds to the finding\n\n- Recommended steps for remediating the vulnerability\n\nNot all controls in a standard can be mapped to Security Command Center findings,\nusually because certain controls can't be automated, but possibly for other\nreasons. Consequently, the total number of controls that Security Command Center\nchecks for is usually less than the total number of controls that a standard\ndefines.\n\nCIS reviews and certifies the mappings of Security Command Center detectors to each\nsupported version of the CIS Google Cloud Foundations Benchmark.\nAdditional compliance mappings are included for reference purposes only.\n\nTo learn more about Security Health Analytics and Web Security Scanner findings and\nthe mapping between supported detectors and compliance standards, see\n[vulnerabilities findings](/security-command-center/docs/concepts-vulnerabilities-findings).\n\nEvaluate compliance across your cloud environment\n\nYou can see at a glance how compliant your cloud environment is with a given\nsecurity standard in the following places:\n\n- The [**Compliance**](https://console.cloud.google.com/security/command-center/compliance) page in the Google Cloud console.\n- The **Risk \\\u003e Overview** page in the Security Operations console. This page shows an at-a-glance view of the top risks found in your cloud environments, including compliance.\n\nEach security standard shows a percentage of how many of their constituent\ncontrols receive a passing grade at the selected scope, whether that is at the\norganization, folder, or project level.\n\nWhere Security Command Center has been activated affects what is shown:\n\n- **At the project level** : You can only view the activated project's compliance\n statistics. If you switch to a folder or organization that the project belongs\n to in the Google Cloud console, the **Compliance** page does not display.\n\n- **At the organization level** : If you switch to the activated organization in\n the Google Cloud console, the **Compliance** page shows compliance\n statistics for the entire organization, including its folders and projects.\n\n To view compliance statistics for individual folders and projects within that\n organization, switch to that resource level in the Google Cloud console.\n\nCompliance reports are generated daily. Reports can be 24 hours stale, and might\nbe missing if they've failed to generate.\n| **Note:** Security Command Center vulnerability detection services, such as Security Health Analytics and Web Security Scanner, monitor controls based on a best effort mapping between the detectors of the services and the controls of a standard.\n\nAssess compliance in Google Cloud console\n\n1. Go to the **Compliance** page in the Google Cloud console.\n\n\n [Go to Compliance](https://console.cloud.google.com/security/command-center/compliance)\n\n \u003cbr /\u003e\n\n2. Select the project, folder, or organization you want to view compliance for.\n\n3. Click **View details** in one of the standards cards to open its\n **Compliance detail** page.\n\nFrom this page, you can do the following things:\n\n- View compliance against the selected standard on a particular date.\n\n- Switch the compliance standard that you're viewing the details for.\n\n- Export a report of the compliance details to a CSV file.\n\n- Track compliance progress over time with a trend chart.\n\n- Expand security standard controls to view their constituent rules and\n rule severity.\n\n- Click rules to view findings for non-compliant resources and remediate issues\n where appropriate. For information on remediating findings, see\n [Remediating Security Health Analytics findings](/security-command-center/docs/how-to-remediate-security-health-analytics-findings)\n and\n [Remediating Web Security Scanner findings](/security-command-center/docs/how-to-remediate-web-security-scanner-findings)."]]