# Cloud threats

Supported in:

This document provides an overview of the rule sets in the Cloud Threats category, the
required data sources, and configuration you can use to tune the alerts generated
by each rule set. These rule sets help identify threats in Google Cloud
environments using Google Cloud data and in AWS environments using AWS data.

## Rule set descriptions

> [!IMPORTANT]
> **Important:** Rule sets in the Cloud Threats category are available with the Google Security Operations Enterprise license tier and Security Command Center Enterprise license tier.

The following rule sets are available in the Cloud Threats category.

- [Rule sets for Google Cloud data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#cloud-rule-sets)

- [Rule sets for AWS data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#aws-rule-sets)

- [Rule sets for Azure data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#azure-curated-detections)

- [Rule sets for Office 365 data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#office-curated-detections)

- [Rule sets for Okta data](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#okta-curated-detections)

The *CDIR* abbreviation stands for *Cloud Detection, Investigation, and Response*.

## Curated detections for Google Cloud data

Google Cloud rule sets help identify threats in Google Cloud environments using event
and context data, and includes the following rule sets:

- **Admin Action**: Activity associated with administrative actions, deemed suspicious but potentially legitimate depending on organizational use.
- **CDIR SCC Enhanced Exfiltration**: Contains context-aware rules that correlate Security Command Center Exfiltration findings with other log sources, including Cloud Audit Logs logs, Sensitive Data Protection context, BigQuery context and Security Command Center Misconfiguration logs.
- **CDIR SCC Enhanced Defense Evasion**: Contains context-aware rules that correlate Security Command Center Evasion or Defense Evasion findings with data from other Google Cloud data sources, including Cloud Audit Logs.
- **CDIR SCC Enhanced Malware**: Contains context-aware rules that correlate Security Command Center Malware findings with data, including the occurrence of IP addresses and domains and their prevalence scores, in addition to other data sources, including Cloud DNS logs.
- **CDIR SCC Enhanced Persistence**: Contains context-aware rules that correlate Security Command Center Persistence findings with data from sources, including Cloud DNS logs and IAM analysis logs.
- **CDIR SCC Enhanced Privilege Escalation**: Contains context-aware rules that correlate Security Command Center Privilege escalation findings with data from several other data sources, including Cloud Audit Logs.
- **CDIR SCC Credential Access**: Contains context-aware rules that correlate Security Command Center Credential Access findings with data from several other data sources, including Cloud Audit Logs
- **CDIR SCC Enhanced Discovery**: Contains context-aware rules that correlate Security Command Center Discovery escalation findings with data from sources such as Google Cloud services and Cloud Audit Logs.
- **CDIR SCC Brute Force**: Contains context-aware rules that correlate Security Command Center Brute Force escalation findings with data, including Cloud DNS logs.
- **CDIR SCC Data Destruction**: Contains context-aware rules that correlate Security Command Center Data Destruction escalation findings with data from several other data sources, including Cloud Audit Logs.
- **CDIR SCC Inhibit System Recovery**: Contains context-aware rules that correlate Security Command Center Inhibit System Recovery findings with data from several other data sources, including Cloud Audit Logs.
- **CDIR SCC Execution**: Contains context-aware rules that correlate Security Command Center Execution findings with data from several other data sources, including Cloud Audit Logs.
- **CDIR SCC Initial Access**: Contains context-aware rules that correlate Security Command Center Initial Access findings with data from several other data sources, including Cloud Audit Logs.
- **CDIR SCC Impair Defenses**: Contains context-aware rules that correlate Security Command Center Impair Defenses findings with data from several other data sources, including Cloud Audit Logs.
- **CDIR SCC Impact** : Contains rules that detect *Impact* findings from Security Command Center with a Critical, High, Medium, and Low severity classification.
- **CDIR SCC Cloud IDS**: Contains rules that detect Cloud Intrusion Detection System findings from Security Command Center with a Critical, High, Medium, and Low severity classification.
- **CDIR SCC Cloud Armor**: Contains rules that detect Google Cloud Armor findings from Security Command Center.
- **CDIR SCC Custom Module**: Contains rules that detect Event Threat Detection custom module findings from Security Command Center.
- **Cloud Hacktool**: Activity detected from known offensive security platforms or from offensive tools or software used in the wild by threat actors that specifically target cloud resources.
- **Cloud SQL Ransom**: Detects activity associated with exfiltration or ransom of data within Cloud SQL databases.
- **Kubernetes Suspicious Tools**: Detects reconnaissance and exploitation behavior from open source Kubernetes tools.
- **Kubernetes RBAC Abuse**: Detects Kubernetes activity associated with the abuse of role-based access controls (RBAC) that attempt privilege escalation or lateral movement.
- **Kubernetes Certificate Sensitive Actions**: Detects Kubernetes Certificates and Certificate Signing Requests (CSR's) actions that could be used to establish persistence or escalate privileges.
- **IAM Abuse**: Activity associated with abusing IAM roles and permissions to potentially privilege-escalate or laterally move within a given Cloud project or across a Cloud organization.
- **Potential Exfil Activity**: Detects activity associated with potential exfiltration of data.
- **Resource Masquerading**: Detects Google Cloud resources created with names or characteristics of another resource or resource type. This could be used to mask malicious activity carried out by or within the resource, with the intention of appearing legitimate.
- **Serverless Threats** : Detects activity associated with potential compromise or abuse of Serverless resources in Google Cloud, including Cloud Run and Cloud Run functions.
- **Service Disruption**: Detect destructive or disruptive actions that, if performed in a functioning production environment, may cause a significant outage. The detected behavior is common and likely benign in testing and development environments.
- **Suspicious Behavior**: Activity that is thought to be uncommon and suspicious in most environments.
- **Suspicious Infrastructure Change**: Detects modifications to production infrastructure that align with known persistence tactics
- **Weakened Config**: Activity associated with weakening or degrading a security control. Deemed suspicious, potentially legitimate depending on organizational use.
- **Potential Insider Data Exfiltration from Chrome**: Detects activity associated with potential insider threat behaviors, including data exfiltration or loss of potentially sensitive data outside of a Google Workspace organization. This includes behaviors from Chrome considered anomalous compared to a 30-day baseline.
- **Potential Insider Data Exfiltration from Drive**: Detects activity associated with potential insider threat behaviors, including data exfiltration or loss of potentially sensitive data outside of a Google Workspace organization. This includes behaviors from Drive considered anomalous compared to a 30-day baseline.
- **Potential Insider Data Exfiltration from Gmail**: Detects activity associated with potential insider threat behaviors, including data exfiltration or loss of potentially sensitive data outside of a Google Workspace organization. This includes behaviors from Gmail considered anomalous compared to a 30-day baseline.
- **Potential Workspace Account Compromise**: Detects insider threat behaviors indicating that the account could have been potentially compromised and may lead to privilege escalation attempts or lateral movement attempts within a Google Workspace organization. This would include behaviors considered rare or anomalous compared to a 30-day baseline.
- **Suspicious Workspace Administrative Actions**: Detect behaviors indicating potential evasion, security downgrading or rare and anomalous behaviors never seen in the last 30 days from users with higher privileges, including administrators.

### Supported devices and log types

The following sections describe the required data needed by rule sets in the Cloud
Threats category.

To ingest data from Google Cloud services, see [Ingest Cloud logs to Google SecOps](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs).
Contact your Google SecOps representative if you need to collect these logs
using a different mechanism.

Google SecOps provides default parsers that parse and normalize raw logs
from Google Cloud services to create UDM records with data required by these rule sets.

For a list of all Google SecOps supported data sources, see
[Supported default parsers](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers).

#### All rule sets

To use any rule set, we recommend that you collect Google Cloud
Cloud Audit Logs. Certain rules require that customers enable Cloud DNS
logging. Make sure that Google Cloud services are configured to record
data to the following logs:

- [Cloud Audit Logs](https://docs.cloud.google.com/logging/docs/audit)
- [Cloud DNS Logs](https://docs.cloud.google.com/dns/docs/monitoring#using_logging)

#### Cloud SQL Ransom rule set

To use the *Cloud SQL Ransom* rule set, we recommend that you collect the following Google Cloud data:

- Log data listed in the [All rule sets](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#all-rule-sets) section.
- [Cloud SQL logs](https://docs.cloud.google.com/sql/docs/mysql/logging).

#### CDIR SCC Enhanced rule sets

All rule sets that begin with the name *CDIR SCC Enhanced* use Security Command Center Premium
findings contextualized with several other Google Cloud log sources, including the following:

- Cloud Audit Logs
- Cloud DNS logs
- Identity and Access Management (IAM) analysis
- Sensitive Data Protection context
- BigQuery context
- Compute Engine context

To use the *CDIR SCC Enhanced* rule sets, we recommend that you collect the following Google Cloud data:

- Log data listed in the [All rule
  sets](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#all-rule-sets) section.
- The following log data, listed by product name and Google SecOps ingestion label:

  - BigQuery (`GCP_BIGQUERY_CONTEXT`)
  - Compute Engine (`GCP_COMPUTE_CONTEXT`)
  - IAM (`GCP_IAM_CONTEXT`)
  - Sensitive Data Protection (`GCP_DLP_CONTEXT`)
  - Cloud Audit Logs (`GCP_CLOUDAUDIT`)
  - Google Workspace Activity (`WORKSPACE_ACTIVITY`)
  - Cloud DNS queries (`GCP_DNS`)
- The following [Security Command Center finding
  classes](https://docs.cloud.google.com/security-command-center/docs/finding-classes), listed
  by `findingClass` identifier and Google SecOps ingestion label:

  - `Threat` (`GCP_SECURITYCENTER_THREAT`)
  - `Misconfiguration` (`GCP_SECURITYCENTER_MISCONFIGURATION`)
  - `Vulnerability` (`GCP_SECURITYCENTER_VULNERABILITY`)
  - `SCC Error` (`GCP_SECURITYCENTER_ERROR`)

The *CDIR SCC Enhanced* rule sets also depend on data from Google Cloud services.
To send the required data to Google SecOps, make sure you complete
the following:

- Enable logging for the required Google Cloud products and services.
- Enable Security Command Center Premium and related services.
- Configure the [Ingestion of Google Cloud
  logs](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs) to Google SecOps.
- Configure the export of Event Threat Detection findings to Google SecOps. By default, all Security Command Center findings are ingested. See [Exporting Security Command Center findings](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs#exporting_security_command_center_findings_to) for more information about how Google SecOps default parsers map the data fields.
- Enable Cloud Audit Logs and configure the export of Cloud Audit Logs to Google SecOps. See [Collect Cloud Audit Logs](https://docs.cloud.google.com/chronicle/docs/ingestion/default-parsers/collect-audit-logs) for more information.
- Enable Google Workspace logs and send these logs to Google SecOps. See [Collect Google Workspace logs](https://docs.cloud.google.com/chronicle/docs/ingestion/default-parsers/collect-workspace-logs) for more information.
- Configure the export of Google Cloud asset metadata, and context-related data, to Google SecOps. See [Exporting Google Cloud Asset Metadata to Google SecOps](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs#exporting_asset_metadata_to) and [Exporting Sensitive Data Protection data to Google SecOps](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs#export-dlp) for more information.

The following rule sets create a detection when findings from [Security Command Center Event Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-event-threat-detection-overview),
[Google Cloud Armor](https://docs.cloud.google.com/armor/docs/cscc-findings), [Security Command Center Sensitive Actions Service](https://docs.cloud.google.com/security-command-center/docs/concepts-sensitive-actions-overview), and [Custom modules for Event Threat Detection](https://docs.cloud.google.com/security-command-center/docs/custom-modules-etd-overview) are identified:

- CDIR SCC Cloud IDS
- CDIR SCC Cloud Armor
- CDIR SCC Impact
- CDIR SCC Enhanced Persistence
- CDIR SCC Enhanced Defense Evasion
- CDIR SCC Custom Module

#### Kubernetes Suspicious Tools rule set

To use the *Kubernetes Suspicious Tools* rule set, we recommend that you collect
the data listed in the [All rule sets](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#all-rule-sets) section. Make sure that Google Cloud
services are configured to record data to [Google Kubernetes Engine (GKE) Node Logs](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/audit-logging)

#### Kubernetes RBAC Abuse rule set

To use the *Kubernetes RBAC Abuse* rule set, we recommend that you collect [Cloud Audit Logs](https://docs.cloud.google.com/logging/docs/audit),
listed in the [All rule sets](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#all-rule-sets) section.

#### Kubernetes Certificate Sensitive Actions rule set

To use the *Kubernetes Certificate Sensitive Actions* rule set, we recommend that you collect [Cloud Audit Logs](https://docs.cloud.google.com/logging/docs/audit),
listed in the [All rule sets](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#all-rule-sets) section.

#### Google Workspace-related rule sets

The following rule sets detect patterns in Google Workspace data:

- Potential Insider Data Exfiltration from Chrome
- Potential Insider Data Exfiltration from Drive
- Potential Insider Data Exfiltration from Gmail
- Potential Workspace Account Compromise
- Suspicious Workspace Administrative Actions

These rule sets require the following log types, listed by product name and
Google SecOps ingestion label:

- Workspace Activities (`WORKSPACE_ACTIVITY`)
- Workspace Alerts (`WORKSPACE_ALERTS`)
- Workspace ChromeOS Devices (`WORKSPACE_CHROMEOS`)
- Workspace Mobile Devices (`WORKSPACE_MOBILE`)
- Workspace Users (`WORKSPACE_USERS`)
- Google Chrome Browser Cloud Management (`CHROME_MANAGEMENT`)
- Gmail logs (`GMAIL_LOGS`)

To ingest the required data, do the following:

- Collect the data listed in the [All rule sets](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#all-rule-sets) section of this document.

- See [Ingest Google Workspace data to Google SecOps](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/workspace-to-chronicle) to collect `WORKSPACE_ACTIVITY`, `WORKSPACE_CHROMEOS`, `CHROME_MANAGEMENT`, and `GMAIL` logs.

- See [Collect Google Workspace logs](https://docs.cloud.google.com/chronicle/docs/ingestion/default-parsers/collect-workspace-logs)
  to ingest the following logs:

  - `WORKSPACE_ALERTS`
  - `WORKSPACE_MOBILE`
  - `WORKSPACE_USERS`

### Serverless Threats rule set

- Collect the data listed in the [All rule sets](https://docs.cloud.google.com/chronicle/docs/detection/cloud-threats-category#all-rule-sets) section of this document.
- [Cloud Run logs](https://docs.cloud.google.com/run/docs/logging) (`GCP_RUN`).

Cloud Run logs include [Request logs and Container
logs](https://docs.cloud.google.com/run/docs/logging) which are ingested as the `GCP_RUN` log type in
Google SecOps. `GCP_RUN` logs can be ingested using direct ingestion or
using Feeds and Cloud Storage. For specific log filters and more ingestion
details, see [Exporting Google Cloud Logs to Google SecOps](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs#export-logs). The following
export filter exports Google Cloud Cloud Run (`GCP_RUN`) logs, in
addition to the default logs both through the [direct ingestion mechanism](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs#export-logs) as well as through
Cloud Storage and
[Sinks](https://docs.cloud.google.com/logging/docs/export/configure_export_v2#creating_sink):

    log_id("run.googleapis.com/stdout") OR
    log_id("run.googleapis.com/stderr") OR
    log_id("run.googleapis.com/requests") OR
    log_id("run.googleapis.com/varlog/system)

## Curated detections for AWS rule sets

AWS rule sets in this category help identify threats in AWS environments using
event and context data, and includes the following rule sets:

- **AWS - Compute**: Detects anomalous activity surrounding AWS compute resources, including EC2 and Lambda.
- **AWS - Data**: Detects AWS activity associated with data resources, including RDS snapshots or S3 buckets made publicly available.
- **AWS - GuardDuty**: Context-aware AWS GuardDuty alerts for Behavior, Credential Access, Cryptomining, Discovery, Evasion, Execution, Exfiltration, Impact, Initial Access, Malware, Penetration Testing, Persistence, Policy, Privilege Escalation, and Unauthorized Access.
- **AWS - Hacktools**: Detects the use of Hacktools in an AWS environment such as scanners, toolkits, and frameworks.
- **AWS - Identity**: Detections for AWS activity associated with IAM and authentication activity, including unusual logins from multiple geo-locations, overly permissive role creation, or IAM activity from suspicious tools.
- **AWS - Logging and Monitoring**: Detects AWS activity related to the disabling of logging and monitoring services, including CloudTrail, CloudWatch, and GuardDuty.
- **AWS - Network**: Detects insecure alterations to AWS network settings such as security groups and firewalls.
- **AWS - Organization**: Detects AWS activity associated with your organization , including the addition or removal of accounts, and unexpected events related to region usage.
- **AWS - Secrets**: Detects AWS activity associated with secrets, tokens, and passwords, including deletion of KMS secrets or Secrets Manager secrets.

### Supported devices and log types for AWS

These rule sets have been tested and are supported with the following Google SecOps
data sources, listed by product name and ingestion label.

- [AWS CloudTrail](https://aws.amazon.com/cloudtrail/) (`AWS_CLOUDTRAIL`)
- [AWS GuardDuty](https://aws.amazon.com/guardduty/) (`GUARDDUTY`)
- [AWS EC2 HOSTS](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_Host.html) (`AWS_EC2_HOSTS`)
- [AWS EC2 INSTANCES](https://docs.aws.amazon.com/AWSEC2/latemp/APIReference/API_Reservation.html) (`AWS_EC2_INSTANCES`)
- [AWS EC2 VPCS](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeVpcs.html) (`AWS_EC2_VPCS`)
- [AWS IAM (IAM)](https://docs.aws.amazon.com/IAM/latest/APIReference) (`AWS_IAM`)

See [Configure the ingestion of AWS
data](https://docs.cloud.google.com/chronicle/docs/ingestion/ingest-aws-logs-into-chronicle) for information
about setting up ingestion of AWS data.

For a list of all supported data sources,
see [Supported default parsers](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers).

The following sections describe the required data needed by rule sets that
identify patterns in data.

You can ingest AWS data using an Amazon Simple Storage Service (Amazon S3)
bucket as a source type or, optionally, using Amazon S3 with Amazon Simple Queue
Service (Amazon SQS). At a high level, you will need to do the following:

- Configure Amazon S3 or Amazon S3 with Amazon SQS to collect log data.
- Configure a [Google SecOps Feed](https://docs.cloud.google.com/chronicle/docs/administration/feed-management) to ingest data from either Amazon S3 or Amazon SQS

See [Ingest AWS logs into Google SecOps](https://docs.cloud.google.com/chronicle/docs/ingestion/ingest-aws-logs-into-chronicle)
for the detailed steps required to configure AWS services and configure a
Google SecOps Feed to ingest AWS data.

You can use **AWS Managed Detection Testing** test rules to verify that AWS data
is being ingested to Google SecOps SIEM. These test rules help verify whether AWS
log data is being ingested as expected. After setting up the ingestion of AWS
data, you perform actions in AWS that should trigger the test rules.

See [Verify AWS data ingestion for Cloud Threats category](https://docs.cloud.google.com/chronicle/docs/detection/verify-data-ingestion#aws-cloud-threats)
for information about how verify the ingestion of AWS data using **AWS Managed Detection Testing** test rules.

## Curated detections for Azure data

> [!NOTE]
> **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).  
> If this feature isn't visible in your environment, see [Manage preview features](https://docs.cloud.google.com/chronicle/docs/secops/preview-features-manage) or contact your system administrator.

Certain rule sets in this category are designed to work with Azure data to identify threats in Azure environments using event data, context data, and alerts. They include the following:

- **Azure - Compute**: Detects anomalous activity related to Azure compute resources, including Kubernetes and virtual machines (VMs).
- **Azure - Data**: Detects activity associated with data resources, including Azure blob permissions, modifications, and invitations to external users to use Azure services on the tenant.
- **Azure - Defender for Cloud**: Identifies alerts received from context-aware Microsoft Defender for Cloud related to user behavior, credential access, cryptomining, discovery, evasion, execution, exfiltration, impact, initial access, malware, penetration testing, persistence, policy, privilege escalation, or unauthorized access across all Azure cloud services.
- **Azure - Hacktools**: Detects the use of hacking tools in an Azure environment, , including Tor and VPN anonymizers, scanners, and red teaming toolkits.
- **Azure - Identity**: Detects activity related to authentication and authorization, indicating unusual behavior, including concurrent access from multiple geographic locations, overly permissive access management policies, or Azure RBAC activity from suspicious tools.
- **Azure - Logging and Monitoring**: Detects activity related to the disabling of logging and monitoring services within Azure.
- **Azure - Network**: Detects insecure and notable alterations to Azure networking devices or settings, including security groups or firewalls, Azure Web Application Firewall, and denial of service policies.
- **Azure - Organization**: Detects activity associated with your organization, including the addition or removal of subscriptions and accounts.
- **Azure - Secrets**: Detects activity associated with secrets, tokens, and passwords (for example modifications to Azure Key Vault or storage account access keys).

### Supported devices and required log types for Azure

These rule sets have been tested and are supported with the following data
sources, listed by product name and [Google SecOps ingestion label](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers).

- [Azure Cloud Services](https://azure.microsoft.com/en-us/free/cloud-services/) (`AZURE_ACTIVITY`)
- [Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity/), previously Azure Active Directory (`AZURE_AD`)
- [Microsoft Entra ID audit logs](https://learn.microsoft.com/en-us/entra/identity/monitoring-health/concept-audit-logs), previously Azure AD audit logs (`AZURE_AD_AUDIT`)
- [Microsoft Defender for Cloud](https://www.microsoft.com/en-us/security/business/cloud-security/microsoft-defender-cloud) (`MICROSOFT_GRAPH_ALERT`)
- [Microsoft Graph API Activity](https://learn.microsoft.com/en-us/graph/use-the-api) (`MICROSOFT_GRAPH_ACTIVITY_LOGS`)

### Ingest Azure and Microsoft Entra ID data

You must ingest data from every data source to have maximum rule
coverage. See the following documentation for information about how to ingest
data from each source.

- [Ingest Azure Monitor Activity logs](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-azure-activity-logs) from Azure Cloud Services.
- [Collect Microsoft Entra ID data](https://docs.cloud.google.com/chronicle/docs/preview/siem-integrations/azure-ad) (formerly called Azure AD), including the following:
  - Microsoft Entra ID logs
  - Microsoft Entra ID audit logs
  - Microsoft Entra ID context data
- [Collect Microsoft Graph security API alert logs](https://docs.cloud.google.com/chronicle/docs/preview/siem-integrations/microsoft-graph-alert) to Ingest Microsoft Defender for Cloud logs using the Microsoft Graph Security API.
- [Collect Microsoft Graph API activity logs](https://docs.cloud.google.com/chronicle/docs/ingestion/default-parsers/microsoft-graph-alert) to Ingest Microsoft Graph API Activity logs using the Microsoft Graph API.

The following section describes how to verify the ingestion of Azure data using
predefined test rules.

### Verify the ingestion of Azure data

The Google SecOps [Data Ingestion and Health dashboard](https://docs.cloud.google.com/chronicle/docs/reports/dashboards-overview#ingest)
lets you see information about the type, volume, and health of all data being ingested
into Google SecOps using SIEM ingestion features.

You can use also *Azure Managed Detection Testing* test rules to
verify the ingestion of Azure data. After setting up the ingestion, you perform
actions in the Azure portal that should trigger the test rules.
They are intended to verify that data is ingested and in the expected format
to use the curated detections for Azure data.

> [!IMPORTANT]
> **Important:** The user who enables these rules in the Detection Engine must have the [`curatedRuleSetDeployments.batchUpdate`](https://docs.cloud.google.com/iam/docs/permissions-reference) IAM permission.

### Enable the Azure Managed Detection Testing test rules

1. In Google Security Operations, click **Detections** \> **Rules \& Detections** to [open the Curated Detections page](https://docs.cloud.google.com/chronicle/docs/detection/curated-detections#open_the_curated_detections_page_and_rule_sets).
2. Select the **Managed Detection Testing** \> **Azure Managed Detection
   Testing**.
3. Enable both **Status** and **Alerting** for the **Broad** and **Precise** rules.

### Send user action data to trigger the test rules

To verify that data is ingested as expected, create a user and login to verify that
these actions trigger the test rules. For information about creating users in Microsoft Entra ID, see
[How to create, invite, and delete users](https://learn.microsoft.com/en-us/entra/fundamentals/how-to-create-delete-users).

1. In Azure, create a new Microsoft Entra ID user.

   > [!IMPORTANT]
   > **Important:** The following steps must be performed as a user in the chosen account that has permission to create a new user in Microsoft Entra ID.

   1. Navigate to the Azure portal.
   2. Open **Microsoft Entra ID**.
   3. Click **Add** , then **Create New User** . Do the following to define the user:
      1. Enter the following information:
         - User principal name: `GCTI_ALERT_VALIDATION`
         - User principal name: `GCTI_ALERT_VALIDATION`
         - Display name: `GCTI_ALERT_VALIDATION`
      2. Select **Auto-generate Password** to auto-generate a password for this user.
      3. Select the **Account Enabled** checkbox.
      4. Open the **Review + Create** tab.
      5. Remember the auto-generated password. You will use this in upcoming steps.
      6. Click **Create**.
   4. Open a browser window in incognito mode, and then navigate to the Azure portal.
   5. Sign in with the newly created user and password.
   6. Change the user password.
   7. Set up multi-factor authentication (MFA), as required by your organization.
   8. Sign out of the Azure portal and confirm your logout.
2. Do the following to verify that alerts are created in Google Security Operations:

   1. In Google Security Operations, click **Detections** \> **Rules \& Detections**
      to [open the **Curated Detections** page](https://docs.cloud.google.com/chronicle/docs/detection/curated-detections#open_the_curated_detections_page_and_rule_sets).

   2. Click **Dashboard**.

   3. In the list of detections, check that the following rules were triggered:

      - **tst_azure_ad_user_creation**
      - **tst_azure_ad_user_login**
3. After you confirm that data is sent and that these rules are triggered,
   deactivate or deprovision the user account.

### Send sample alerts to trigger the test rules

Perform the following steps to verify that generating sample security alerts in Azure
triggers the test rules. For more information about generating sample security
alerts in Microsoft Defender for Cloud, see [Alert validation in Microsoft Defender for Cloud](https://learn.microsoft.com/en-us/azure/defender-for-cloud/alert-validation).

> [!IMPORTANT]
> **Important:** The following steps must be performed as a user in the chosen account that has permission to edit the tags of a virtual machine (VM) instance.

1. In the Azure Portal, navigate to **All Services**.
2. Under **Security** , open **Microsoft Defender for Cloud**.
3. Navigate to **Security Alerts**.
4. Click **Sample Alerts** , and then do the following:
   1. Select your subscription.
   2. Select **all** for **Defender for Cloud Plans**.
   3. Click **Create Sample Alerts**.
5. Verify that test alerts are triggered.
6. In Google Security Operations, click **Detections** \> **Rules \& Detections** to [open the **Curated Detections** page](https://docs.cloud.google.com/chronicle/docs/detection/curated-detections#open_the_curated_detections_page_and_rule_sets).
7. Click **Dashboard**.
8. In the list of detections, check that the following rules were triggered:
   - **tst_azure_activity**
   - **tst_azure_defender_for_cloud_alerts**

### Execute a GET API request in Microsoft Graph Explorer to trigger the test rules

Perform the following steps to verify that generating sample security alerts in Azure
triggers the test rules.

> [!IMPORTANT]
> **Important:** Make sure you are logged in to the Azure portal.

1. Navigate to [**Microsoft Graph Explorer**](https://developer.microsoft.com/en-us/graph/graph-explorer).
2. Verify that the appropriate tenant is selected.
3. Click **Run Query**.
4. Verify that test alerts are triggered.
5. In Google Security Operations, click **Detections** \> **Rules \& Detections** to [open the **Curated Detections** page](https://docs.cloud.google.com/chronicle/docs/detection/curated-detections#open_the_curated_detections_page_and_rule_sets).
6. Click **Dashboard**.
7. In the list of detections, check that the **tst_microsoft_graph_api_get_activity** rule was triggered.

### Disable the Azure Managed Detection Testing rule sets

1. In Google Security Operations, click **Detection** \> **Rules \& Detections** to [open the **Curated Detections** page](https://docs.cloud.google.com/chronicle/docs/detection/curated-detections#open_the_curated_detections_page_and_rule_sets).
2. Select the **Managed Detection Testing** \> **Azure Managed Detection
   Testing** rules.
3. Disable both **Status** and **Alerting** for the **Broad** and **Precise** rules.

## Curated detections for Office 365 data

Office 365 rule sets in this category help identify threats in Office 365
environments using event and context data, and includes the following rule sets:

- **Office 365 - Administrative**: Detects malicious, suspicious
  and high-risk activities in Office 365, including backup policy changes, Microsoft
  Purview, and ATP detections.

- **Office 365 - eDiscovery**: Detects malicious, suspicious,
  and high-risk activities in Office 365 eDiscovery, including attempts to search for
  credentials or other sensitive data.

- **Office 365 - Email**: Detects malicious, suspicious, and high
  risk activities in Office 365 Email, including phishing attempts, risky email
  setting changes, and suspicious email activity.

- **Office 365 - Forms**: Detects malicious, suspicious, and high
  risk activities in Office 365 Forms, including phishing attempts, and status updates
  for forms accounts.

- **Office 365 - Identity**: Detects malicious, suspicious, and
  high-risk activities in Office 365 related to identity and access management,
  including potential token theft, risky authentication configurations, MFA attacks,
  password attacks, and known hacking tools.

- **Office 365 - Sharepoint and OneDrive**: Detects malicious,
  suspicious, and high-risk activities in Office 365 Sharepoint and OneDrive,
  including malware uploads, anonymous file sharing, and searches for credentials
  and financial data.

- **Office 365 - Teams**: Detects malicious, suspicious, and
  high-risk activities in Office 365 Teams, including impersonation of teams accounts,
  exporting of recordings, and transcripts.

### Supported devices and required log types for Office 365

These rule sets have been tested and are supported with the following data sources,
listed by product name and [Google SecOps ingestion label](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers):

## Curated detection for Okta rule sets

Okta rule sets in this category help detect threats within Okta environments by
analyzing event and context data. The rule set includes the following:

- **Okta**: Identifies a range of malicious and suspicious activities occurring within the Okta platform, including MFA attacks, brute force attempts, password spraying, login anomalies, and more.

### Supported devices and required log types for Okta

These rule sets have been tested and are supported with the following data sources,
listed by product name and [Google SecOps ingestion label](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers):

## Tune alerts returned by rule sets

You can reduce the number of detections a rule or rule set generates using
[rule exclusions](https://docs.cloud.google.com/chronicle/docs/investigation/alert-suppression#suppress-rule-exclusions).

A rule exclusion defines the criteria used to exclude an event from being evaluated by
the rule set, or by specific rules in the rule set. Create one or more rule exclusions
to help reduce the volume of detections. For more information, see
[Configure alert suppression](https://docs.cloud.google.com/chronicle/docs/investigation/alert-suppression).

## What's next

- [Ingest Google Cloud logs](https://docs.cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs)
- [Ingest AWS logs](https://docs.cloud.google.com/chronicle/docs/ingestion/ingest-aws-logs-into-chronicle)
- [Investigate an alert](https://docs.cloud.google.com/chronicle/docs/investigation/investigate-alert)

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)