> [!NOTE]
> Enterprise (Deprecated) [service tier](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt)

> [!CAUTION]
> The Security Command Center Enterprise service tier will shut down on May 21, 2027. If your organization uses the Enterprise service tier, then the organization will automatically move to the Premium service tier on or after May 21, 2027. Contact your account representative or a [Google Cloud sales specialist](https://cloud.google.com/contact) if you have questions.

The Enterprise tier of Security Command Center lets you apply curated detection rules,
detect threats on other cloud platforms, and use cases to manage your
investigations.

The curated rules enable you to identify patterns in Google Cloud, AWS, and Azure data.
These features extend Security Command Center Enterprise threat detection to let you
identify more threat patterns in additional cloud environments.

For general information about how to use curated detections, see
[Getting started with curated detections](https://docs.cloud.google.com/chronicle/docs/detection/use-curated-detections.md.txt).

## Curated detections for AWS data

See [Overview of Cloud Threats Category](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category.md.txt)
for information about available curated detections for AWS data and the required data for each rule set.
For information about how to ingest data required by these rule sets, see the following:

- [Ingest AWS data](https://docs.cloud.google.com/chronicle/docs/ingestion/ingest-aws-logs-into-chronicle)
- Google Cloud data: You configured the Google Cloud data ingestion during the [Security Command Center Enterprise tier activation process](https://docs.cloud.google.com/security-command-center/docs/activate-enterprise-tier.md.txt). To change the configuration of Google Cloud data ingestion, see [Ingest Google Cloud data](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs).

## Curated detections for Microsoft Azure data

> [!WARNING]
>
> **Preview**
>
>
> This feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the
> [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA features are available "as is" and might have limited support.
>
> For more information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

See [Curated detections for Microsoft Azure and Microsoft Entra ID data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category.md.txt#azure-curated-detections)
for information about available rule sets and the required Azure data.

For information about how to ingest Azure and Microsoft Entra ID data required by these rule sets, see the following:

- [Supported devices and required log types](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category.md.txt#azure-supported-devices).
- [Ingest Azure and Microsoft Entra ID data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category.md.txt#ingest-azure).

## What's next

- If you purchased Mandiant Threat Defense as an add-on to Security Command Center Enterprise tier,
  Mandiant will provision access to the Mandiant documentation
  portal where you can find onboarding steps in the
  [Getting Started Guide for Mandiant Threat Defense for Google Security Operations](https://docs.mandiant.com/mh-hunt-getting-started).
  If you have not purchased Mandiant Threat Defense and are interested in learning more
  about this offering, see [Mandiant Threat Defense](https://docs.cloud.google.com/security/products/mandiant-managed-threat-hunting)
  or contact your account team.

- If you are working with AWS data, do the following:

  - Review the rule sets for AWS data in the [Cloud Threats category](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category.md.txt).
  - [Ingest AWS data](https://docs.cloud.google.com/chronicle/docs/ingestion/ingest-aws-logs-into-chronicle) to the Google Security Operations component.
- If you are working with Microsoft Azure and Microsoft Entra ID data, do the following:

  - Review the [Curated detections for Azure data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category.md.txt#azure-curated-detections).
  - Ingest [Azure and Microsoft Entra ID data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category.md.txt#ingest-azure) to the Google Security Operations component.