Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The CA/Browser Forum set 47-day certificates as target for 2029. Let’s Encrypt decided to implement it a year earlier. In December 2025, Let’s Encrypt announced their roadmap to cut certificate lifetimes from 90 days to 45 days by February 2028, a full year ahead of the industry mandate. It’s exactly what we’d expect from the CA that made automation mandatory from day one.

What’s the difference between container scanning and container security? Scanning finds vulnerabilities in images before deployment—it’s container auditing, not container security. Real security requires runtime visibility: seeing what processes execute, what network connections occur, and what files get accessed while containers run. Most teams have scanning covered. Most teams are blind at runtime.

What are the three types of cloud compliance tools? Audit-prep platforms (Drata, Vanta) automate evidence collection for certifications. Security posture management/CSPM (Wiz, Prisma Cloud) scan configurations at a point in time. Runtime compliance verification (ARMO, Sysdig) monitors actual workload behavior continuously. Choosing the wrong type means solving for the wrong problem. What is compliance drift and why does it matter? The gap between your last scan and your current state.

When you’re managing a handful of certificates, one big list works fine. Add a few dozen more and things get messy. Add multiple teams or projects and you’ve got a problem. Who should have access to the production certificates? What about staging? Does the contractor working on the marketing site really need to see your internal infrastructure? CertKit now supports multiple applications from our roadmap to help you sort this out.