Threat Model Report: Security Considerations for Hardening D...
summary
ControlPlane publishes a threat model and demo repo for an Argo CD multi‑tenant EKS deployment that enumerates 19 threats enumerated with 6 high‑priority paths, uses data flow diagrams and Deciduous attack trees built from STRIDE, and tests a Terraform‑deployed control plane with Git repos, autosync on main, and a Bastion host. Key findings: default Argo CD project and cluster‑wide service accounts increase blast radius; recommended fixes include delete default Argo CD project, use SSO and external KMS and workload identity, and restrict service account tokens and repo/cluster scopes.
AI-written summary · about
chapters (10)
- 0:00Threat modeling Argo CD
- 2:52Threat modeling importance
- 7:05Project scope assumptions
- 10:13Multi-tenant architecture
- 14:04Critical data assets
- 16:33Data flow diagrams
- 18:39Attack trees enumeration
- 21:51Tenant cluster takeover
- 22:34Security controls mitigations
- 24:40Threat modeling effectiveness
related talks
24mThe Hidden Dangers of Defaults: Securing Multi-Tenant Argo CD Install...
37mThreat Modelling: How to Improve Your Kubernetes Security Posture with Threat Mod...
33mAvengers Assemble: Threat Modeling Kubernetes Clusters at a...
32mIntro to Threat Modeling in the Cloud
23mA Practical Guide to ArgoCD Security Gating
31mAttacking Argo CD with Argo CD (and then Defending)
24mScaling Argo Security and Multi-Tenancy in AWS EKS at the New York Times
38mThreat Modelling Kubernetes: A Lightspeed Introduction