Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Reviewing Malicious PRs at Scale with AI

As AI coding assistants accelerate software development, the volume of pull requests at Datadog has grown to nearly 10,000 per week, increasing the risk that malicious changes slip through due to review fatigue. To address this, Datadog built BewAIre, an LLM-powered code review system designed to identify malicious source code changes introduced by threat actors. By reducing approval fatigue for developers while increasing friction for attackers, BewAIre guides human reviewers to the areas where judgment matters most, without slowing developer velocity.

The Fastest-Growing AI Categories in the Enterprise Are Also the Riskiest

Security teams often focus governance efforts on the most popular AI tools. But the real risk question isn't which tools employees use most. It's which tools are growing fastest and what data those tools can reach. New data from Cyberhaven Labs shows that the AI categories posting the largest year-over-year growth numbers are the same categories with privileged access to source code, credentials, customer contracts, and internal architecture.

AI Is Moving Fast in Manufacturing

Artificial intelligence is rapidly becoming embedded across manufacturing environments, from engineering and design to supply chain optimisation and operations. What was once experimental is now being applied in day-to-day workflows, often driven by the need for speed, efficiency, and competitive advantage. Recent research shows that 73% of manufacturing organisations report rapid AI adoption, with 90% ranking AI as a top security priority for 2026. The direction of travel is clear.

How to Harden AI Agents in Cloud Environments: The 9 Capabilities Your Stack Must Provide

Most “hardening” advice for AI agents is a checklist of things to configure before the agent runs. CIS Kubernetes Benchmark gates. Pod Security Standards baselines. NetworkPolicy templates. None of it’s wrong — it’s just one of four phases, the one your stack already covers. The other three are Observe, Enforce, and Reconcile. They’re where AI agents actually get breached, and they’re where most stacks have nothing.

AI Agent Security Performance: Framework for Evaluating Latency, Throughput, and Observability Overhead

Every AI workload security PoC reaches the same conversation. Platform engineering pushes back: the AI team won’t accept extra latency on inference. The security engineer hunts for benchmarks and finds a contradiction. Langfuse publishes 15% overhead. AgentOps publishes 12%. The security vendor quotes 1–2.5%. None is lying. They measure different layers.

AI Agent Incident Response in Cloud-Native Environments: A Playbook for Modern SOCs

It’s 2 a.m. and the SOC has a Tier 3 page. A customer-service agent on the production cluster has just wired refund payments to seven addresses outside the approved disbursement list. The runbook is unambiguous: isolate the pod, image the disk, image the memory, root-cause within 48 hours.

Turn Busywork Into Real Work With Egnyte's AI

It’s Friday afternoon, and you need a quick team update. Five minutes, tops, right? You ping Slack. A few people reply, a few don’t. So, you schedule a “quick sync” to get everyone on the same page. Two hours later, you’ve spent your afternoon chasing updates instead of doing actual work. And you’ll do it all over again next week. Now picture this. You’re collecting product demo videos for an agency.

AI Is Replacing Security Dashboards (Headless Cloud Security Explained)

AI is changing cloud security—and dashboards might be next to go. In this video, we introduce headless cloud security: a new model where AI agents, not humans, operate security systems. Instead of dashboards and manual triage, security becomes API-driven, automated, and built for autonomous execution. This shift redefines DevSecOps, cloud security, and AI security workflows—moving humans from operators to orchestrators.

AI GitHub Agents: How One Issue Leaked Private Repos

In May 2025, a developer using Claude with the GitHub MCP server asked their AI assistant to do something entirely routine: review the open issues in a public repository. The repository contained a malicious GitHub issue planted by a researcher demonstrating a security vulnerability. The issue contained hidden instructions. The AI read them, followed them, accessed the developer's private repositories, and posted the contents in a publicly visible pull request. No credentials were stolen.