Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Identity security has long been built around a simple premise: Authenticate a user, grant access, and trust that decision until their next login. While for many this model worked well enough when identities were primarily human and access patterns were predictable, that’s no longer the case for humans and definitely not the case for AI agents.

Right now, somewhere in your organization, a service account token is sitting in a CI/CD environment variable with access to your entire cloud environment. The job it was created for got deleted three sprints ago, and nobody knows it's still there.

A new CVE drops into a package you depend on. With the JFrog power for Kiro installed, your next move is a single prompt in your IDE, not a tab switch to the JFrog UI and thirty minutes of hand-rolled REST calls. This is what governed agentic development looks like in practice.

Modern IT and security teams no longer evaluate platforms in isolation. They ask how a platform fits into the architecture they run, the workflows they trust, and the outcomes they need to improve. Enterprise stacks are not isolated; they are interdependent. Identity shapes access, endpoint posture influences policy, while SIEM tools drive investigations and rely on shared data and context. AI tools introduce new layers and patterns of usage, risk, and data movement across the network.

Today, we’re launching BlueVoyant AI. In my first months as CEO, I’ve had the chance to meet with many of you. What struck me most is the scope and importance of what you’re protecting, and how seriously you carry that responsibility. What also came through clearly is that your vision for the future of security aligns with ours.

With version 2.3.0, GitProtect brings the long-awaited support for Confluence, SharePoint, and shared mailbox backup. Speaking of DevOps stack protection, your repo copies now feature enhanced granularity and accelerated recovery with automated mapping. Release 2.3.0 also includes a number of stability and performance improvements. Below, you can find a detailed overview of the new features.

Security teams today don’t struggle because they lack visibility. They struggle because every meaningful investigation still depends on too much manual work. An alert fires. Analysts pivot between dashboards. They pull identity context from one tool, endpoint telemetry from another, and threat intelligence from somewhere else entirely. Then comes the response; disabling users, isolating endpoints, resetting passwords, notifying stakeholders, documenting incidents.

The ripple effects of a cyberattack rarely stay contained. Modern organizations rely on vast ecosystems of vendors, suppliers, SaaS providers, and partners. As those connections deepen, so does the potential blast radius of a third-party compromise. What begins as an exposed system or stolen credential inside a vendor environment can quickly cascade across the supply chain. Attackers understand this. Increasingly, they target trusted third parties as an indirect path into larger organizations.

Grid is LimaCharlie's agentic AI layer for security teams that want AI operations running across their existing stack right now. Security providers and SOCs need access to AI capabilities without waiting for a migration window, a contract renewal, or a vendor to ship the features they need. Every major security vendor is offering some version of AI. CrowdStrike has Charlotte AI. SentinelOne has Purple AI. Microsoft has Copilot for Security.

Modern IT environments span on-premises, hybrid and multi-cloud infrastructure, and every new asset added needs to be discovered, evaluated and brought under access control. Discovery tools can surface those resources, but without automation, processing them is slow, inconsistent and prone to error. Critical assets get missed, and security gaps open.