Every story tagged Secrets Management, curated for CIOs and IT leaders — ranked by source credibility, engagement, and freshness.
3 stories · open in the command center
Kloak is an agentless Kubernetes security solution that uses eBPF to intercept HTTPS traffic and replace secret placeholders with actual credentials at the network edge, ensuring applications never directly access sensitive data and eliminating a major attack surface for credential theft. This approach delivers enterprise-grade secret management without code changes, sidecar overhead, or latency impact, while maintaining compatibility with standard Kubernetes Secrets and requiring only simple YAML labels for enablement. For IT organizations, Kloak reduces operational complexity and security risk by shifting secrets enforcement from application-layer to kernel-layer, significantly lowering the blast radius of compromised workloads.
Keycard is a new security tool that enables developers to inject API keys directly into application subprocesses without exposing them through shell environment variables, reducing the attack surface for credential theft. This approach addresses a critical vulnerability in traditional environment variable-based secrets management, where credentials can be inadvertently logged, exposed in process listings, or leaked through debugging tools. By preventing secrets from entering the shell environment entirely, Keycard offers a more secure alternative for credential management in development and production workflows.
Keeper is an embedded secret management library for Go applications that provides cryptographic storage of secrets at rest using industry-standard encryption (XChaCha20-Poly1305) with flexible security levels ranging from automatic startup unlock to HSM and remote KMS integration. For IT organizations, this represents a shift toward decentralized secret management embedded directly in applications rather than external vaults, reducing operational overhead while enabling fine-grained per-bucket access control and audit trails. The strategic implication is that development teams can now implement hardened secret management without external dependencies, though IT must establish clear policies around when embedded stores are appropriate versus centralized KMS solutions.