IceKube
IceKube copied to clipboard
WithSecureLabs
https://github.com/kubernetes/kubernetes/issues/119270
Workflows should enforce we have documentation for each attack path defined. Should be a simple check that iterates over attack path names and ensures a relevant markdown file is present...
Current checks are focused around whether any hostPath could expose a path should it exist. For example, `/etc/kubernetes/admin.conf` would check if that or any parent paths are shared into a...
Update logic for relating a pod and its service account to ensure the service account is actually mounted, not solely checking the service account defined in the pod spec.
Need to implement attack paths that leverage the `bind` verb. This would require computing what the resultant permissions would be, and how we would integrate that into the graph. `escalate`...
Need to figure out how to support making attack paths that could have more than one source node as part of the attack. Mainly used when you can compromise two...
Add an attack path to accessing Azure's wireserver. This would need to only be run when the cluster is AKS, else it would be too confusing for all other clusters.
Therre can be secrets in `kube-system` of type `bootstrap.kubernetes.io/token` that contain bootstrap tokens