-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
THREAT-413 - Tune EKS Anonymous API Access Detection Rule (#1405) #1433
Conversation
@bcpenta we noticed some noise with this rule when we deployed it to our lab environment. Please take a look at the tuning changes and let us know if you have any questions! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to hold off on merging until we get those sample logs where objectRef is missing - I suspect the tuning improvements will probably exclude those events, but would like to confirm before we merge this!
Old title: New title: |
Tuned version of #1405
Background
This change introduces a new detection rule for identifying anonymous API access to the Kubernetes API server in Amazon EKS clusters. Anonymous access should be disabled in production environments to prevent unauthorized access, as it poses a potential security risk. Detecting anonymous requests helps ensure that EKS clusters are properly configured for secure API usage.
Changes
Testing