Safety classification of AI inputs and outputs across harm categories — hate, violence, sexual content, self-harm, and illegal activity. For fintechs, the stakes are concrete: AI systems handle card PANs, bank credentials, KYC selfies and IDs, and payment histories.
LGPD applies to AI data use; the PL 2338/2023 AI bill advances a risk-based framework. Guardrails deployed in Brazil must also work in Portuguese, not just English.
Frameworks to satisfy: PCI DSS · PSD2/open-banking rules · local e-money licensing
LGPD applies to AI data use; the PL 2338/2023 AI bill advances a risk-based framework.
Language coverage matters: primary business language — Portuguese. Ask vendors for measured accuracy per language, not a supported-language list.
Safeguards and guard models are configured for the use case — and updated or fine-tuned for your domain when needed.
Every command, tool call, and data access is observable in one place — across models, frameworks, and MCP servers.
Policies apply inline as agents act — block, redact, or require approval before the action executes, not after.
A preserved audit trail of every agent action — evidence you can hand to auditors, regulators, and incident responders.
PII and secrets detected and redacted in tool-call payloads and MCP traffic before data leaves your org.
GuardionAI builds its own guard models and publishes the benchmarks — the numbers below come from the public guard models guide. Independent alternatives are listed right after this section.
Guard models are natively trained on 8 languages (English, Spanish, Italian, Portuguese, Russian, Chinese, Hindi, Arabic) — including Portuguese — extended to 100+ languages, and evaluated across 1,000+ languages — including historical and dead languages — with graceful post-training decay.
Precision 0.98 • FPR 0.02
Recall 0.99 • aligned with the NVIDIA Aegis (Nemotron) content-safety taxonomy
Precision 1.00 • FPR 0.004
PII groups
Person name · Contact · Address · Government ID · Payment · Digital ID · Company
Secrets
AWS access & secret keys · GitHub tokens · Google API keys · Slack tokens · Stripe keys · Private keys & JWTs · npm tokens · Seed phrases · Generic API keys, secrets & passwords
Policy engine decisions return in under 130ms — 20× faster than cloud provider guardrails. Benchmarks: sensitivity L1–L4, methodology in the docs.
Request a demoIndependently listed from the Runtime Guardrails & AI Firewall category of the index — each with its own analysis page.
A focused runtime security layer protecting against prompt injection, PII leakage, and hallucinations via API. Acquired by Check Point in late 2025 (~$300M reported); Lakera Guard and Lakera Red remain live products and anchor Check Point's Center of Excellence for AI Security.
For fintechs: check Lakera (Check Point)'s coverage of PCI DSS and PSD2/open-banking rules requirements and its handling of card PANs before committing.
A set of LLM safeguards designed to detect violating content across multiple use cases. Model-based guardrail.
For fintechs: check Meta (Llama Guard)'s coverage of PCI DSS and PSD2/open-banking rules requirements and its handling of card PANs before committing.
Google Cloud's GA service for screening LLM prompts and responses for prompt injection, jailbreaks, harmful content, malicious URLs, and sensitive data leakage. Model-agnostic (works with Gemini, OpenAI, Anthropic, Llama over REST) and integrated with Apigee, Vertex AI, Agent Gateway, and Security Command Center, with org-wide floor settings for baseline enforcement.
For fintechs: check Google Cloud Model Armor's coverage of PCI DSS and PSD2/open-banking rules requirements and its handling of card PANs before committing.
GuardionAI covers the full ai content moderation stack (prompt defense F1 0.95, moderation F1 0.98, PII/DLP F1 0.97), and strong alternatives include Lakera (Check Point), Meta (Llama Guard), Google Cloud Model Armor — compared in detail on this page.
Safety classification of AI inputs and outputs across harm categories — hate, violence, sexual content, self-harm, and illegal activity.
Fintechs route card PANs, bank credentials, KYC selfies and IDs, and payment histories through AI systems, so the top risks are bot abuse and scripted attacks on AI onboarding flows; card and bank-credential leakage in support chat; jailbreaks that turn assistants into fraud tools. Relevant frameworks: PCI DSS, PSD2/open-banking rules, local e-money licensing.
LGPD applies to AI data use; the PL 2338/2023 AI bill advances a risk-based framework. Fintechs additionally answer to PCI DSS, PSD2/open-banking rules, local e-money licensing.
Yes — Guardion's guard models are natively trained on Portuguese (one of 8 training languages), extended to 100+ languages, and evaluated across 1,000+ languages — including historical and dead languages — with graceful post-training decay. Verify language coverage explicitly when evaluating any vendor.
Published benchmarks report precision/recall/F1 and false-positive rate per model family. Guardion publishes its methodology and per-sensitivity results (L1–L4) in the guard models guide: https://guardion.ai/docs/guides/guard-models.