Threat Model Report: Security Considerations for Hardening D...
summary
ControlPlane produces a threat model for Argo CD deployments and finds 19 threats with 6 high priority attack chains mapped into attack trees; the demo uses Argo CD on EKS with Terraform, a Git server, autosync, a Bastion host and Kubernetes service account tokens, and shows how leaking the init admin password or SA token leads to tenant cluster takeover. Recommendations: delete default Argo CD project, use namespace-scoped access and workload identity, protect creds with external KMS and SSO/MFA, and limit repos and app project scope.
AI-written summary · about
chapters (6)
- 0:00Threat modeling Argo CD
- 6:43Threat modeling process
- 14:04Critical data assets
- 18:39Attack trees and threats
- 22:33Security controls
- 24:40Evaluating threat model
related talks
24mThe Hidden Dangers of Defaults: Securing Multi-Tenant Argo CD Install...
31mAttacking Argo CD with Argo CD (and then Defending)
37mThreat Modelling: How to Improve Your Kubernetes Security Posture with Threat Mod...
23mA Practical Guide to ArgoCD Security Gating
32mIntro to Threat Modeling in the Cloud
21mMulti-Tenant ArgoCD with security and isolation
33mAvengers Assemble: Threat Modeling Kubernetes Clusters at a...
34mPrinciple of Least Privilege: How to Secure Kubernetes Without Making Users Hate You