What Verdict Runtime covers

What Verdict Runtime covers: code, dependencies, IaC, secrets, containers, cloud and Kubernetes posture, and live testing across the OWASP Web, API and LLM Top 10.

Coverage

One report across your whole stack

Every engine lands in one schema, deduplicated and correlated, so you read one report, not six.

Dependencies & supply chain

Vulnerable packages, whether they're reachable from your entry points, and a signed SBOM.

Reachability · SBOM · signing · VEX

Source code

Injection, auth, access-control and crypto defects, cross-checked by two engines.

~20 in-house rules for gaps the market misses

Secrets, cloud & pipelines

Committed credentials, cloud and Kubernetes misconfiguration, hijackable CI workflows.

Cloud posture · container images · CI

Running application

Authenticated testing, including broken authorization that only shows when two real accounts are compared.

20 targeted checks · OWASP API1–10 · A01–A10

AI & LLM features

Live adversarial testing of your model-backed features, judged against planted canaries and markers, not a model's opinion.

21 checks · LLM01–LLM10 · agentic

Business logic

An agent that learns your app's real API traffic, then tests rules like double-redeemed coupons and replayed checkouts.

Uncertain results are labelled for review
See the AI & LLM checks and what each one proves
OWASPCheckWhat a finding proves
LLM01Prompt injectionA crafted instruction overrode the system prompt and returned an exact attacker-chosen marker.
LLM01Indirect prompt injectionAn instruction planted in fetched content — not in the user's message — was followed.
LLM01Multi-turn escalationDefences that hold on a single message fail across a real multi-turn conversation.
LLM02Sensitive information disclosureA canary secret planted in your own data came back in a model response.
LLM03Plugin and tool enumerationThe model disclosed the real integrations it can reach when asked to list them.
LLM04Persistent data poisoningContent written by one account changed what a different account was told, on a fresh session.
LLM05Improper output handlingModel output reached the page or a downstream system without escaping.
LLM06Excessive agencyThe model invoked a sensitive tool outside the user's stated intent.
LLM07System prompt leakageA known verbatim fragment of your own system prompt was recovered.
LLM08Cross-tenant retrieval leakageRetrieval crossed a tenant boundary and returned another tenant's canary.
LLM08Knowledge-base poisoningA document submitted through your own product changed later answers after sync.
LLM09Hallucination under pressureThe model produced confident technical detail about an entity that does not exist.
LLM10Unbounded consumptionOversized input and long conversations were accepted with no effective cap.
AgenticAgent code executionThe agent ran an attacker-supplied command through its own execution tool.
AgenticTool parameter injectionAn authorised tool was re-invoked with an out-of-scope parameter value.
AgenticAgent-to-agent trustA message claiming another agent's identity was accepted without verification.
AgenticIdentity and guardrail erosionSustained reframing across turns moved the model off its assigned identity and limits.

Seventeen of twenty-one checks shown. Every one requires your written authorisation before it sends a single request.

Get your first verdict free

One repository, one report, no obligation: the findings, the evidence behind each one, the fixes we can prepare, and an honest note on what we couldn't check.

Request a free assessment See a sample report Reply within two business days.
We never scan first. Nothing is tested until you've named the target in writing and confirmed you're authorised to have it tested.