Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The bell rings. Last call for 398-day certificates is March 15. After that, every CA is required to cut you off at 200 days. Some have already stopped serving them early. The rest follow in two weeks. The irony of good certificate management is that when it works, nobody notices. No alerts, no outages, no 2am pages. The only time it gets attention is when something expires. Which means the teams doing it well rarely have the budget or the political capital to fix the process before it breaks.

Why does traditional Kubernetes security fall short? Static scanners flag thousands of CVEs but can’t tell you which ones are actually loaded into memory and exploitable—only about 15% are loaded at runtime. Traditional tools also create siloed visibility, with CSPM, vulnerability scanners, and EDR each seeing only one slice of your environment. This makes it impossible to spot lateral movement or connect events across cloud, cluster, container, and application layers.

AI is not just another workload category. It is the first category of workloads that decides what to do at runtime. And that changes everything about how security must work in the cloud. For years, cloud security evolved around deterministic systems. You deploy code. That code follows defined logic paths. If something unexpected happens, such as a new process, an unusual outbound connection, or privilege escalation, you investigate and respond.

Here at ARMO, our customers run production Kubernetes clusters that face the open internet every day. That’s the reality of modern cloud-native infrastructure — your ingress controllers, API gateways, and load balancers are the front door, and threat actors are constantly rattling the handle.

AI risk management is the process of identifying, assessing, and mitigating risks associated with artificial intelligence systems to ensure they are developed and used responsibly. It involves using frameworks like the NIST AI Risk Management Framework to address technical, ethical, and social challenges, including data bias, privacy violations, and security vulnerabilities.

The CertKit Agent 1.6 is out. Three things in this release, all of them coming from the same underlying problem: the shorter certificate lifespans get, the more certificate deployment has to behave like real software deployments.