Going with the (work)flow? Incident Response for Vicious Workflows
summary
Researchers scan Internet-indexed Argo and Airflow instances and find concrete failures: thousands of exposed credentials and API keys (AWS, Azure, GCP, PayPal), a Monero miner running eight months inside an exposed Argo cluster, and attacker-controlled images or a crypto-mining container via Airflow’s code editor. Misconfigurations include Argo’s default server off mode inheriting pod permissions, exposed quickstart.yaml and visible connection extras. Recommended fixes: patch, lock down kubeconfig/quickstart, apply least privilege, and run git-secrets, custodian and magpie.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:34Who are we
- 1:10What are workflows
- 3:12Argo Workflows
- 9:37Airflow
- 16:07How to protect yourself
- 22:01Open source security
- 23:47Favorite open source security tools
related talks
22mUsing Argo Project to Help Elastic infoSec Team in Securing Elastic
20mDemystifying Argo Workflows: An Architectural Deep Dive
44mSecuring CI/CD Pipelines: Exploring Vulnerabilities In Workflows
26mThreat Model Report: Security Considerations for Hardening D...
23mMastering Argo Workflows at Scale: A Practical Guide to Scalability Excellence
23mA Practical Guide to ArgoCD Security Gating
26mThreat Model Report: Security Considerations for Hardening D...
31mPrepare to Be Boarded! A Tale of Kubernetes, Plunder, and Cryptobooty
