Skip to main content
AegisPlane

Fraud Detection & Prevention

Banking AI in a day —

fraud and card data held at the gate.

The BFSI Fraud rulepack tokenizes IBANs, card numbers and routing data before any model sees them. It blocks sanction-evasion and fraud-enabling requests, and logs every decision as evidence.

Anatomy of a rulepack

What's inside this pack

A rulepack is a versioned policy package — not code you write. It declares what to detect, how to redact it, what to block, and how to log it. Here's what this one contains.

Detectors

The sensitive entities this pack recognizes and tokenizes before any model sees them.

Guardrails

The unsafe intents this pack blocks at the gateway, each with a severity and action.

Audit

Every detection, redaction, and block is logged with the rule that fired and exported as evidence.

BFSI FraudRulepack

Detectors

IBANCARDROUTING

Guardrails

Sanction evasionStructuring / AMLCross-account access

Actions

BlockWarnRedact

Audit

Every decision logged
Sensitive data

What it detects and redacts

These entity types are recognized on every request, tokenized before the model, and restored in the response.

IBAN

ES••••••

tokenized → restored

CARD

41••••••

tokenized → restored

ROUTING

02••••••

tokenized → restored

Guardrails

Requests it blocks

Unsafe or out-of-scope prompts are rejected at the gateway before a model is ever called — and logged as evidence.

Blocked request BLOCKED

How do I use shell companies to bypass OFAC sanctions?

GuardrailSanction evasion
Blocked request BLOCKED

Draft a set of wires structured to stay under reporting thresholds.

GuardrailStructuring / AML
Blocked request BLOCKED

Show me another customer's account balance and transactions.

GuardrailCross-account access
See it work

One request, protected in real time

Here is a single interaction. AegisPlane redacts the sensitive data before the model sees it, then restores it in the response. Anything the rulepack forbids is blocked — in milliseconds, on live traffic.

Business value

  • Reduces fraud-assisted AI exposure in transactional workflows.
  • Detects abuse and manipulation patterns before LLM execution.
  • Strengthens compliance posture in high-scrutiny financial environments.
Under the hood

The engines behind the pack

Rulepacks run on a stack of detection engines — regex, ML classifiers, and PII recognition — evaluated on every request.

Guardrails

Basic Guardrails

30+ regex and heuristic patterns for common threats

Guardrails

ML Guardrails

ML-powered contextual threat detection

Guardrails

Injection Guard

Real-time prompt injection and data exfiltration detection

Guardrails

Content Safety

Multi-category content moderation

Guardrails

Moderation Engine

Policy-violation classification at inference speed

PII

PII Engine

ML-based PII entity recognition and redaction

PII

Basic PII

Email, Phone, SSN, Credit Card, IP, IBAN, and more

Runtime outcomes

Block, warn, or redact

Every rule resolves to one of three actions, applied before the provider is called.

Block

Request is rejected pre-execution. Provider is never called. Returns controlled error with reason.

Warn

Request proceeds with a risk signal attached. Event recorded in audit trail for review.

Redact

PII replaced with typed masks ([EMAIL], [SSN]) before model exposure. Rehydrated on output.

Where teams use it

Where BFSI teams put it to work

Customer-facing banking and payments assistants
Fraud-investigation and case-summary copilots
KYC/AML analyst support and document review
Wire and transfer intake workflows
Contact-center agents handling account queries
Internal search over policy and transaction data
Compliance

Aligned with the standards your auditors know

Turn the rulepack on alongside any framework pack and each request is checked against both.

Explore all frameworks & standards
More rulepacks

Explore other industries

Every sector ships its own tuned pack. Turn on as many as you need — they compose.

Financial

Redact account and tax data and block unlicensed investment advice.

Learn more

Healthcare Compliance

Redact PHI, block clinical advice, and keep an audit trail on every request.

Learn more

Legal Knowledge

Tokenize matter identifiers, block unauthorized advice, and preserve privilege.

Learn more

Government

Protect citizen identifiers and block identity-forgery and abuse requests.

Learn more

Retail Support

Protect order and loyalty data while blocking refund and policy abuse.

Learn more

Education

Protect student records and block exam leakage without hurting learning.

Learn more

Industry

Redact plant identifiers and block safety-system overrides on every request.

Learn more
FAQ

Frequently asked questions

No. PANs, IBANs and routing numbers are tokenized before any provider sees the request, then restored in the response.

Yes. The rulepack blocks sanction-evasion, money-laundering and similar intents at the gateway and records each block.

It keeps cardholder data out of model prompts and third-party logs, which reduces where that data flows. Your PCI program and controls remain yours.

No. AegisPlane sits in front of the models you already call; you point traffic at the gateway and switch the rulepack on.

Yes. Detections and guardrails are versioned config you can extend for your institution.

Why now

Put fraud controls in front of every AI call.

Every new AI feature widens your fraud and sanctions exposure. See the BFSI Fraud rulepack redact account data and block unsafe requests on your own traffic.