⚡Lightning Talk: Airgap-native Identity Management: Lessons From Keycloak in DoD Deployments
summary
Zarf creates a Zarf single-file ZST bundle from container images, Helm charts and a zarf.yaml manifest, Zarf init injects an internal registry (via configmap image URL overrides) and Zarf package deploy pushes and Helm-installs Keycloak in an air-gapped cluster. Keycloak uses a Keycloak X.509 authenticator plus custom client authenticators and policies to treat CACs as CAC as MFA with unique CAC_ID attribute, validating against DoD/federal PKI, requiring header sanitization, producing SBOMs, and integrating with Istio/Authservice for full network lockdown.
AI-written summary · about
related talks
42mExploring Best Practice for Implementing Authn and Authz in a Cloud-Native...
36mSecuring Agentic Platforms with Zero-Trust Workload Identities
23mKeynote: Cloud & Cloud Native Identity and Access Management: Challenges & Opportunities
21mDon't Be Afraid to Operate Alone! The ABCs of Authentication Infrastructure Management
45mZero Trusting as a True Cloud Native Dev
31mFast & Secure: Package, Sign, Verify, and Deploy
05mLightning Talk: Don’t Make Me Impersonate My Identity
19mKeynote: Demystifying Secure Application Communication with Zero Trust: Identity, Integri...