blog

Company

Product

Why we built Treat

Why we built Treat

Gal Dudi

Gal Dudi

|

|

Reading Time:

7

min

Table of Contents

I was sitting with a CISO. Experienced, respected, running a team of twenty-plus. I asked him what kept him up at night. Ransomware, I figured. Compliance deadlines. Board pressure.

Instead he said: "My team resolves thousands of cases every month. I couldn't tell you if they're following policy consistently, whether we're making the same call twice for the same situation, or if the urgent things are getting handled first. I have no way to verify that nothing slips."

That landed differently than any threat briefing I'd ever heard. He wasn't describing a security problem. He was describing a service execution gap: the distance between what an organization needs from security and what the team can actually deliver.

The more organizations I talked to, the more universal it looked. Every department now depends on security. R&D wants to train a model on customer data? Security signs off. Sales needs a vendor approved before a deal closes? Security. The volume has grown far beyond what anyone planned for.

Requests arrive from everywhere: ITSM tickets, Jira, Slack, Teams. When they land, there's almost nothing to work with. No context on who's asking, what's at risk, or what precedent exists. So analysts do detective work. Backchannel DMs. Old threads. One alert becomes ten open tabs. Every case is handled a little differently, and every decision depends on who picks it up and what they happen to remember.

Nobody owns that queue. It is a waiting room.

I've seen this movie before

Twenty years ago, IT operations faced the same thing. Every request was ad hoc. Nobody knew who owned what. Processes lived in people's heads. Then structured tooling emerged and turned IT into an operational discipline.

Security is at that point now. CISOs are hiring Chiefs of Staff. Teams are building real reporting structures and process governance. George Kurtz spent his 2025 RSA keynote on how CISOs earn their place at the board table. The profession is moving from "the team that blocks things" to a function expected to run like a business.

But the stakes are higher. A slow IT ticket means someone waits a day for a laptop. A slow or wrong security decision means an attacker moves deeper, a vulnerability stays exposed, or a compromised vendor gets approved because nobody had time to dig into the assessment.

What's missing

Detection is not the bottleneck anymore. AI-powered SecOps tools find threats faster and summarize alerts. The bottleneck is what happens after: the investigation, the decision, the resolution, and whether that resolution is consistent, defensible and aligned with policy.

Look at how the existing categories break. SOAR automates a slice of alerts. ITSM tracks tickets without security context. GRC documents risk after the fact. Some detect. Some route. Some document. None own the queue.

  • A queue without an owner becomes a waiting room.

  • A queue without context becomes detective work.

  • A queue without a record becomes an audit problem.

Most tools also run without organizational awareness. They can block a threat but can't tell you if blocking it kills a deal. They can flag a policy violation but don't know that the same violation was approved as an exception six months ago, for a reason that lives only in someone's head. They rank by severity score and have no sense of the business weight behind it.

Without that context, automation is speed without judgment. You close a ticket in seconds and still get it wrong. A ticket closed is not a problem solved.

What we realized needed to exist

Detection is pattern matching. Operations is judgment. And judgment needs context that no existing tool was capturing.

So we built Agentic Cyber Service Management. Treat assembles the context behind every request, alert and approval, then resolves it end to end, in one queue.

Context Assembly comes first. Treat normalizes signals from chat, ITSM and cloud systems into one stream. Every case is ranked by security risk and business impact. For the first time, the CISO can see the full scope of what the team handles.

Underneath it is a knowledge graph. This is the part I'm personally obsessed with. It maps users, assets and business risk. When a case arrives, Treat already has the requester's identity and risk profile, the related historical cases and the policies that apply. The full picture is there before anyone opens the case.

Then the Reasoning Layer works the case. It investigates and recommends a resolution. Agents and policies run the workflow from there. They encode how your organization actually works: procedures, approval chains, exceptions, how decisions get made. A new hire works with the rigor of a ten-year veteran.

Treat does the work. It does not run unsupervised. Nothing acts until you say so. Every agent runs in shadow against your real queue first, and you decide what graduates. Every step is reversible. Every decision is documented, so the record is there when the board, the auditor or your own team asks.

Over time, more cases resolve without a human touch. The analyst stops being the responder to every case and becomes the supervisor of the queue. The team stays the same size. The queue does not.

Here is what that looks like in practice:

  • 90% reduction in mean time to resolve

  • 92% of tickets auto-closed without an analyst touching them

  • 860 hours of investigation time back every month

Treat also does not ask you to rip out your stack. It runs alongside the tools you already use, including ServiceNow, and makes them useful for the work that starts after a signal arrives.

Why us

I didn't start Treat from a market thesis. I started it because I lived the problem, long enough that building the solution felt inevitable.

My background is in AI and in building systems that understand complex data relationships: ontologies, entity resolution, the layers that turn raw information into something a machine or a person can reason about. I spent years watching security teams drown because nothing connected what the organization needed to what the security team could see.

Yonathan, our CTO, comes from deep cyber operations. He spent years inside high-pressure security environments, watching processes break when it mattered most. He didn't just observe it. He started building the fix long before we made it a company.

What convinced us was taking that experience outward. We talked to security leaders across industries and continents and heard the same pain and the same workarounds. Nobody had a system designed for how security actually operates. Everyone was adapting tools built for someone else.

So we built Treat to fit each customer, not the other way around:

  • Small models, one per job. We run targeted small language models for each workflow, alongside large models for complex reasoning. They are fast, cost-efficient and specific to your environment. Customer data stays in the customer's environment and is never used to train our general models.

  • A dedicated Forward Deployed Engineer. Every customer gets an FDE who works next to the in-house team. They learn your systems, policies, approval paths, owners and priorities, then configure Treat to take the right action in the right situation. You say what you need in your own words. No developers required.

  • An AI-native team. Our engineers work with AI-native workflows, each producing the output of five. Our data team builds the ontological layer that lets Treat understand what a case says and what it means in context.

Where this goes

Security is earning its place at the leadership table. CISOs present in business terms, own operational outcomes and quantify risk in ways the board can act on. The question is what can support them in getting there.

Every business is under pressure to move faster: adopt AI tools, approve vendors, connect data, grant access, ship, close deals. Each move needs security's signoff. When review can't keep pace, launches slip, deals stall and teams look for ways around the controls meant to protect them.

We're building for a world where security moves from wait to done. Every decision is informed, consistent and fast. The CISO can show the board exactly what the team handles, how well it handles it and what that means for the business. Security stops being what everyone waits on and becomes the reason the organization moves faster.

That's what Treat is for.

Questions? Knock twice.