[EKS] [request]: Automated EKS CIS benchmarking of nodes
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Assessing compliance of EKS CIS standards into standard AWS security services**
Having a overall view of infrastructure configuration from a security perspective in a single place is valuable. kube-bench scores compliance of EKS configuration against the EKS CIS standard. However, running the eks benchmark against EKS deployments is manual and not available through an AWS managed component. It would be great if CIS EKS could be executed and findings / results reflected back into security monitoring services - Security Hub provides a great place to aggregate findings from various systems in a single service.
**Which service(s) is this request for?**
EKS (and Fargate?)
Contributor guide
Research direction
Start by reviewing the EKS CIS benchmarking request and how kube-bench currently assesses EKS configuration. Investigate the AWS Security Hub integration point and clarify whether EKS nodes, Fargate, or both are in scope. Done means automated CIS results are collected and reflected as findings in the security monitoring service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100