LLM SECURITY CONTROL PLANE · ON-PREM
Wardline sits in front of enterprise LLM traffic. It inspects every request, returns one of five decisions and shows why that decision was made, with evidence. Built for enterprises.
| Decision | Reason code |
|---|---|
| ALLOW | — |
| MASK | PII.TCKN |
| ALLOW | POLICY.DEFAULT_ACTION |
| DENY | PI.DIRECT_OVERRIDE |
| MASK | PII.IBAN_TR |
| REWRITE | PII.CREDIT_CARD |
| REQUIRE_APPROVAL | PI.TOOL_COERCION |
01 — DECISIONS
Wardline never produces an ambiguous state. Partial inspection is not a decision; it is a flag attached to one. Analysts and auditors speak the same language.
The request reaches the model unchanged. Decisions without flags produce compact evidence.
Example reason code: POLICY.DEFAULT_ACTIONPersonal data is masked by position before it reaches the model.
Example reason code: PII.TCKNPolicy requires the request to be rewritten; if the rewrite cannot be applied, the request is rejected with a flag.
Example reason code: PII.CREDIT_CARDA request that requires approval is rejected until the approval flow is in place; it does not reach the model.
Example reason code: PI.TOOL_COERCIONThe request is blocked and returns to the application with a reason code.
Example reason code: PI.DIRECT_OVERRIDE02 — EVIDENCE
In the default installation, prompt and response text are not stored and do not reach the panel. Evidence reads like this: message 0, bytes 120–131, entity tckn, checksum verified. Auditors can trace the decision through this record; analysts can explain it without seeing personal data.
| SOURCE | BYTES | ENTITY | VERIFICATION | CONFIDENCE |
|---|---|---|---|---|
| message 0 | 120–131 | tckn | checksum verified | 0.99 |
| message 0 | 148–173 | iban | checksum verified | 0.97 |
| tool 1 | 200–215 | phone | format only | 0.71 |
Latency targets will be published here once measured on reference hardware.
03 — ARCHITECTURE
Applications connect to the Wardline gateway with an API key. The engine evaluates each request against a signed policy; the decision and evidence are recorded, the text is not recorded by default.
04 — COMPLIANCE
Evidence carries only position and entity type. Detected national IDs, IBANs and card numbers are not shown in the evidence or the interface.
Designed for organizations that require on-premises hosting: in an on-prem install every component runs in the bank’s own infrastructure.
Who changed what, and when: policy, role and key changes are kept with before/after diffs.
In Cloud, the Wardline operator panel reads only directory information such as organization name, plan and region; it has no access path to prompts, evidence, events or user data. On-prem installs contain no operator panel at all.
05 — TWO FACES
“Why was this decision made?”
“How is it configured?”
06 — DEPLOYMENT
The gateway, engine and classifiers run on your infrastructure. The on-prem build contains no sign-up, billing or operator panel surfaces, and a build check verifies this.
Run by Wardline, with an organization dedicated to you. Usage starts once your demo request has been reviewed; the Wardline team opens the organization and invites you.
A session with your security team: architecture, evidence viewer and policy editor.