AWS guardduty: Custom Detection Rules now support Runtime Monitoring events
Summary
Expands the 'how it works' page to cover Runtime Monitoring as a supported data source for Custom Detection Rules, including per-data-source requirements (Runtime Monitoring enabled for EKS/EC2/ECS on Fargate, minimum GuardDuty security agent version), the note that stale agents silently fail to match, and data-source-specific finding aggregation behavior (CloudTrail vs Runtime Monitoring). Also scopes the redaction section to CloudTrail rules only.
Security assessment
The change documents a threat-detection capability (custom rules over Runtime Monitoring process/file/network telemetry) and its operational prerequisites, including the warning that an outdated security agent causes rules to silently not match ('GuardDuty does not report an error in this case, so keep the agent up to date'). This is detection-coverage/hardening guidance rather than a fix for a specific vulnerability, so it is security documentation of medium impact.
Evidence
+Custom Detection Rules supports AWS CloudTrail management events and Runtime Monitoring events. When observed activity matches a rule, GuardDuty generates a _signal_. A signal represents a single observed occurrence of the activity that the rule detects.
Diff
diff --git a/guardduty/latest/ug/custom-detection-rules-how-it-works.md b/guardduty/latest/ug/custom-detection-rules-how-it-works.md index bb42583..b3c7169 100644 --- a//guardduty/latest/ug/custom-detection-rules-how-it-works.md +++ b//guardduty/latest/ug/custom-detection-rules-how-it-works.md @@ -15 +15,24 @@ Begin by browsing the rules that GuardDuty offers to identify the ones that dete -After you associate a rule, GuardDuty monitors the data sources that the rule depends on and evaluates the incoming logs for matching events. Custom Detection Rules currently supports AWS CloudTrail management events. When observed activity matches a rule, GuardDuty generates a _signal_. A signal represents a single observed occurrence of the activity that the rule detects. +After you associate a rule, GuardDuty monitors the data sources that the rule depends on and evaluates the incoming logs for matching events. Custom Detection Rules supports AWS CloudTrail management events and Runtime Monitoring events. When observed activity matches a rule, GuardDuty generates a _signal_. A signal represents a single observed occurrence of the activity that the rule detects. + +Each data source has its own requirements: + +AWS CloudTrail management events + + +GuardDuty analyzes these events in every account where GuardDuty is enabled. No additional setup is required. + +Runtime Monitoring events + + +Runtime Monitoring rules evaluate the process, file, and network activity that the GuardDuty security agent observes on your resources. A Runtime Monitoring rule can match activity only on a resource that meets both of the following requirements: + + * Runtime Monitoring is enabled for the resource type: Amazon EKS, Amazon EC2, or Amazon ECS on Fargate. For more information, see [GuardDuty Runtime Monitoring](./runtime-monitoring.html). + + * The GuardDuty security agent runs on the resource, at or above the rule's minimum agent version for that platform. + + + + +Each Runtime Monitoring rule states the minimum agent version that it requires on each platform where it can run. To view these requirements, call the [GetCustomDetectionRule](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_GetCustomDetectionRule.html) operation. + +If the agent on a resource is older than a rule's minimum version, the rule does not match activity on that resource. GuardDuty does not report an error in this case, so keep the agent up to date on the resources where you enable Runtime Monitoring rules. For information about agent versions, see [GuardDuty security agent release versions](./runtime-monitoring-agent-release-history.html). @@ -32 +55,8 @@ For more information, see [Dry run](./custom-detection-rules-managing.html#custo -GuardDuty aggregates signals that share the same tactic, service, and technique into a single finding. Each finding follows the format `Tactic:Service/Technique`, for example, `Persistence:IAM/AccountManipulation`. A single finding can contain multiple signals when GuardDuty observes the same activity repeatedly from the same principal. +Each finding follows the format `Tactic:Service/Technique`, for example, `Persistence:IAM/AccountManipulation` or `Persistence:Runtime/SuspiciousCommand`. How GuardDuty groups signals into findings depends on the data source that generated the signal, as described in the following list: + + * **AWS CloudTrail rules** – GuardDuty aggregates signals that share the same tactic, service, and technique into a single finding. A single finding can contain multiple signals when GuardDuty observes the same activity repeatedly from the same principal. + + * **Runtime Monitoring rules** – GuardDuty aggregates signals that share the same rule, resource, and process details into a single finding. Each finding covers one resource, such as an instance, a task, or a container. The process details that GuardDuty compares depend on the finding type. For example, file modification findings also compare the file operation and the user that ran the process. A repeat match updates the existing finding instead of creating a new one. Findings from different rules stay separate, even when the rules generate the same finding type for the same resource and process. + + + @@ -38 +68 @@ For more information about the finding structure and fields, see [Custom Detecti -Custom Detection Rules evaluate the fields that AWS CloudTrail records in an event. Redaction happens upstream of GuardDuty. An AWS service can redact the value of a field in the events that it publishes. This redaction protects potentially sensitive data. When a field is redacted, AWS CloudTrail records that the field was present but does not record its value. +AWS CloudTrail rules evaluate the fields that AWS CloudTrail records in an event. Redaction happens upstream of GuardDuty. An AWS service can redact the value of a field in the events that it publishes. This redaction protects potentially sensitive data. When a field is redacted, AWS CloudTrail records that the field was present but does not record its value.