Jev’s Keep SOC analyst replay

0 / 0 judged · 0 blocked
Attacks caught
0 / 0
of the attacks judged so far
False alarms
0
legitimate requests blocked
Avg decision latency
— ms
per request · real Jev round-trip
0Incoming
0Admitted
0Repelled
Legitimate request · Attack (the shape = what it really is)
Through the gate = Jev allowed · hits the wall = Jev blocked, ranked by attack type
Details ↓

Accuracy both waves

Request stream

Red-flag log blocked requests, newest first

Beyond classic attacks: what a signature WAF can’t see

Wave 1 is classic attacks — SQL injection, XSS, path traversal — things with a recognisable payload shape. A rule-based WAF catches most of those. Wave 2 is a newer class that carries no signature: prompt injection against an app’s AI, requests that ask it to leak data, and business-logic abuse. They read as ordinary English, so pattern rules never fire. Below, a signature WAF and Jev see the same set of these semantic attacks.

What each let through

Semantic attack (the actual request)TypeRegex WAFJev