---
title: "Someone has to hold the valve"
description: "AI security is a new job. Most companies gave it to someone who already has one."
canonical: https://www.vero.security/blog/manifesto
last_updated: 2026-11-18T13:15:20Z
---

# Someone has to hold the valve

Elad Tessler · 2026-11-18

In the early days of steam, a man stood next to the engine with his hand on a valve.

Too much steam and the engine ran away; too little and the engine stopped altogether. The man watched it all day, every day, because the engine never got tired.

In 1788, James Watt bolted two weighted iron balls onto a spinning shaft.

When the engine sped up, the balls swung out and closed the valve. When it slowed, they dropped and opened it again. He called the device a **governor**, and so the man at the valve could go home.

It's more than two hundred years later, but it turns out we are, unfortunately, standing at the valve again.

## AI is a flood

In most organizations we talk to, the person running some sort of security function woke up one morning to find “AI” in her job description. Nobody hired her for it, nobody took anything else off her plate. AI security just miraculously became her responsibility.

Now her company's agents write code, read mail, move files and call tools she has never heard of, using credentials someone granted on a busy afternoon. Every week something new ships. She has to notice it, work out what it can reach, decide what's allowed and write the control. By the time she's done, the engine has changed speed again.

And the work takes judgment. Say an AI assistant is allowed to read email and update the CRM. A customer emails asking to change their record. Is that email enough for the assistant to make the change? Or can anyone who sends an email now edit your customer data? No setting answers that. Someone has to think it through.

She's good at her job. She's also tired, and the engine isn't.

## The people already doing the job

Here's what I keep seeing. The people doing this work don't share a title. One is a cloud security engineer, one sits in AppSec, one is the CISO's most curious hire. But they all do the same job. They find out where AI is being used, what data it can reach and what it can do on someone's behalf. They decide where the boundaries belong and make sure those boundaries hold in practice. And they keep the controls current while the AI layer changes every week.

That isn't a side duty bolted onto an old role. It's a new profession forming in real time: the AI security engineer. It borrows from identity, cloud and AppSec, and adds things nobody has written down yet. What it doesn't have is a line on the org chart, a playbook, or a room where the people doing it can compare notes.

I think within a few years every security team will have one, the way every team now has someone who owns cloud.

## What CISOs told us

I met Daniel, my co-founder, in Unit 8200, where we ran a cyber operations unit together. Later, at Astrix, I spent years on the identities machines use to talk to each other: the keys and tokens that agents now run on.

Vero started in conversations with CISOs and the people they had put in charge of AI security. We asked what the work actually looked like, week to week.

Different companies used different tools, but they kept running into the same professional questions. What data may AI use? What may it do on an employee's behalf? When does a person have to approve? Security teams will have to answer those questions, and enforce the answers, years from now, with tools nobody has heard of yet. We chose to build Vero around that ongoing work.

When the engine moves faster than people can, you don't put a stronger man on the valve. You build a governor. And it has to act while the engine runs, not in a review a week later. Once an agent is about to act, the control has to work before that action goes through.

## So we built the governor

That's Vero. You write your security goals in plain words, the way you'd say it to a colleague: “I want our engineers to use coding assistants without exposing production secrets.” Vero does the rest. It finds which coding assistants, plugins and skills are in use, works out which of them can reach those secrets, and proposes the protection. Once your team approves, Vero enforces it at runtime. It works across the vendor-made coding, cloud, SaaS and desktop agents your people use, browser assistants, and the MCP servers, plugins, skills and credentials around them. When the AI changes, the control changes with it.

People stay where people belong. You set the goals, you decide what Vero handles alone, and you see everything it did. Vero only knocks when a call needs a human.

Here's the kind of thing it's for. One of our customers allowed AI plugins from the official marketplace only. A Telegram plugin got through anyway, the way things always get through. Vero caught it and blocked it from sending the contents of a code repository to an outside Telegram chat. The code never left.

We don't do everything yet. Agents a company builds for itself are next, not today. I'd rather tell you that now than have you find out later.

## Step away from the valve

The woman at the valve already does this work. It deserves a name, a craft and people to learn from. A discipline needs a home. We call the discipline AI Security Engineering, and the people who practice it AI security engineers. That's why we're building [AISecurityEngineering.org](https://aisecurityengineering.org) with the people doing it today. It's open to anyone, customer or not.

You can use it today. Start with the roadmap: the whole job laid out in nine tracks and more than 250 topics, each with a few hand-picked links, so you can see what the work covers and where to go deeper. A credential track is on the way. Join, bring what you've learned, and help decide where this profession goes.

And she deserves a governor. Her goals, her calls.

Watt didn't make the engine safer by watching it harder. He made it steer itself, so people could get back to deciding where it should go.

**You set the goals. Vero does the work.**
