TL;DR: Decision models like Jev are shifting AI from chat-style output to bounded security judgments inside APIs, workflows and applications, according to Cato Networks. Security teams need deterministic controls so probabilistic scores do not turn into uncontrolled actions.
Editorial analysis by NHI Mgmt Group, based on content published by Cato Networks: “Wait, Did We Just Invent Classifiers Again? Introducing Jev, a new way to do AI.”.
Key questions
Q: Why does embedded AI in SaaS create a governance gap?
A: Embedded AI creates a governance gap because authenticated access to an application does not reveal how that application will use the data it receives.
Q: How can organisations use probabilistic AI outputs without losing control?
A: Use the model to score risk or recommend a state, then map each outcome to fixed policy and workflow rules.
Q: How should security teams govern AI models that can call tools and access data?
A: Security teams should govern AI models as non-human identities with named owners, limited scope, short-lived credentials, and continuous authorization.
Practitioner guidance
- Define decision thresholds for AI-assisted triage Map each probability band to a specific outcome such as close, review or contain, and require those mappings to be approved by the control owner.
- Inventory embedded AI across workflows and APIs Locate model calls inside applications, event pipelines and security tooling, then record what data enters the model and what actions its output can influence.
- Separate model scoring from enforcement Keep the model advisory and let deterministic policy, workflow rules and access controls perform the actual enforcement step.
Bottom line: AI decision models shift the security problem from open-ended language generation to bounded operational judgment.
Glossary terms: Decision Model, Embedded AI, Probabilistic Output, Deterministic Controls
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Decision-centric AI will matter more than chat-centric AI in security operations. Security teams do not need every model to write a report. They need models that can turn noisy state into bounded operational judgments such as investigate, contain or close. That makes the governance question much sharper because the model is now part of the decision path, not just the interface. The practitioner implication is to classify every AI decision point by the control it influences and the action it can trigger.
A question worth separating out:
Q: How should security teams secure AI agents before they are embedded into business workflows?
A: Security teams should treat AI agents as a distinct identity and access problem, not just an application feature. The first step is to inventory agent activity, define allowed actions, and constrain access to only the data and systems each agent needs. Governance should include monitoring, policy enforcement, and review of agent decisions so unintended actions are detected early.
👉 Read our full editorial: AI models that make security decisions are moving into workflows