All Resources
R-59
Technology
Defending the Data, Not the Perimeter
Most databases assume the network keeps attackers out and store data in the clear behind it. Tessera's AutoGuard puts an eight-layer AI-security stack inside the engine, so protection travels with the data.
PAR2 Labs
August 29, 2026
2 min
The classic database security model is a moat: authenticate at the edge, and assume that anyone inside the wall is trustworthy. That assumption fails the moment a credential leaks, an insider goes rogue, or an application is tricked into issuing a query it shouldn't. AutoGuard, Tessera's AI-security stack, is built for the world where the perimeter has already been crossed.
01
Why in-engine beats a bolt-on gateway
A proxy in front of the database sees traffic; it doesn't see data. It can't reason about whether this account's behaviour is unusual for that account, or whether a query is trying to walk the graph the way an attacker enumerates it. Because AutoGuard runs inside the engine, protection travels with the data instead of living in a separate box that has to be kept in sync with the thing it's guarding.
02
Eight layers, at the claim level
Injection detection — inspects every query for known attack shapes, with case and comment normalisation to defeat bypasses, and can block in real time. On by default.
Behavioural anomaly scoring — learns what normal looks like for each account and flags deviations: unusual amounts, high velocity, brand-new counterparties.
Canary / honeypot tokens — planted tripwires that reveal enumeration and probing.
Adaptive query defence — defences that tighten as suspicious activity rises.
Behavioural biometrics — models of normal access patterns that catch anomalous callers.
Security-posture escalation — the system raises its own guard level in response to detected pressure.
Meta-detection — detection of attempts to probe or evade the detectors themselves.
Ensemble blocker — a final decision layer that acts on the aggregate signal.
Tessera defends the data — eight layers deep, inside the engine, with every action written to a tamper-evident ledger.
03
The compliance surface on top
Above the stack sit the capabilities regulated teams actually get graded on: a tamper-evident, hash-chained audit log where altering any past entry breaks the chain and is detected on verification; fraud-cycle detection that finds circular money movement in the transaction graph; AML typology alerts; sanctions screening — against the lists you provide — with alias and fuzzy matching; and regulatory classification that maps fields onto the FIBO and BIAN vocabularies. A circular-flow signature, for instance, is a pattern the graph can express directly:
cypher
// Money that leaves an account and comes back around:
MATCH (a)-[:SENDS]->(b)-[:SENDS]->(c)-[:SENDS]->(a)
RETURN a, b, cAnd red-team simulation lets you attack the whole stack on demand — enumeration, exfiltration, injection, privilege escalation, structuring — and get back a measured report of what was blocked, rather than a feeling that you're probably fine.
Most databases protect the perimeter. Tessera defends the data — eight layers deep, inside the engine, with every action written to a tamper-evident ledger.
04
The honest scope
AutoGuard and the banking pack are Enterprise capabilities, and they're a defensive depth layer, not a replacement for network security, patching, or least-privilege access — which Tessera also enforces, with RBAC checked on every request. Sanctions screening is the matching engine; you load the lists you're required to screen against. The point isn't that one layer is magic. It's that an attacker now has to beat all of them, from inside, without tripping the ledger.
Key Takeaways
01
A proxy in front of a database sees traffic, not data; AutoGuard runs inside the engine, so protection travels with the data.
02
Eight layers run from injection detection and behavioural anomaly scoring to canary tokens and an ensemble blocker.
03
On top sit a hash-chained audit log, fraud-cycle detection, AML alerts, sanctions screening and FIBO and BIAN classification.
04
It is an Enterprise defensive-depth layer, not a replacement for network security, patching or least-privilege access.
PAR2 Labs · Technology
Work With Us