[[["易于理解","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-09-02。"],[],[],null,["Overview of composite rules category \nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n\nThis document provides an overview of the composite rule sets, the required data\nsources, and the configuration options for tuning the alerts they generate.\nThese rule sets provide higher-fidelity alerting. They establish severity,\nconfidence, risk, and priority levels\nacross all Google Security Operations-enabled detection content for Google Cloud\nand endpoint environments.\n\nDescribe rule sets\n\nThe Composite Rules category includes the following rule sets:\n\n- [Endpoint composite rules](#endpoint_composite_rules)\n- [Cloud composite rules](#cloud_composite_rules)\n\nUnderstand endpoint composite rules\n\nThese rules correlate findings from multiple detection rules that relate to\nthe same endpoint over a defined time period. Confidence and risk levels are\ndetermined by specific characteristics of those detections.\n\nUnderstand Cloud composite rules\n\nThese rules correlate findings from multiple detection rules associated with the same\nGoogle Cloud account or Google Cloud resource over a defined\ntime period. Confidence and risk levels are based on specific\ncharacteristics of those detections.\n\nSupported devices and log types\n\nThese rules primarily rely on Cloud Audit Logs, endpoint detection and\nresponse logs, and network proxy logs. Google SecOps UDM\nautomatically normalizes these log sources. The following categories outline\nthe most important log sources required for the curated composite content to\nfunction effectively:\n\n**Endpoint composite rule log sources**\n\n- [Linux threats](/chronicle/docs/detection/linux-threats-category#supported_devices_and_log_types)\n- [MacOS threats](/chronicle/docs/detection/macos-threats-category#supported_devices_and_log_types)\n- [Windows threats](/chronicle/docs/detection/windows-threats-category#supported_devices_and_log_types)\n\n**Google Cloud composite rule log sources**\n\n- [Google Cloud](/chronicle/docs/detection/cloud-threats-category#log-types)\n- [AWS](/chronicle/docs/detection/cloud-threats-category#aws-log-types)\n- [Azure](/chronicle/docs/detection/cloud-threats-category#azure-supported-devices)\n- [Office365](/chronicle/docs/detection/cloud-threats-category#supported_devices_and_required_log_types_for_office_365)\n- [Okta](/chronicle/docs/detection/cloud-threats-category#supported_devices_and_required_log_types_for_okta)\n\n**Google Cloud and endpoint rule log sources**\n\n- [Applied Threat Intelligence (ATI)](/chronicle/docs/detection/ati-curated-detections#supported_devices_and_log_types)\n- [Chrome Enterprise Threats](/chronicle/docs/detection/chrome-enterprise-threats-category#supported_devices_and_log_types)\n- [Risk Analytics for UEBA](/chronicle/docs/detection/risk-analytics-ueba-category#required_data_needed_by_risk_analytics_for_ueba_category)\n\nFor a complete list of the available curated detections, see\n[Use curated detections](/chronicle/docs/detection/curated-detections). Contact\nyour Google SecOps representative if you need to enable the\ndetection sources using a different mechanism.\n\nGoogle SecOps provides default parsers that parse and normalize\nraw logs to create UDM records with data required by composite and curated\ndetection rule sets. For a list of all Google SecOps supported\ndata sources, see [Supported default parsers](/chronicle/docs/ingestion/parser-list/supported-default-parsers).\n\nModify rules in a rule set\n\nYou can customize the behavior of rules within a rule set to meet your\norganization's needs. Adjust how each rule operates by selecting one of\nthe following detection modes, and configure whether the rules\ngenerate alerts.\n\n- **Broad:** detects potentially malicious or anomalous behavior, but may produce more false positives due to the general nature of the rule.\n\nTo modify the settings, do the following:\n\n1. From the rules list, select the checkbox next to each rule that you want to\n modify.\n\n2. Configure the **Status** and **Alerting** settings for the rules as follows:\n\n - **Status:** applies the mode (**Precise** or **Broad** )\n to the selected rule. Set to `Enabled` to activate the rule's status to the\n mode.\n\n - **Alerting:** controls whether the rule generates an alert on the **Alerts**\n page. Set to **On** to enable alerts.\n\nTune alerts from rule sets\n\nYou can reduce the number of alerts generated by a composite rule by using\n[rule exclusions](/chronicle/docs/detection/rule-exclusions).\n\nA rule exclusion specifies criteria that prevent certain events from being\nevaluated by a rule or rule set. Use exclusions to reduce detection volume. See\n[Configure rule exclusions](/chronicle/docs/detection/rule-exclusions) for\nmore information.\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]