Infisical - January Update

January was a big month for Infisical. We shipped secure AI agent access, certificate approval workflows, expanded secret rotation, real-time events, and major platform hardening. Here’s what changed.

AI agents are becoming part of everyday workflows, but the real challenge isn’t adoption — it’s governance. Giving agents unrestricted access to external tools quickly becomes unauditable and uncontrolled. In January, we expanded Infisical’s agentic capabilities with deeper support for the Model Context Protocol, or MCP. You can now expose MCP tools and servers to AI agents through well-defined endpoints with full activity logging, so you always know what’s being accessed, when, and by whom.

We also added gateway support, which means MCP servers running inside private networks can securely connect back to Infisical Cloud without opening inbound access. With tighter RBAC conditions and OAuth improvements, agent access stays scoped, explicit, and fully revocable.

Issuing certificates is easy. Governing them at scale is where things start to break down. January focused on turning PKI into a first-class, auditable workflow instead of a collection of one-off actions. Certificate requests can now go through structured approval workflows. Just like secrets, you can issue intermediate CAs through certificate policies with clearer defaults and TTL configuration, making it much easier to delegate safely.

There’s also a dedicated certificate requests view with filtering, along with more flexibility around ACME enrollment when you need it. The result is that PKI becomes easier to operate, safer to scale, and much harder to lose track of.

If you manage PKI through Terraform, you can now define your entire certificate hierarchy as code — CAs, policies, and environment profiles — and integrate it directly into your CI pipeline. This makes PKI reproducible, reviewable, and fully infrastructure-as-code.

Secrets don’t just live in cloud APIs. They live on servers, operating systems, and long-running machines. In January, we pushed secret rotation deeper into the infrastructure that teams still manage every day. You can now rotate Unix and Linux local account passwords over SSH, Windows local accounts via SMB and RPC, and third-party API keys like OpenRouter — all automatically.

Rotated secrets are now grouped more clearly in the UI, making it easier to understand what’s managed and what’s actively rotating. This helps eliminate credential sprawl in places that have traditionally relied on manual updates.

Privileged access isn’t just about databases anymore. We expanded privileged access management beyond traditional data stores, bringing just-in-time access and session visibility to more of the stack. You can now grant temporary, auditable access to Kubernetes clusters and Redis databases, alongside existing MySQL, PostgreSQL, and SSH support.

We also strengthened PAM sessions with MFA and WebAuthn, so privileged access stays tightly controlled from start to finish.

Under the hood, January included a revamped event architecture. Infisical now supports real-time subscriptions to secret mutations using Server-Sent Events. That means your systems can listen for secret creates, updates, deletes, and imports as they happen — without polling.

Events are automatically permission-filtered, rate-limited, and kept in sync even as access changes. This unlocks a new class of automation and monitoring workflows that react instantly when secrets change.

Alongside these larger features, January included a wave of identity and security improvements. You can now sign in using WebAuthn for MFA, recover locked accounts more reliably, and organize machine identities into groups as environments grow. We also hardened invitation and authentication flows to reduce abuse and eliminate edge-case failures at scale.

That’s a quick look at what shipped in January.