BEGIN:VCALENDAR
VERSION:2.0
PRODID:Data::ICal 0.24
BEGIN:VEVENT
DESCRIPTION:   'Title: cloud-auth: a provider-agnostic CLI for cross-cloud 
 workload\n   identity\n   Tags: Demo 💻 | Cloud Village | Creator Talk/P
 anel\n   When: Saturday\, Aug 8\, 14:50 - 15:20 PDT\n   Where: LVCCW Level
  3 W313 (Cloud Village Talks) - [1]Map\n\n   Description:\n\n   Modern eng
 ineering teams don't live in one cloud. A workload in Google\n   Kubernete
 s Engine needs to read from an S3 bucket. An EC2 instance\n   needs to fet
 ch a secret from Azure Key Vault. A single GitHub Actions\n   job has to d
 eploy to AWS\, log telemetry to GCP\, and trigger a workflow\n   in Azure 
 — all in the same run. The default way teams make this work\n   is the s
 ame way they have for a decade: paste a long-lived credential\n   into a s
 ecret and hope nobody finds it.\n\n   This is the credential sprawl proble
 m at the heart of every\n   multi-cloud breach. Static AWS access keys\, G
 CP service account JSON\n   files\, Azure client secrets — the most reli
 ably exploited foothold\n   in cloud environments\, sitting in env vars\, 
 secret managers\, and\n   committed git history across every blue team's e
 nvironment.\n\n   Why this was hard before cloud-auth? In theory\, every m
 ajor cloud\n   already supports a way to skip the static credential entire
 ly. A GKE\n   pod can assume an AWS IAM role directly — no AWS keys anyw
 here. An\n   EC2 instance can call Azure with no service principal on it. 
 A\n   Kubernetes workload can hit GCP APIs with no service account JSON\n 
   file. In practice\, each cloud has its own model\, API\, and failure\n  
  modes. Setting up just one of these connections means learning a new\n   
 mental model\, authoring trust documents with provider-specific subject\n 
   formats\, and validating it all by hand. Doing it across clouds means\n 
   doing that work three or four times over\, with no consistent way to\n  
  set it up\, validate it\, or clean it up. That friction is why\n   cloud-
 auth exists. The secure path is already supported by the clouds\n   — de
 fenders just need tooling that makes it as easy as pasting an\n   access k
 ey\, or easier. So most teams stay on static keys.\n\n   cloud-auth: cross
 -cloud workload identity for defenders cloud-auth is\n   an open-source CL
 I and library that gives blue teams one consistent\n   way to set up\, val
 idate\, and safely retire cross-cloud workload\n   identity. One command s
 tands up the trust between any two of: AWS\,\n   GCP\, Azure\, HashiCorp V
 ault\, Cloudflare\, GitHub Actions\, and\n   Kubernetes. The same command 
 validates it\, previews changes before\n   applying\, and tears it down wi
 thout touching anything it didn't\n   create.\n\n   Live demo GKE pod → 
 AWS S3\, no AWS keys. A GKE pod reads from S3\n   using a short-lived AWS 
 role. EC2 → Azure Key Vault\, no service\n   principal. An EC2 instance 
 fetches a secret with no Azure client\n   secret on it. GitHub Actions →
  AWS\, GCP\, and Azure in one workflow.\n   A single CI job deploys across
  three clouds. Catching a misconfigured\n   trust. The validator flags an 
 overly permissive trust before it ships.\n   Safe teardown. Dry-run a mult
 i-cloud cleanup\, then execute. cloud-auth\n   only deletes what it create
 d.\n\n   What attendees leave with? A working open-source tool\, a concret
 e\n   pattern for cross-cloud workload identity\, and a validation framewo
 rk\n   to drop into existing CI/CD. Repository:\n   https://github.com/ani
 rudhbiyani/cloud-auth (LGPL-3.0)\n\n   SpeakerBio:  Aniruddha Biyani\n\n  
  Aniruddha "AB" Biyani leads the Security and Compliance program at\n   Pr
 ophecy\, where he focuses on building security as a business enabler\n   f
 or high-growth cloud and AI platforms. His work centers on scaling\n   inf
 ormation security programs\, strengthening cloud and identity\n   security
 \, enabling secure product development\, and aligning security\n   strateg
 y with customer trust\, compliance\, and engineering velocity. He\n   has 
 previously held security roles at Mandiant\, Securonix\, CRED\, and\n   Kh
 oros.\n\n   AB's career spans cloud security leadership across startups an
 d\n   cybersecurity vendors\, with deep experience in defensive cloud\n   
 engineering\, identity and access management\, secure developer\n   enable
 ment\, and operationalising secure-by-default practices in\n   fast-moving
  organizations. He is known for translating complex\n   security challenge
 s into practical programs\, tools\, and frameworks\n   that help engineeri
 ng teams move quickly while reducing risk.\n\n   AB has presented at globa
 l security conferences including Black Hat\n   Arsenal\, SANS CloudSecNext
 \, and MCPDev BLR\, on workload identity\,\n   multi-cloud attack surface 
 discovery\, credential lifecycle management\,\n   and secure cloud adoptio
 n at scale. He is also an active open-source\n   contributor and community
  builder\, maintaining cloud security tools\n   and secure developer train
 ing resources. He previously served for\n   three years as a core DEF CON 
 Cloud Village CTF volunteer\, leading\n   contest design and build efforts
 .\n\n   '\n\n   1. #LVCCW_Level3_South\n\n\n
DTEND:20260808T222000Z
DTSTART:20260808T215000Z
LOCATION:Cloud Village - LVCCW Level 3 W313 (Cloud Village Talks)
SUMMARY:cloud-auth: a provider-agnostic CLI for cross-cloud workload identi
 ty
END:VEVENT
END:VCALENDAR