Vero Security Raised $11 Million Because Most Companies Haven't Decided Who Secures Their AI Agents. Yours Probably Hasn't Either
Vero Security, a New York and Tel Aviv startup founded in 2025, raised an $11 million seed round led by TLV Partners for software that turns a security team's AI policies into enforced controls on employees' AI tools and agents. What it does, why investors are funding the category, and the questions every New York company using AI agents should be asking.

NEW YORK — Employees are connecting AI assistants and coding agents to company email, code repositories and customer data faster than most companies can write a policy about it. A young New York and Tel Aviv startup has raised money on the premise that somebody needs to own that problem full-time.
Vero Security announced $11 million in seed funding on Nov. 18. TLV Partners led the round, with participation from GTM Capital, Maple Capital and angel investors. Founded in 2025, the company says it already counts multiple Fortune 500 companies as customers and has offices in New York and Tel Aviv.
The Problem: A Job Nobody Was Hired For
Vero calls its category “AI Security Engineering”: the ongoing work of securing the AI tools and agents employees use. The company’s pitch rests on an organizational gap. Citing research from IANS and Artico Search, Vero says 65% of companies with at least $10 billion in revenue had assigned someone to lead AI security, but only 18% had made it a dedicated role. Everywhere else, it was added to an existing leader’s job.
And the target keeps moving. Employees adopt new tools and grant agents permission to read sensitive data and take actions, while AI vendors keep shipping new models, plugins and integrations that can change the risk of settings that were safe last month.
“CISOs have seen enough dashboards and tables that tell their teams what’s wrong and leave the work to them,” said Elad Tessler, Vero’s co-founder and CEO, in the announcement.
What Vero Does
Instead of just flagging risks, Vero says it does the follow-through. A security team sets a policy and decides which changes Vero may make on its own. Vero then turns that policy into controls, works through the endpoint, identity, AI and security tools a company already runs (so employees have nothing new to install), and updates those controls as vendors change their products. Decisions that need a human come back to the security team with analysis and a recommendation.
At the center is what the company calls its AI Runtime Governor, which inspects supported prompts, tool calls and agent actions and enforces policy when an action is attempted. Vero says it can stop a coding agent from reading secrets it has no reason to touch, block agent actions that break policy, and keep malicious “skills” or prompt injection from triggering unauthorized behavior.
The company gave one example: a new Fortune 1000 customer started with a single rule, that only developers could connect AI agents to corporate code repositories or let them execute code. Vero says it translated that into more than 15 controls across coding agents, MCP servers, skills, identities and runtime actions within minutes. That’s the company’s account; we haven’t independently verified it.
Vero is also launching AISecurityEngineering.org, an open community with field guides, workshops and a credential track for people taking on the role.
The Team and the Money
Tessler previously led product at Astrix Security, which Vero says was acquired by Cisco in 2026. Co-founder and CTO Daniel Meirov was the first employee at Sightfull, where he led R&D and product. The two met in the Israeli military’s Unit 8200, where they co-led a cyber operations unit of more than 100 people, according to the company.
GTM Capital said it invested after a structured evaluation with its community of Fortune 500 CIOs and CISOs. Vero says it will use the funding to expand coverage across enterprise AI tools and security workflows and grow its go-to-market presence in the United States.
Why New York Companies Should Pay Attention
Vero sells to big enterprises, but the question it’s built around applies to a 20-person agency or a Series A startup just as much: when an AI agent can read your files and act on your behalf, who decides what it’s allowed to do?
It’s a theme that keeps showing up in New York funding news. We’ve covered Sentra, which secures the data AI agents touch; Crux Labs, which checks agents’ work; and Daylight, which pairs AI agents with human security engineers.
You don’t need an enterprise platform to start. A few practical steps for smaller teams:
- Make a list. Write down which AI tools and agents your team actually uses, including free ones and browser extensions.
- Name an owner. Even if it’s a part-time responsibility, one person should approve new AI tools and their connections.
- Check permissions. Review what each tool can access: email, drives, code, customer records. Remove anything it doesn’t need.
- Keep secrets out of reach. Make sure coding agents can’t read passwords, API keys or production credentials.
- Revisit regularly. Vendors change features often. A setting you approved in the spring may do something different now.
Vero’s bet is that AI security will become a dedicated job at large companies. For everyone else, it’s already a job. The only question is whether anyone has been assigned to do it.
