After a service, feature, or product is officially
deprecated, it continues to be available for at least the period of time defined in the
Terms of Service. After this period of time, the service is scheduled for shutdown.
Feature
Deprecated date
Shutdown date
Details
Manual state changes for Security Health Analytics and VM Manager findings
February 20,
2024
On or after October 21, 2024
On or after the shutdown date, you can no longer manually
update the state of vulnerability or misconfiguration findings that are
generated by Security Health Analytics or VM Manager.
Security Command Center also prevents the manual creation of findings under the exact
same name as a source that is automatically managed by Security Command Center. This
restriction prevents you from creating findings that can never be resolved.
Security Health Analytics use of security marks for asset allowlists
June 26, 2023
On or after April 15, 2025
This feature is available only in instances of Security Command Center that were
activated before June 26, 2023. If your activation of Security Command Center
began on or after June 26, 2023, use the
mute feature to
suppress findings for certain assets.
After April 15, 2025, you can still apply security marks to assets,
but they no longer affect the way that Security Health Analytics processes assets.
The Preview release of
the Rapid Vulnerability Detection service is discontinued and the
service was shut down on July 14, 2024.
The status of any findings produced by the Rapid Vulnerability
Detection service have automatically been set to
Inactive. Findings are retained for the period defined in
the
Security Command Center data retention policy.
Security Command Center asset management features:
Security Command Center Asset API endpoints
Except for gcloud scc assets update-marks, the assets
subgroup of the gcloud scc
The Assets page and related functionality in the
Google Cloud console
June 20, 2023
On or after June 20, 2024
This feature is available only in instances of Security Command Center that were
activated before June 20, 2023, and used the asset functionality in
the 90 days prior to that date.
If your organization activated Security Command Center before June 20, 2023, plan
to migrate your asset management operations from the
Security Command Center API and the gcloud scc assets commands to
Cloud Asset Inventory by June 20, 2024. These Security Command Center asset
management features will be removed from Security Command Center for all users on
or after June 20, 2024.
For a list of asset types that Cloud Asset Inventory supports, see
Supported asset types.
Detector shut downs
Detection rules and modules are managed services, and aren't subject to Google
Cloud's deprecation policy. They can be shut down when they have become
redundant or have lost relevance.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["| Standard, Premium, and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThe\n[Google Cloud Platform Terms of Service (section \"Discontinuation of Services\")](/terms)\ndefines the deprecation policy that applies to Security Command Center.\nThe [deprecation policy](/terms/deprecation) only applies to the services,\nfeatures, or products listed therein.\n\n\nAfter a service, feature, or product is officially\ndeprecated, it continues to be available for at least the period of time defined in the\nTerms of Service. After this period of time, the service is scheduled for shutdown.\n\n| Feature | Deprecated date | Shutdown date | Details |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Manual state changes for Security Health Analytics and VM Manager findings | February 20, 2024 | On or after October 21, 2024 | On or after the shutdown date, you can no longer manually update the state of vulnerability or misconfiguration findings that are generated by Security Health Analytics or VM Manager. Security Command Center also prevents the manual creation of findings under the exact same name as a source that is automatically managed by Security Command Center. This restriction prevents you from creating findings that can never be resolved. |\n| Security Health Analytics use of security marks for asset allowlists | June 26, 2023 | On or after April 15, 2025 | This feature is available only in instances of Security Command Center that were activated before June 26, 2023. If your activation of Security Command Center began on or after June 26, 2023, use the [mute feature](/security-command-center/docs/how-to-mute-findings) to suppress findings for certain assets. After April 15, 2025, you can still apply security marks to assets, but they no longer affect the way that Security Health Analytics processes assets. For more information about security marks for assets, see [Add assets to allowlists](/security-command-center/docs/how-to-use-security-health-analytics#allowlist-assets). |\n| Rapid Vulnerability Detection service | May 14, 2024 | July 14, 2024 | The [Preview release](/products#product-launch-stages) of the Rapid Vulnerability Detection service is discontinued and the service was shut down on July 14, 2024. The status of any findings produced by the Rapid Vulnerability Detection service have automatically been set to `Inactive`. Findings are retained for the period defined in the [Security Command Center data retention policy](/security-command-center/docs/concepts-data-security-overview#data_retention). |\n| Security Command Center asset management features: - Security Command Center Asset API endpoints - Except for `gcloud scc assets update-marks`, the assets subgroup of the `gcloud scc` - The **Assets** page and related functionality in the Google Cloud console | June 20, 2023 | On or after June 20, 2024 | This feature is available only in instances of Security Command Center that were activated before June 20, 2023, and used the asset functionality in the 90 days prior to that date. If your organization activated Security Command Center before June 20, 2023, plan to migrate your asset management operations from the Security Command Center API and the `gcloud scc assets` commands to [Cloud Asset Inventory](/asset-inventory/docs/asset-inventory-overview) by June 20, 2024. These Security Command Center asset management features will be removed from Security Command Center for all users on or after June 20, 2024. For a list of asset types that Cloud Asset Inventory supports, see [Supported asset types](/asset-inventory/docs/supported-asset-types). |\n\nDetector shut downs\n\n\u003cbr /\u003e\n\nDetection rules and modules are managed services, and aren't subject to Google\nCloud's deprecation policy. They can be shut down when they have become\nredundant or have lost relevance.\n\n| Service | Finding display name | API name | Shutdown date | Description |\n|----------------------------------|------------------------------------------------------|------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Virtual Machine Threat Detection | Defense Evasion: Unexpected kernel code modification | `Not applicable` | June 2, 2025 | Detects unexpected modifications in the kernel code memory. |\n| Event Threat Detection | Outgoing DoS | `OUTGOING_DOS` | October 24, 2024 | Detects outgoing denial of service traffic. |\n| Virtual Machine Threat Detection | VMTD disabled | `VMTD_DISABLED` | October 18, 2024 | VM Threat Detection is disabled. Until you enable it, this service can't scan your Compute Engine projects and VM instances for unwanted applications. |"]]
