Sentra announced a $150 million strategic investment led by Capital One Ventures on November 4, 2026, with a Capital One representative joining its board. The company says the money will expand its platform for discovering sensitive data, mapping access and controlling what human and AI identities can reach across enterprise systems.
Existing investors Bessemer Venture Partners, Zeev Ventures, Standard Investments, Munich Re Ventures and Key1 Capital also participated, according to Sentra’s announcement. Co-founder and CTO Ron Reiter describes the financing as a Series C in his accompanying post, a designation also reported by Axios.
The product bet behind the financing deserves more attention than the amount alone. An enterprise agent’s effective power depends heavily on the data permissions behind its credentials. Sentra is pitching a way to govern that access across cloud storage, SaaS applications, data warehouses and on-premises systems before an agent starts working.
Agent Identities Make Old Permission Problems More Urgent
Enterprise data permissions often reflect years of accumulated sharing, group memberships and service-account access. Adding an AI agent introduces another consumer of those permissions, potentially one that searches and retrieves information continuously.
Sentra CEO Yoav Regev says agents can “inherit access to data that hasn't been fully classified or governed.” The company’s proposed response is to connect two inventories: where sensitive information lives, and which identities can reach it, including through inherited permissions. Its announcement explicitly includes people, service accounts and AI agents in that mapping. Sentra’s announcement makes this connection the foundation of its approach.
Consider a hypothetical assistant that searches an internal document repository through a shared service account. Giving that assistant a narrow task does not automatically narrow the account’s permissions. If the account can read unrelated financial records, those records remain within its potential reach unless another control restricts access.
That distinction matters for deployment. A task description tells an agent what it should do; authorization determines what its underlying identity can do.
My view is that identity mapping is the most consequential part of Sentra’s pitch. A sensitive-data inventory becomes much more actionable when a security team can connect each dataset to the people, applications and agents able to access it. The same identity-level concern appears in Zeniteq’s coverage of .
