-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Can we implement EKS-AMI hardening? #245
Comments
Did you check why? |
As there AMI has passed the CIS benchmark test. with some agents like Splunk and TrendMicro are Baked into it. As we scanned the Base EKS AMI for CIS benchmarks it got 58%. So we need to go with EKS-AMI hardening where it fails to launch a worker node. |
@khetanvallurupalli We have an issue (#99) for CIS benchmarks, would that cover your use case or are there additional changes? |
it may not be accurate... but I believe there's sort of 2 levels here. Linux ami hardening, and then kube hardening. Both with separate benchmarks from CIS. |
@pthrasher I believe you are correct: Kubenetes hardening: CIS_Kubernetes_Benchmark_v1.4.1.pdf There is no specific and official CIS hardened AMI for EKS that I can find. If anyone else can please point us. |
Hi everyone, |
Looking for aws hardened image, what are the options available currently. |
Nothing official from AWS that I can find, but there are python/ansible scripts that you can search up on Github that are unofficial |
Does anyone has an idea what the status is of this issue? Are there plans to provide hardened images for EKS? |
I am surprised this receives so little attention. |
team, is there any update on this ? is AWS planing to provide a CIS AL2 hardened EKS AMI's which can be used as a part of the cluster node group ? |
In case it helps, this official repo has packer scripts to create custom hardened amis. |
@mmerkes @abeer91 @heybronson is there any way to get AWS feedback on this? |
@pierluigilenoci I'll discuss this with my team and post an update here soon. |
@mmerkes today I read this. https://aws.amazon.com/blogs/containers/introducing-cis-amazon-eks-benchmark/ So is it solved? FYI @burnertoday |
@pierluigilenoci that blog post is about the CIS benchmark for EKS, not about the CIS benchmark for amazonlinux. |
Amazon can you please provide an "official" response on support for EKS Worker CIS OS Benchmark hardening. This is a pain point for many AWS customers. I find it particularly painful since AWS Inspector fails Amazon Linux II for the CIS OS Benchmark. Everyday organizations are demanding secure by default and not something we should have to jump through hoops to make work. All we want is EKS to be secure by default or at least have an option to turn on a more secure implementation. |
is there any update on this, getting alot of customer requests for CIS level 1 for EKS, there seems to be nothing on this. |
any update on this one? I agree with the fact that we're all looking for "secure by default" solution to this hardening issue. |
/push any news on the issue? At least an official response would be helpful. |
I tried my lock with Image builder and CIS benchmark. it wasn't a successful try! |
Please note Bottlerocket AMI is now CIS hardened out of the box 🎉 Amazon Web Services’s Bottlerocket has been certified by the Center for Internet Security® (CIS®) to ship secure as hardened to CIS Bottlerocket Benchmark v1.0.0. Organizations that leverage Bottlerocket can now be assured that it will successfully run on a CIS hardened environment. Please note AWS Inspector Center for Internet Security (CIS) Benchmarks reports does not support Bottlerocket yet as per https://docs.aws.amazon.com/inspector/v1/userguide/inspector_cis.html |
Steps for Building Amazon Linux 2 CIS Benchmark AMIs for Amazon EKS((Level 1 and 2) Specifically about the FAILED/SKIPPED checks, it has been addressed here: There is a section on the bottom for "#cis-scan-results-and-exceptions-for-failed-controls" |
As per Our Infosec team, Every server should be using Hardened AMI according to there policies.
While we do the same for EKS AMI worker nodes are terminated before starting. Any suggestions?
The text was updated successfully, but these errors were encountered: