AWS guardduty: Rewrite GuardDuty Runtime Monitoring end-to-end flow description
Summary
Restructures the 'How Runtime Monitoring works' page from a two-step enable/manage list into a four-step end-to-end flow (agent deployment, event collection, event delivery to GuardDuty, analysis/findings). Removes the note about the VPC endpoint and Instance identity roles authentication (content now linked to a separate agent-connectivity page), adds a note about the agent's bounded CPU/memory usage, and renames several child topic links (e.g. 'How Runtime Monitoring works with ...' -> 'Deploying the security agent to ...', 'After you enable Runtime Monitoring' -> 'Tracking Runtime Monitoring coverage').
Security assessment
The changed line documents a security-relevant property of the GuardDuty Runtime Monitoring agent (runtime events are delivered to the GuardDuty backend and the data remains within the AWS network), which supports threat detection coverage for EC2/EKS/Fargate. However, it is a documentation restructure and link retitle rather than a fix for a specific vulnerability or a new hardening control (the VPC endpoint / instance identity role details were moved to the linked connectivity page), so no incident, CVE, or IAM/permission change is evidenced.
Evidence
+ 3. **The agent sends events to GuardDuty.** The agent delivers the events to the GuardDuty backend. The data remains within the AWS network, and GuardDuty doesn't charge for the events transmitted from your compute resources to GuardDuty. For details, see [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html).
Diff
diff --git a/guardduty/latest/ug/how-does-runtime-monitoring-work.md b/guardduty/latest/ug/how-does-runtime-monitoring-work.md index f87dad2..18dd908 100644 --- a//guardduty/latest/ug/how-does-runtime-monitoring-work.md +++ b//guardduty/latest/ug/how-does-runtime-monitoring-work.md @@ -9 +9 @@ -To use Runtime Monitoring, you must enable Runtime Monitoring and then manage the GuardDuty security agent. The following list explains this two-step process: +Runtime Monitoring uses a lightweight security agent to observe the runtime behavior of your Amazon EC2, Amazon EKS, and Amazon ECS on Fargate workloads and detect threats. It works end to end as follows: @@ -11 +11 @@ To use Runtime Monitoring, you must enable Runtime Monitoring and then manage th - 1. **Enable Runtime Monitoring** for your account so that GuardDuty can accept the runtime events that it receives from your Amazon EC2 instances, Amazon ECS clusters, and Amazon EKS workloads. + 1. **The agent is deployed to your resources.** GuardDuty can deploy and update the agent for you (automated agent configuration), or you can deploy and manage it yourself (manual agent configuration). The steps depend on the resource type. @@ -13 +13 @@ To use Runtime Monitoring, you must enable Runtime Monitoring and then manage th - 2. **Manage GuardDuty agent** for the individual resources for which you want to monitor the runtime behavior. Based on the resource type, you can choose to: + 2. **The agent collects runtime events.** On each monitored resource, the agent observes operating system-level activity, such as process execution, file access, and network connections. @@ -15 +15 @@ To use Runtime Monitoring, you must enable Runtime Monitoring and then manage th - * Use automated agent configuration, where GuardDuty manages the agent deployment and automatically creates a Amazon Virtual Private Cloud (Amazon VPC) endpoint. + 3. **The agent sends events to GuardDuty.** The agent delivers the events to the GuardDuty backend. The data remains within the AWS network, and GuardDuty doesn't charge for the events transmitted from your compute resources to GuardDuty. For details, see [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html). @@ -17 +17 @@ To use Runtime Monitoring, you must enable Runtime Monitoring and then manage th - * Install agent manually, which requires you to create the VPC endpoint as a prerequisite. + 4. **GuardDuty analyzes the events and generates findings.** When it detects suspicious behavior, such as privilege escalation or communication with a known malicious host, GuardDuty generates a finding. To see the up-to-date list of findings that GuardDuty generates, see [GuardDuty Runtime Monitoring finding types](./findings-runtime-monitoring.html). @@ -19 +18,0 @@ To use Runtime Monitoring, you must enable Runtime Monitoring and then manage th -The security agent uses a VPC endpoint to deliver events to GuardDuty, ensuring that the data remains within the AWS network. This approach enhances security and allows GuardDuty to monitor and analyze runtime behavior across your resources (Amazon EKS, Amazon EC2, and AWS Fargate-Amazon ECS). GuardDuty uses [Instance identity roles](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html#ec2-instance-identity-roles) that authenticate the security agent for each resource type to send the associated runtime events to the VPC endpoint. @@ -22,0 +22 @@ The security agent uses a VPC endpoint to deliver events to GuardDuty, ensuring +The agent runs within defined CPU and memory limits, so its resource consumption stays predictable and doesn't degrade the performance or availability of the workloads running on the same host. For these limits, see [Prerequisites to enabling Runtime Monitoring](./runtime-monitoring-prerequisites.html). @@ -24,5 +24 @@ The security agent uses a VPC endpoint to deliver events to GuardDuty, ensuring -###### Note - -GuardDuty analyzes runtime events in your AWS environment, uses them internally for threat detection, and presents the results through findings. - -When you manage the security agent (either manually or through GuardDuty) in EKS Runtime Monitoring or Runtime Monitoring for EC2 instances, and GuardDuty is presently deployed on an Amazon EC2 instance and receives the [Collected runtime event types](./runtime-monitoring-collected-events.html) from this instance, GuardDuty will not charge your AWS account for the analysis of VPC flow logs from this Amazon EC2 instance. This helps GuardDuty avoid double usage cost in the account. +###### Contents @@ -30 +26 @@ When you manage the security agent (either manually or through GuardDuty) in EKS -The following topics explain how enabling Runtime Monitoring and managing GuardDuty security agent works differently for each resource type. + * [Enabling Runtime Monitoring](./runtime-monitoring-enablement.html) @@ -32 +28 @@ The following topics explain how enabling Runtime Monitoring and managing GuardD -###### Contents + * [Deploying the security agent to Amazon EKS](./how-runtime-monitoring-works-eks.html) @@ -34 +30 @@ The following topics explain how enabling Runtime Monitoring and managing GuardD - * [How Runtime Monitoring works with Amazon EKS clusters](./how-runtime-monitoring-works-eks.html) + * [Deploying the security agent to Amazon EC2](./how-runtime-monitoring-works-ec2.html) @@ -36 +32 @@ The following topics explain how enabling Runtime Monitoring and managing GuardD - * [How Runtime Monitoring works with Amazon EC2 instances](./how-runtime-monitoring-works-ec2.html) + * [Deploying the security agent to Amazon ECS on Fargate](./how-runtime-monitoring-works-ecs-fargate.html) @@ -38 +34 @@ The following topics explain how enabling Runtime Monitoring and managing GuardD - * [How Runtime Monitoring works with Fargate (Amazon ECS only)](./how-runtime-monitoring-works-ecs-fargate.html) + * [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html) @@ -40 +36 @@ The following topics explain how enabling Runtime Monitoring and managing GuardD - * [After you enable Runtime Monitoring](./runtime-monitoring-after-configuration.html) + * [Tracking Runtime Monitoring coverage](./runtime-monitoring-after-configuration.html) @@ -53 +49 @@ Runtime Monitoring -With Amazon EKS clusters +Enablement