# Chrome Enterprise threats

Supported in:

> [!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.

This document provides an overview of the rule sets within the Chrome Enterprise
Threats category, the required data sources, and configuration you can use to
tune the alerts generated by each rule set.
Rule sets in the Chrome Enterprise Premium Threats category help identify threats in the
Google Cloud environment using Chrome Enterprise Premium Management logs. This category
includes the following rule sets:

- **Chrome Extension Threats**: Detects activities related to Chrome extensions
  that could indicate malicious or suspicious behavior.

- **Chrome Browser Threats**: Detects suspicious behavior within Chrome browser that
  may indicate a compromise. This includes, but is not limited to, payload
  deliveries, exfiltration attempts, and password harvesting.

## Supported devices and log types

The rule sets in the Chrome Enterprise Premium Threats category require logs from the
following Google Security Operations data sources:

- Chrome Management Logs (`CHROME_MANAGEMENT`)

To feed these logs to Google SecOps, follow the steps in
[Collect Google Chrome logs](https://docs.cloud.google.com/chronicle/docs/ingestion/default-parsers/collect-chrome-management).
Contact your Google SecOps representative if you need to collect
these logs using a different mechanism.

For a list of all Google SecOps supported data sources, see
[Supported log types and default parsers](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).

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