Sentinel
A security layer built for AI systems rather than adapted to them. Sentinel holds the perimeter of a deployed model application, intercepts hostile input in the request path, and contains abuse before it compounds. Currently hardening Selina.ai. Spinning out as a standalone product.
Every AI application inherits an attack surface nobody designed for.
Web application firewalls understand requests. They do not understand instructions. A model wrapper accepts natural language as executable intent, which collapses the distinction between the payload and the prose carrying it. Signature matching cannot see that, because there is no malformed byte sequence to catch. Rate limiting cannot stop it, because a single well-formed message is enough.
The failure mode is not a crash. It is an application that continues to behave correctly by every operational metric while doing something its operator never authorized. Uptime stays green. Latency stays flat. The system is compromised and the dashboard says nominal.
Sentinel treats the prompt boundary as the actual security boundary. It models what normal interaction looks like for a given application, flags deviation probabilistically rather than by signature, and contains the session before a successful technique can be repeated at scale.
PERIMETER SWEEP
Contacts illuminate as the sweep resolves them. Illustrative.
REQUEST CLASSIFICATION
Traffic scored continuously against a learned envelope. Height is deviation, not volume. Sustained excursion escalates to containment.
01
Injection interception
Instruction-override attempts are identified in the request path and neutralized before they reach the reasoning layer. The payload never becomes an instruction.
02
Jailbreak resistance
Continuous adversarial evaluation against identity hijack, role subversion and gradual constraint erosion across every model the application can route to.
03
Behavioral baselining
Probabilistic models of normal traffic make novel attacks legible as deviation, which means detection does not require a prior signature for the technique.
04
Automated containment
Detection triggers isolation without waiting for a human in the loop. Blast radius is bounded in minutes rather than discovered in a quarterly audit.
05
Content blindness
The guard watches the door, never the room. Enforcement runs on metadata, timing and behavioral signal rather than the substance of private conversation.
06
Wrapper-native design
Purpose-built for model applications rather than retrofitted from web firewalls that have no representation of a prompt as an executable object.
07
Multi-model coverage
Defense travels with the application, not the provider. Routing across vendors does not open a gap in the perimeter or reset the threat baseline.
08
Enumeration defense
Systematic probing for capability boundaries, hidden instructions or credential structure is recognized as a campaign rather than a series of odd requests.
09
Telemetry surface
Every enforcement decision is observable and attributable, so posture can be reasoned about instead of assumed.
What we assume the attacker already has.
AVAILABILITY
Sentinel is announced without a release date. If you operate an AI application and want to be told when it opens, open a channel.