Skip to content

v0.1.6

Latest

Choose a tag to compare

@marcinc marcinc released this 20 Aug 20:34
· 3 commits to master since this release
fe0d391
  • Krane now reports access granted to unauthenticated callers. Every other subject rule judges a subject by the permissions its roles grant; unauthenticated-subject-access judges it by who it is, reporting any binding to system:anonymous or to the system:unauthenticated group whatever the bound role grants. Binding cluster-admin to system:anonymous, the most damaging RBAC mistake there is, previously produced no finding at all, since every rule filtered out the default roles such a binding tends to reference (#527, closes #339)
  • The anonymous access a cluster legitimately ships with is excluded, so anything reported is actionable: system:public-info-viewer, serving the health and version endpoints, and kubeadm:bootstrap-signer-clusterinfo, serving the cluster-info ConfigMap that kubeadm join discovery reads. Both lists are overridable through custom_params, and adding system:authenticated widens the check to permissions available to every authenticated principal (#527)
  • RBAC installed by a managed control plane is no longer reported as risk. EKS, GKE, AKS and OpenShift all ship their own roles and reconcile them on the operator's behalf, but none carry the kubernetes.io/bootstrapping label Krane used to recognise platform RBAC by, so an EKS report opened with aws-node and eks:addon-manager flagged as danger: findings the reader could neither act on nor suppress. They are now classified alongside the Kubernetes defaults and skipped by the rules that already exclude those (#528, closes #326)
  • Reports on a managed cluster will therefore show fewer findings than under 0.1.5. Detection is marker based rather than a list of role names, which would go stale with each provider release: a role qualifies on a label its provider stamps on the RBAC it owns (eks.amazonaws.com/component, addonmanager.kubernetes.io/mode, kubernetes.azure.com/managedby), or on a name prefix it has reserved (eks:, aws-node, gce:, system:gcp-, system:gke-, aks-, system:azure-, openshift-, system:openshift:). Set TREAT_VENDOR_MANAGED_ROLES_AS_DEFAULT=false, exposed as params.treatVendorManagedRolesAsDefault in the chart, to have vendor RBAC judged like any other (#528)
  • FIX: A rule's info text is interpolated by the dashboard as plain text, so the backticks one rule wrote there reached the reader as literal characters. No shipped rule marks up its info now, and a spec guards it (#527)
  • The shipped risk rules are covered by a spec. Nothing in the suite read config/rules.yaml, so a rule could be edited into a shape that raises, or that silently stops matching, without an example failing (#527)
  • FIX: The custom_params documentation described a list of single-key hashes, while the resolver has always iterated it as a map (#527)
  • The chart, the gem and the raw manifests under k8s/ are pinned to v0.1.6 (#528)