The Complete Guide to Secret Hygiene for Java and Cloud-Native Engineers
summary
Forensic tour of concrete failures: plain-text Maven settings.xml and effective-settings reveal passwords (Maven 3.9 fixes some leaks), settings-security uses a hardcoded salt so encrypt properly and prefer a master password; git search finds pushed secrets so change credentials rather than rewriting history and add pre-commit scans; Docker layers retain deleted files — use dive to inspect images and adopt a two-stage build as a fast fix (30% of container apps affected); CI/CD prints/base64 leaks require short‑lived tokens and Vault/Spring injection plus actuator sanitization and secret rotation.
AI-written summary · about
chapters (10)
- 0:00Secret hygiene importance
- 5:13Credentials like radioactive material
- 9:46Maven settings XML risks
- 15:04Git secrets leaks prevention
- 22:29Docker layers secret exposure
- 31:13CI/CD pipelines leakage risks
- 38:04Spring Boot Actuator misconfigurations
- 41:01Vault secure secrets management
- 47:02Q&A
- 50:35Summary
related talks
51mWeb application security for developers. Nanne Baars. Java Fest 2020 Online
38mAdventures in Cloud Security: What DevOps Can Learn from a Security Engineer
46mStrengthening Java Apps: Best Practices in Secure Coding for Java Developers
48mThe Hidden Security Hazards in Your Java Stack
26mHow To Keep A Secret
39mAre your secrets secure - How mobile apps are leaking millions of credentials
30mBehind Closed Doors: Managing Passwords in a Dangerous World
56mDiscover the Art of Managing Secrets as a Software Engineer.