HabrSeptember 23, 2026🇷🇺Translated from Russian

Evaluating Jev: Can the New Encoder-Based Model Serve as an Effective Guard for LLMs?

The cybersecurity community continues to explore specialized guard models that can protect large language models from jailbreaks, prompt injection, and data exposure. A new analysis from Raft asks whether Jev, released by TypeSafe on 15 September, can serve as a practical guard model for both safety and privacy use cases.

Over the past two years, open-source guard models have largely been dominated by large language models such as Qwen Guard, gpt-oss-safeguard, and YuFeng XGuard. Earlier encoder-based attempts, including Wildguard built on Mistral 7B, offered strong classification quality but suffered from slow inference and high memory requirements. Most BERT-style encoders lacked multilingual pre-training, making them ineffective for Russian text, while LLMs inherited multilingual capabilities from their pre-training.

In May 2026, three new encoder-based guard models appeared almost simultaneously: gliner guard, gliguard from Fastino, and the gliclass family. These models represent a shift back toward efficient encoder architectures. Jev distinguishes itself by offering a unified model for both safety and privacy detection and by claiming an unusually large context window of 32K–64K tokens, far exceeding the typical 512–8192 token limits of most encoders.

Testing shows that Jev handles obvious jailbreaks and prompt-injection attempts effectively. It can indicate whether a text contains personally identifiable information, yet it does not perform classic named-entity recognition and cannot return exact text spans for masking. Consequently, production deployments would require an additional NER stage or full request blocking.

On the Aegis 2.0 benchmark from NVIDIA, Jev achieved an F1 score of 0.85 and recall of 0.84 on prompts at the 0.5 threshold, with an AUC of 0.921. On model responses the AUC rose to 0.927, although recall dropped to 0.76. In the broader GuardRate evaluation, Jev placed second with a score of 0.835, behind only the 0.4B opir-multitask-large GliClass model (0.906) and ahead of Qwen3Guard-Gen-8B (0.819) and both YuFeng XGuard variants.

Despite these promising results, two practical blockers remain for production use: all inference currently routes through an external API, raising data-protection concerns under Russian Federal Law 152-FZ, and the model has not yet been evaluated on Russian-language traffic. Organizations considering Jev are advised to validate domain-specific performance and false-positive rates on their own datasets before deployment.

Related articles

HabrAI Security

How to Grant AI Agents Access to Internal APIs via MCP: Key Questions Security Teams Will Ask

As AI agents increasingly need to call internal APIs, security teams focus on three core questions: who granted access, how to revoke it, and how to investigate incidents after the fact. The answers lie in operation-level access control rather than traffic inspection alone. MCP, now managed by the Agentic AI Foundation under the Linux Foundation, has become the standard for connecting AI agents to enterprise systems with hundreds of millions of SDK downloads monthly. The article details how NEOMSA APIM implements MCP servers, tool publication from OpenAPI specs, subscription-based scopes, and 15 independent security checks. It explains why classic traffic filters fail against valid but unauthorized tool calls and stresses the need for owner approval, application-specific identities, and proper identity propagation through token exchange. Rate limiting at the subscription level and business-object validation are presented as essential controls to prevent overreach and duplication.

BoletimSecAI Security

HackerSec's Yaga AI Agent Delivers Autonomous Penetration Testing with 98% Effectiveness

HackerSec has developed an autonomous penetration testing platform powered by its Yaga AI agent, marking a shift from scripted automation to adaptive, decision-making offensive security operations. Unlike traditional tools that follow predefined checks, Yaga observes the target environment, interprets responses, forms hypotheses, and replans attack paths in real time while maintaining memory and state across findings. The system relies on a proprietary harness that coordinates advanced AI models, security tools, contextual data, and ongoing decision logic rather than depending on a large language model alone. Yaga already achieves more than 98 percent effectiveness and supports continuous testing that matches the rapid change cycles of modern applications. CEO Andrew Martinez noted that periodic manual pentests can no longer keep pace with AI-accelerated attacks, requiring an AI-native model capable of operating at the same speed as the systems it protects. The platform allows human specialists to monitor and validate results while the agent conducts the investigation independently.

HabrAI Security

AI Gateway Emerges as Unified Control Layer for Enterprise LLM Access and Data Protection

As organizations scale LLM usage beyond individual enthusiasts to dozens of teams, IDEs, internal agents, and automations, AI Gateway becomes essential infrastructure for security, cost management, and reliability. The solution acts as a single entry point that authenticates users, enforces policies, performs DLP checks, depersonalizes sensitive data, routes requests across providers, and enables detailed auditing and billing. Companies face strict requirements under Russian Federal Law 152-FZ on personal data, along with risks of leaks involving API tokens, client information, and internal code when employees bypass official channels. Mature implementations from Cloudflare, Kong, and Microsoft Azure API Management already demonstrate analytics, rate limiting, fallback mechanisms, and governance features. Compatibility with OpenAI API reduces migration friction when switching between providers, including Chinese models, while handling edge cases like tool calls and vision capabilities. The article stresses separating AI Gateway responsibilities from DLP, MCP Gateway, and guardrails to avoid creating an unmanageable monolithic system. Early implementation priorities include ownership, comprehensive auditing from day one, real-world client compatibility testing, shadow-mode DLP, and clear documentation of production architecture.

HabrAI Security

AI Accelerates DevSecOps but Expands Attack Surfaces Across Code, Supply Chains, and Runtime Environments

Experts from Solar, Luntry, and Hexway report that AI has shortened the vulnerability exploitation window from 63 days in 2019 to just hours in 2025. The shift toward third-party libraries and vibe coding has redirected attacker focus to supply-chain compromises affecting thousands of organizations. AI-generated code introduces unique risks because it often bypasses established libraries, testing phases, and security reviews, with 41% of confidential data leaks into LLMs now consisting of source code. While AI tools like the Solar appScreener plugin achieve over 90% accuracy in triage and 85% in code-fix recommendations, human verification remains mandatory for critical vulnerabilities. Platforms such as Hexway ASOC and Luntry extend protection into container orchestration and runtime monitoring to handle AI agents that make decisions during execution. The overall effect is a tenfold increase in AppSec team capacity, yet also a larger volume of findings that must be managed through integrated ASOC workflows.