Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Data in Motion vs. Data at Rest: Why the Model Breaks

Every data security program still gets built around a two-state model: data in motion and data at rest. It made sense when data had a network path you could log and a storage location you could lock down. This approach makes a lot less sense now that the same file can sit at rest in Google Drive one minute and get pasted into a Claude or ChatGPT prompt the next, with no firewall event to mark the handoff.

Cyberhaven: Data Security for the Agentic Enterprise

AI changed work, Cyberhaven protects it. Cyberhaven exists to protect the way enterprises actually work today: with AI agents accessing, moving, and acting on data across every workflow. In this video, we share Cyberhaven's mission and our stance on data security for the agentic enterprise.Traditional data security, built for files at rest, wasn't built for AI agents acting at machine speed. Cyberhaven traces data through its full lifecycle and adapts protection as context changes, so security keeps pace with how work actually happens.

Securing the Agentic Enterprise

We're living through the biggest shift in how work gets done in a generation. In every industry, every company is becoming an agentic enterprise, meaning a business where humans and autonomous AI work side by side. What makes an agentic enterprise successful is its workflows: how it combines intelligence, both human and machine, with its proprietary data.

Endpoint DLP vs SaaS DLP: Choosing the Right Data Protection

Most data loss prevention (DLP) programs start with a budget decision disguised as an architecture decision. Cover the SaaS layer first, since that is where most collaboration tools live, or cover the endpoint first, since that is where users actually act on data. Whichever layer gets funded first tends to become the program's foundation by default, not by design. That default has unintended consequences for data security.

Agent Containment Lessons From OpenAI-Hugging Face Breach

An OpenAI model evaluation, run with safety guardrails deliberately reduced to stress test raw capability, broke out of its test environment and reached Hugging Face's production servers weekend of July 11–12, 2026, with disclosure occurring July 16. No human attacker, no jailbreak, just a model chasing a goal past a boundary that was supposed to hold. Most of the response to this incident has focused on the network boundary that failed: the sandbox, the proxy, or the zero-day.

How Does DLP Detect Data Exfiltration

Most data exfiltration does not look like a policy violation while it is happening. An employee moves a file to a personal cloud account they use every day. A contractor pastes source code into a chatbot to get help debugging. An AI agent with standing access to a shared drive pulls a document into a workflow no one is watching. None of it trips a keyword match, because none of it was written with a banned word in the payload.

Data Discovery vs. Data Classification

Most DLP rollouts stall in the same place. The classifier flags a file as "confidential," but nobody, including the DLP solution itself, can say why, where it came from, or whether that label still matches what's inside the file six months later. Data discovery and data classification get bundled together in nearly every vendor pitch, but they solve different problems, and the gap between them is where false positives, stale labels, and missed exfiltration events live.

You Can Automate Data Security Workflows. You Can't Automate Accountability.

The most pressing security question isn't whether AI will automate your workflows. It's what remains once it does. The answer, consistently, is judgment, and judgment has always belonged to a human. The SEC charged SolarWinds' CISO personally for misrepresenting the company's cybersecurity practices. Uber's CISO was convicted of a federal crime for concealing a data breach.

How Data Security Fits Into a Data Management Framework

Most data management frameworks list security as one component among several, including governance, quality, integration, retention, architecture, and analytics. Security is often treated as an equally weighted checkbox on the same list as the others. That framing is where data security programs start to break down.

Data Lineage vs. Data Provenance: What's the Difference?

Security and governance teams often use "data lineage" and "data provenance" as if they have the same definition and offer the same insights. They don't, and the gap between them shows up fast once a program tries to act on it. A provenance record can tell you where a file came from, but it cannot tell you what happened to it after an employee copied it into a new spreadsheet, renamed it, and uploaded it to a personal cloud drive.

How to Prevent AI Agents from Exfiltrating Sensitive Data

An AI agent on a developer's laptop has read access to a code repository, a set of internal documents, and an external model. Nobody approved that specific combination, and nobody is watching what the agent does with it session to session. The agent is not malicious, however, it is doing exactly what it was configured to do. But, that configuration is the exposure, and most security teams do not have a way to see it, let alone stop it before sensitive data leaves the environment.

Agentic AI Governance Requires a New Enforcement Model

AI has swiftly shifted from a browser-based chat interface to an autonomous actor operating within enterprise environments. Agents run locally on endpoints, inherit employee permissions, access sensitive data in bulk, and execute multi-step workflows with no human approving each step. That shift fundamentally changes the enforcement surface. The governance programs most organizations have built were designed for a different model: one user, one prompt, one decision.

How to Protect R&D Data During M&A

Mergers and acquisitions (M&A) concentrate risk into a narrow window. The moment a deal is announced, employees with access to proprietary research, source code, and unreleased product plans face pressure and opportunity at the same time. Some update their resumes. A smaller number decide to take something with them: a research file, a pricing model, or a customer list before the transition is final. For compliance and security teams, the challenge goes beyond stopping data exfiltration.

Microsoft Purview DLP Limitations and How to Close Them

Security teams that roll out Microsoft Purview DLP inside their Microsoft ecosystem often assume coverage extends further than it does. Policies apply cleanly to Word, Excel, and Outlook. Then a sensitive.dwg is inspected only by extension because Purview doesn't scan CAD content, a developer on a Linux workstation falls outside endpoint coverage entirely, or raw source code moves to a USB drive without matching the source-code classifier, which runs on the endpoint only for Office and PDF files.

How to Secure AI Agents in the Enterprise: A Practical Guide for CISOs

Building guardrails for AI agents sounds like a policy problem but it is actually a data problem. You cannot enforce boundaries on behavior you cannot see. And you cannot govern identity for actors you have not discovered. That dependency chain is what most enterprise security programs miss in 2026, and it is where exposure quietly accumulates. A human employee who mishandles sensitive data creates a containable event. An AI agent with the same permissions creates a different problem.

How to Prevent Data Leakage to GenAI Applications

An analyst pulls up the DLP console expecting to see alerts on the source code, customer records, and financial data employees paste into ChatGPT, Copilot, and a dozen other AI tools every day. Instead, the console is quiet, because the policies enacted by the legacy DLP system were built to catch file transfers and email attachments. But, none of the above traffic looks like a file transfer.

5 Common AI Governance Mistakes Enterprises Make

Enterprise AI adoption has outpaced enterprise AI governance. Seventy-eight percent of organizations now use AI in at least one business function, up from 55% the year before, and most of that adoption happened before governance teams finished drafting their first policy. The result is a familiar pattern: leadership approves a rollout, security builds guardrails around the tools it knows about, and sensitive data keeps moving through channels nobody mapped.

How to Build a Red Team Exercise for AI Workflows

AI agents now retrieve data, generate recommendations, and trigger actions across enterprise systems with little human review in between. That speed is the point, and it is also the problem. A single manipulated prompt or a poisoned data source can push an AI system toward a decision no one signed off on, and most security teams have never tested for it. Building a red team exercise for AI workflows is how you find that gap before an attacker does.

Implementing AI Security: Your Enterprise LLM Security Checklist

Security teams are approving large language model (LLM) deployments faster than they can build the controls necessary to govern them and protect vital, sensitive data. Employees paste customer records into ChatGPT, engineering teams connect internal APIs to coding assistants, and business units stand up retrieval systems against production data, often without formal review.

CASB vs DLP: Key Differences and When to Use Each

Security leaders evaluating cloud access security broker (CASB) and data loss prevention (DLP) tools often discover the two categories overlap just enough to create budget friction and just little enough to leave real gaps. A CASB can flag risky file-sharing behavior in Salesforce without ever inspecting the content inside the file. A traditional DLP tool can classify that same file as containing source code without knowing whether the sharing link is public.