Amazon GuardDuty expands Prolonged Risk Detection protection to Amazon EKS clusters

Immediately, I’m completely happy to announce Amazon GuardDuty Prolonged Risk Detection with expanded protection for Amazon Elastic Kubernetes Service (Amazon EKS), constructing upon the capabilities we launched in our AWS re:Invent 2024 announcement of Amazon GuardDuty Prolonged Risk Detection: AI/ML assault sequence identification for enhanced cloud safety.

Safety groups managing Kubernetes workloads typically wrestle to detect subtle multistage assaults that focus on containerized purposes. These assaults can contain container exploitation, privilege escalation, and unauthorized motion inside Amazon EKS clusters. Conventional monitoring approaches may detect particular person suspicious occasions, however typically miss the broader assault sample that spans throughout these totally different information sources and time intervals.

GuardDuty Prolonged Risk Detection introduces a brand new important severity discovering kind, which robotically correlates safety indicators throughout Amazon EKS audit logs, runtime behaviors of processes related to EKS clusters, malware execution in EKS clusters, and AWS API exercise to determine subtle assault patterns which may in any other case go unnoticed. For instance, GuardDuty can now detect assault sequences wherein a menace actor exploits a container software, obtains privileged service account tokens, after which makes use of these elevated privileges to entry delicate Kubernetes secrets and techniques or AWS assets.

This new functionality makes use of GuardDuty correlation algorithms to watch and determine sequences of actions that point out potential compromise. It evaluates findings throughout safety plans and different sign sources to determine widespread and rising assault patterns. For every assault sequence detected, GuardDuty supplies complete particulars, together with probably impacted assets, timeline of occasions, actors concerned, and indicators used to detect the sequence. The findings additionally map noticed actions to MITRE ATT&CK® ways and methods and remediation suggestions primarily based on AWS greatest practices, serving to safety groups perceive the character of the menace.

To allow Prolonged Risk Detection for EKS, you want no less than one in all these options enabled: EKS Safety or Runtime Monitoring. For optimum detection protection, we suggest enabling each to boost detection capabilities. EKS Safety screens management aircraft actions by audit logs, and Runtime Monitoring observes behaviors inside containers. Collectively, they create a whole view of your EKS clusters, enabling GuardDuty to detect complicated assault patterns.

The way it works
To make use of the brand new Amazon GuardDuty Prolonged Risk Detection for EKS clusters, go to the GuardDuty console to allow EKS Safety in your account. From the Area selector within the upper-right nook, choose the Area the place you wish to allow EKS Safety. Within the navigation pane, select EKS Safety. On the EKS Safety web page, overview the present standing and select Allow. Choose Verify to save lots of your choice.

After it’s enabled, GuardDuty instantly begins monitoring EKS audit logs out of your EKS clusters with out requiring any further configuration. GuardDuty consumes these audit logs instantly from the EKS management aircraft by an unbiased stream, which doesn’t have an effect on any current logging configurations. For multi-account environments, solely the delegated GuardDuty administrator account can allow or disable EKS Safety for member accounts and configure auto-enable settings for brand new accounts becoming a member of the group.

To allow Runtime Monitoring, select Runtime Monitoring within the navigation pane. Underneath the Configuration tab, select Allow to allow Runtime Monitoring to your account.

Now, you possibly can view from the Abstract dashboard the assault sequences and important findings particularly associated to Kubernetes cluster compromise. You may observe that GuardDuty identifies complicated assault patterns in Kubernetes environments, resembling credential compromise occasions and suspicious actions inside EKS clusters. The visible illustration of findings by severity, useful resource affect, and assault sorts offers you a holistic view of your Amazon EKS safety posture. This implies you possibly can prioritize essentially the most important threats to your containerized workloads.

The Discovering particulars web page supplies visibility into complicated assault sequences concentrating on EKS clusters, serving to you perceive the total scope of potential compromises. GuardDuty correlates indicators right into a timeline, mapping noticed behaviors to MITRE ATT&CK® ways and methods resembling account manipulation, useful resource hijacking, and privilege escalation. This granular degree of perception reveals precisely how attackers progress by your Amazon EKS surroundings. It identifies affected assets like EKS workloads and repair accounts. The detailed breakdown of indicators, actors, and endpoints supplies you with actionable context to know assault patterns, decide affect, and prioritize remediation efforts. By consolidating these safety insights right into a cohesive view, you possibly can rapidly assess the severity of Amazon EKS safety incidents, cut back investigation time, and implement focused countermeasures to guard your containerized purposes.

The Sources part of the Discovering particulars web page exhibits context concerning the particular belongings affected throughout an assault sequence. This unified useful resource record supplies you with visibility into the precise scope of the compromise—from the preliminary entry to the focused Kubernetes parts. As a result of GuardDuty consists of detailed attributes resembling useful resource sorts, identifiers, creation dates, and namespace data, you possibly can quickly assess which parts of your containerized infrastructure require rapid consideration. This centered strategy eliminates guesswork throughout incident response, so you possibly can prioritize remediation efforts on essentially the most important affected assets and decrease the potential blast radius of Amazon EKS focused assaults.

Now obtainable
Amazon GuardDuty Prolonged Risk Detection with expanded protection for Amazon EKS clusters supplies complete safety monitoring throughout your Kubernetes surroundings. You should use this functionality to detect subtle multistage assaults by correlating occasions throughout totally different information sources, figuring out assault sequences that conventional monitoring may miss.

To start out utilizing this expanded protection, allow EKS Safety in your GuardDuty settings and contemplate including Runtime Monitoring for enhanced detection capabilities.

For extra details about this new functionality, confer with the Amazon GuardDuty Documentation.

— Esra