~/talk

Know Your Enemy: Mapping Security Risks Using Threat Matrix for Kubernetes

links:none on file
links:none on file
slides:none on file

Microsoft publishes an updated Threat Matrix for Kubernetes that maps concrete TTPs (examples: node-managed identity token theft, CoreDNS configmap poisoning, private registry image theft) and shows how to measure detection coverage using Kubernetes audit logs, image-whitelisting, service/ingress exposure monitoring and node process/cpu/memory checks. A real-world campaign against Kubeflow is analyzed (exposed dashboard → pipeline → legit TensorFlow image pulling a cryptominer from GitHub). Comparison with MITRE ATT&CK for Containers highlights differing inclusion criteria and technique placement. exposed sensitive interfaces

AI-written summary · about

  1. 0:00Intro
  2. 1:42Where did we start?
  3. 3:30Kubernetes threat landscape
  4. 4:33Threat Matrix for Kubernetes
  5. 5:35Examples
  6. 7:57Kubeflow Pipelines campaign
  7. 10:00Measuring the security coverage
  8. 14:17MITRE ATT&CK for Containers
  9. 14:53Which matrix should I use?
  10. 18:36Key takeaways
  11. 19:16Final words
  12. 20:35Useful links
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.