Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Shadow AI Explained: What It Is, Where It Hides, and What It Costs

Shadow AI is the term for AI tools, models, and capabilities that operate within an organization without formal approval, oversight, or governance. It is the enterprise AI equivalent of shadow IT, which is the unauthorized software and cloud services that proliferated as employees found faster ways to get work done than waiting for IT procurement cycles. The difference is that the consequences of unmanaged AI are considerably more significant than those of unmanaged software.

How to Discover and Control Shadow AI Agents in Your Environment

Most security programs have a working model for responding to shadow AI: identify the unsanctioned tools employees are using, sanction or block them, and update the acceptable use policy. That model worked, however imperfectly, when the threat was limited to web-based GenAI applications. It does not work when the threat is an autonomous agent, running locally on an endpoint, that reads the file system, calls external APIs, and transmits internal data.

A double-edged bleeding edge: Classifying AI threats

Sophos X-Ops presents a working taxonomy for attacks using, and targeting, AI Conversations about ‘AI threats’ typically collapse into one of two extremes. On the one hand, hype: unverified claims that don’t hold up to scrutiny and invite significant criticism. On the other, dismissal: it’s just old tradecraft with new branding.

From prompt to action: Al Security with Salt Security and CrowdStrike

As enterprises accelerate adoption of Generative AI, the security perimeter is rapidly expanding. This creates a new, largely unprotected attack surface: the Agentic Action Layer. In this on-demand webinar, @CrowdStrike and Salt Security introduce an AI-native security architecture that spans the full chain of intent-to-action. Learn how CrowdStrike Falcon AIDR protects the model runtime, prompts, inference, and LLM behavior, while Salt Security governs and defends the APIs, MCPs, and services where AI actions actually occur.

How Retailers Can Build a Security Strategy for AI Shopping Assistants

AI shopping assistants have moved well past novelty. Deloitte reports that 63% of global retailers now agree that companies without AI agents will fall behind within two years. These systems already handle product discovery, purchase recommendations, loyalty redemptions, autonomous checkout sequences, and more.

Scaling security reviews at 1Password: Building an AI-powered pipeline

The developers and engineers here at 1Password are always working to improve our products. With all the active development to introduce features, fix bugs, and enhance the overall user experience, numerous code changes go into every release. We strive to ensure each iteration is better than the last and that new code doesn’t introduce vulnerabilities. A key part of this process is our Product Security (ProdSec) team’s review of all code changes that may have security implications.

Claude Tag Didn't Create Another Identity Problem. It Created a Control Risk.

Anthropic’s Claude Tag represents a meaningful shift in how AI agents operate inside the enterprise. Unlike traditional AI assistants that act on behalf of an individual user, Claude Tag introduces a shared AI agent with its own identity, credentials, service accounts, and permissions. That shared agent lives inside a Slack channel, builds context over time, connects to enterprise systems, and performs work for everyone in the conversation.

What Is Agentic AI Security? Why AI Agents Need a New Security Model

AI systems are starting to do more than generate answers. Across customer support, IT operations, software development, and internal business workflows, organizations are deploying AI agents that can retrieve information, use tools, interact with applications, and complete tasks with limited human involvement. This shift is happening quickly. According to a McKinsey Report, 62% of organizations are already experimenting with AI agents, while 23% are actively scaling them across parts of their business.

Snyk VulnBench JS 1.0: Can LLMs Find the Same Bugs Twice?

We ran 300 vulnerability-finding scans to measure how repeatable an agentic LLM security review is on the same code, prompt, and harness. The headline result is not that one scanner "wins" a self-referential leaderboard. It is that LLM security findings are unevenly repeatable: reference-matched findings were stable, but extra-model reports varied widely from run to run.