Re:NSA Kubernetes Hardening Guidance [pdf]
by throwaway984393 on Tuesday August 03, 2021 @06:35PM
(#28055075)
This would be less of a concern if the cluster's pods were Firecrackers, yes?
AWS EKS on Fargate has a dedicated ENI and kernel per pod; the only way to intercept the traffic is when it crosses a network, or with flow control logs. Or if somebody hacked the control plane, but that's always "Game over man, game over!"
Re:NSA Kubernetes Hardening Guidance [pdf]
by killjoywashere on Tuesday August 03, 2021 @05:58PM
(#28054756)
And if you've been in that kind of rare environment, those people encrypt everything. They'd encrypt their license plate if they could. You want paranoid, look up laser microphones.
Re:NSA Kubernetes Hardening Guidance [pdf]
by raesene9 on Wednesday August 04, 2021 @03:12AM
(#28058164)
Although with many clusters, compromising a single node is likely to lead to cluster compromise as it allows for all the service account tokens assigned to workloads running on the compromised node to be used by the attacker :)
So always encrypt everything unless you’re in a very rare environment with central network control that cannot be compromised or intercepted from a given machine.