AWS EKS Access Entry Granted Cluster Admin Policy
Description
Detects when the AmazonEKSClusterAdminPolicy or AmazonEKSAdminPolicy is associated with a principal via the EKS Access Entries API. This grants full cluster-admin equivalent access to the specified IAM user or role. Unlike the legacy aws-auth ConfigMap which is only visible in Kubernetes audit logs, Access Entries modifications appear in CloudTrail, providing an additional detection surface. Attackers who have obtained IAM permissions to manage EKS access entries can use this API to backdoor cluster access for persistence, mapping attacker-controlled IAM identities to cluster-admin privileges without modifying any Kubernetes resources.
Query · kuery
data_stream.dataset:"aws.cloudtrail" and event.provider:"eks.amazonaws.com" and event.action:"AssociateAccessPolicy" and event.outcome:"success" and aws.cloudtrail.request_parameters:(*AmazonEKSClusterAdminPolicy* or *AmazonEKSAdminPolicy*)
Investigation fields
Pivot points the source recommends for triage.
@timestampuser.nameuser_agent.originalsource.ipaws.cloudtrail.user_identity.arnaws.cloudtrail.user_identity.typeevent.actionevent.outcomecloud.account.idcloud.regionaws.cloudtrail.request_parametersaws.cloudtrail.response_elements
Known false positives
- Platform or security teams may legitimately associate these policies during cluster onboarding, break-glass admin setup, or controlled RBAC migrations from aws-auth. Validate the caller, change ticket, and target IAM principal.
Analyst notes
Investigating AWS EKS Access Entry Granted Cluster Admin Policy
Successful AssociateAccessPolicy with AmazonEKSClusterAdminPolicy or AmazonEKSAdminPolicy binds highly privileged Kubernetes access to an IAM principal. Review who invoked the API (user.name, aws.cloudtrail.user_identity fields), source.ip, user_agent.original, cloud.account.id, and cloud.region.
Possible investigation steps
- Parse aws.cloudtrail.request_parameters and response elements for cluster name, access entry ARN, and policy ARN.
- Confirm whether the IAM principal receiving the policy is expected to have cluster-admin-class access.
- Correlate with other EKS API calls (CreateAccessEntry, UpdateAccessEntry) and with Kubernetes audit activity from newly authorized principals.
- Compare against change records for migrations from aws-auth or new administrator onboarding.
Response and remediation
- If unauthorized, disassociate the policy or remove the access entry per AWS guidance; audit who can call eks:* APIs in IAM.
- Rotate credentials for any suspected compromised IAM principal; review organizational SCPs and cluster auth mode.