Adversarial security assurance · Banking & insurance

Prove what attackers can actually do.

X-PHY continuously tests applications, APIs, identities, business logic and AI agents to find exploitable attack paths — then gives you the evidence to fix, verify and assure them. It runs inside your own perimeter and seals every result to a hardware root of trust.

Discover. Prove. Fix. Verify. Assure.
Open the live console
For Banking · Insurance · Enterprise · Government — built for real-world security operations.
1
AI-agent exploit proven & verified end-to-end
3/3
replays to confirm every finding
7
OWASP API Top-10 classes confirmed on a live target
100%
on-premise · nothing leaves the estate
The loop

Every engagement runs one closed loop.

01
DISCOVER
Map the estate — apps, APIs, identities, AI agents, shadow assets.
02
ATTACK
Exploit under the safety kernel — authz, logic, tokens, agents.
03
PROVE
Re-execute 3× against clean state; unproven is discarded.
04
FIX
Ship a developer-ready fix prompt for each proven finding.
05
VERIFY
Replay the exact exploit → Verified Closed.
06
ATTEST
Regulator packs, sealed to the X-PHY root of trust.
The loop re-runs on every change to the estate.
The gap

Scanners list conditions. Regulators need proof.

Automated tools flood teams with unverified findings and miss the flaws that actually move money. The market has rejected unaccountable AI — support for fully-automated pentesting fell to single digits. What banks need is machine speed with human-grade accountability.

01

Business logic goes untested

The rules that lose money — limits, maker-checker, entitlements, claims aggregates — live in your documents, not in code. Scanners built to read code rarely reach them.

02

AI agents are the new attack surface

Copilots and agents with real tool access can be manipulated into acting beyond the invoking principal. Most tools do no AI testing at all.

03

Findings can't be trusted or signed

AI output is frequently overstated. Autonomous reports don't satisfy auditors who require reproducible evidence and a named tester.

04

Data can't leave the jurisdiction

Regulated institutions can't ship source, findings or traffic to a foreign SaaS. Cloud-only tools are closed off before the first scan.

What powers the loop

Six capabilities that close the loop.

The loop only closes because of what sits under each step. Together these capabilities are why a regulated institution can say yes.

Proof, not findings

Every finding is a replayable capsule. A separate engine re-executes it three times against clean state; anything that doesn't reproduce is never reported. Every reported finding is backed by reproducible evidence — and labelled with how far it was driven: observed, exploitability proven, or business impact proven.

Business logic from your own rules

X-PHY converts your explicit business obligations — authority matrices, approval rules, product terms and transaction limits — into executable adversarial invariants, then tasks agents with violating them.

AI & agent abuse testing

Indirect prompt injection, agent-authority escalation and forgeable tokens, chained into the rest of the estate and tested alongside every other layer.

Sovereign & air-gapped

Runs entirely inside your perimeter. No source, no finding, no packet leaves your jurisdiction — the difference between being allowed to bid and not.

Hardware root of trust

Evidence is signed with software Ed25519, and can be sealed to a non-extractable key inside an X-PHY Cyber Secure SSD for on-prem deployments. Every capsule is labelled with its trust mode — X-PHY never presents a software signature as hardware attestation.

Test once, attest many

One structured evidence base emits regulator-specific packs — MAS TRM, BNM RMiT, HKMA iCAST, PCI DSS — each countersigned by an accredited human tester.

The engagement journey

From "we want to test" to a signed regulator pack — one guided path.

Eight steps, threat-intelligence-led in the shape MAS, HKMA and DORA expect. At every step you see exactly what you provide and what X-PHY does.

Engage
1

Scope & authorize

A one-page rules-of-engagement fixes targets, off-limits systems, a financial-effect ceiling, the test window and the named accountable tester — the pre-engagement alignment regulators require before any offensive activity.

YouSign the rules-of-engagementX-PHYLocks scope + ceiling into the safety kernel
MAS TRM · pre-engagementDORA TLPT · scoping
2

Deploy inside your perimeter

X-PHY stands up as an appliance in your own environment. Source, traffic, findings and credentials never leave your jurisdiction — the difference between being allowed to bid and not.

YouPlace the appliance (VM or X-PHY box)X-PHYRuns air-gapped; nothing phones home
SovereignData residency
Run
3

Discover & model the application

X-PHY crawls the estate, authenticates as real users (credentials stay in your perimeter, MFA pause-and-resume), and builds an application model — routes, roles, objects, ownership, data classes and your business rules — so attacks are application-specific, not signature-based.

YouStaging URL + test creds for 2+ rolesX-PHYCrawl → authenticate → application graph
Discover → ModelShadow-API discovery
4

Attack — under a graduated safety kernel

Testing starts read-only (GET-only), then widens to authorized exploitation as confidence builds — BOLA/BFLA, broken auth & forgeable tokens, OAuth/FAPI flaws, business-logic abuse (transaction limits, maker-checker), and AI-agent manipulation — every action scoped, rate-limited and hash-logged. You watch it live.

Safe firstGET-only, then broaden on approvalX-PHYAgent fleet attacks under the kernel
OWASP API Top-10Business logicAI / agent abuse
Prove
5

Prove by independent replay

Each candidate is re-executed three times against clean state, capturing request/response and route-level context. Anything that doesn't reproduce is discarded; everything reported carries reproducible evidence, labelled with the tier of proof it reached — observed, exploitability proven, or business impact proven.

X-PHY3× replay · request/response captured · unproven discarded
Reproducible evidence
6

Seal to the hardware root of trust

Proven capsules are hash-chained and signed with software Ed25519, and can be sealed to a non-extractable X-PHY Cyber Secure SSD hardware key on-prem. Either way an auditor verifies the chain and signature offline, with no trust in the vendor.

X-PHYHash-chain + X-PHY signature
Tamper-evidentOffline-verifiable
Assure
7

Fix & verify — close the loop

Each finding ships a developer-ready fix prompt. After remediation, X-PHY re-runs the exact exploit capsule; three blocked replays flip the finding to Verified Closed. Continuous evidence across cycles — not a point-in-time PDF.

YouApply the fixX-PHYReplays the exploit → Verified Closed
Fix → Verify → Repeat
8

Attest & keep watch

One evidence base emits per-regulator packs — MAS TRM, BNM RMiT, HKMA iCAST, PCI DSS — each clause-mapped and countersigned by an accredited tester. Then X-PHY re-tests affected paths on every change, so assurance is continuous.

X-PHYRegulator packs + human sign-offYouHand the auditor a pack they can re-run
Multi-regulatorContinuous
See the console the journey produces
Verified, not asserted

12 weaknesses reproduced on a live third-party API.

We pointed X-PHY at VAmPI — a well-known open-source vulnerable API we did not write — and it reproduced 12 weaknesses across 7 OWASP API Top-10 classes, each re-executed 3/3. Six were driven through to proven business impact; six were retained at the evidence level actually demonstrated — nothing is overstated. Open the console to inspect every evidence capsule.

CriticalJWT forged to admin — weak signing secret✓ 3/3
CriticalBOLA account takeover — reset another user's password✓ 3/3
CriticalSQL injection on user lookup✓ 3/3
CriticalMass assignment — self-grant admin on register✓ 3/3
+ 8 more across API3, API4, API8, API9 — all replay-verified.
Regulatory coverage

One evidence base. Every regime that governs you.

Multi-jurisdiction institutions pay repeatedly for overlapping tests. X-PHY derives a separate, clause-mapped attestation pack for each regulator from a single assessment.

Singapore · MAS TRM Malaysia · BNM RMiT Hong Kong · HKMA C-RAF / iCAST India · RBI · IRDAI Indonesia · OJK Australia · APRA CPS 234 Global · PCI DSS 4.0 EU exposure · DORA / TIBER Payments · SWIFT CSP
Root of trust

Evidence you can't forge — even from the inside.

The one thing no software-only competitor can match, because it requires the hardware.

Every proof capsule and hash-chained evidence bundle is signed with software Ed25519, and can be sealed to a key that lives inside an X-PHY Cyber Secure SSD — non-extractable, every signature produced on-device — for on-prem deployments. In both modes an auditor verifies the chain and signature offline — no network, no trust in the vendor.

Chain of custody

A single operation, sealed and verifiable:

Exploit captured as a parameterized capsule
Re-executed 3× against clean state
Capsules hash-chained into one bundle
Signed — software Ed25519 · X-PHY hardware attestation on-prem
Auditor re-runs & verifies offline

See it prove a breach — live.

Open the operator console and inspect twelve replay-verified findings on a real target, or read the auditor-ready report.