AI agents now participate directly in daily work. They write code, summarize data, generate documents, and automate tasks at a speed and scale no human can match. As your organization adopts more assistants and autonomous workflows, you introduce a new type of insider: an agent operating inside your systems with real identities, credentials, and privileges. Human and machine activity now blend inside enterprise environments. The shift expands insider risk in ways many teams can’t yet see.

When your CNAPP flags a suspicious dependency in an AI agent container, your WAF logs an unusual API spike, and your SIEM shows a burst of cloud storage calls—are those three separate incidents or one rogue agent attack? Most security teams treat them as three tickets in three queues, investigated by three people who may never connect the dots. By the time someone pieces together that a single compromised agent drove all three signals, the attacker has already moved laterally and exfiltrated data.

What resonated most at RWC 2026? GitGuardian highlights key research on private key leaks, password managers, trusted execution environments, and secret sprawl.

We’re excited to share new updates and enhancements for March, including: For more info on these updates, check out the list below and dive into the detailed articles. Please join the Egnyte Community to get the latest updates, chat with experts, share feedback, and learn from other users.

Your AI-BOM shows every model, tool, and data source you deployed. But when your SOC investigates an alert about unusual agent behavior, that inventory tells them nothing about what actually happened at runtime. Static AI-BOMs document what you intended to run. Attackers exploit what your AI workloads actually do in production: which APIs they call, what data they touch, and how they use approved tools in unapproved ways.

Although Jira serves as the system of record for many DevOps and IT teams, retrieving secrets or approving requests for privileged information often occurs on other platforms. Teams may depend on external tools, email messages or Slack chats to manage credentials or elevation requests, leading to context switching, audit gaps and delays that increase operational risk.

Public sector organizations are operating in a threat environment that is both relentless and increasingly personal. Federal agencies, state and local governments and educational institutions are prime targets for ransomware, phishing, business email compromise (BEC) and credential theft. Local governments alone account for an estimated 43% of ransomware victims in 2025. But the real shift isn’t just in volume. It’s in tactics. Attackers have stopped trying to break in.

Exactly 8 years ago today, we launched the 1.1.1.1 public DNS resolver, with the intention to build the world’s fastest resolver — and the most private one. We knew that trust is everything for a service that handles the "phonebook of the Internet." That’s why, at launch, we made a unique commitment to publicly confirm that we are doing what we said we would do with personal data.

If the public sector had unlimited cybersecurity budgets and fully staffed SOCs, today’s threat landscape would look very different. But that’s not reality. Public sector organizations face chronic staffing shortages, constrained budgets and compensation structures that make it difficult to recruit and retain cybersecurity talent. Meanwhile, adversaries are accelerating their attacks. The result? Small teams carrying massive responsibility.