ProtocolGovGuardFinGuardExplorerPlaygroundAdoptCloudTrustDocsRequest Pilot
Comparison / Fraud Detection

Pre-action authorization vs post-action fraud detection

Detection finds bad actions after they execute. Pre-action authorization stops them before they execute. For irreversible actions — wire transfers, benefit redirects, AI-voice-cloned approvals — detection alone is the wrong primitive.

The shape of detection

Modern fraud detection — behavioral analytics, statistical anomaly models, BEC scoring, transaction monitoring — runs after the action submits. The signals are real: unusual destination, unusual time, unusual amount, atypical user agent. The downside is structural: by the time the alert fires, the wire has cleared.

That tradeoff worked when most fraud cleared slowly and recovery was possible. It does not work when the action is an instant ACH or a same-day wire to a beneficiary that goes silent within minutes.

Where detection breaks for AI-era fraud

Behavioral models assume the legitimate user is a stable signal — same IP ranges, same device, same approval cadence. AI-voice-cloned phone calls reproduce the legitimate user's signal exactly. Prompt-injected agent runtimes operate from the same authenticated session, the same scope, the same device. The "anomaly" the detection model is looking for is no longer there.

EP changes the question. The system doesn't ask "does this transaction look anomalous?" — it asks "did a named human authorize this exact destination, this exact amount, with a valid handshake?" The answer is binary, cryptographic, and resistant to the channel the attack arrived on.

Side by side

DimensionPost-action fraud detectionEP pre-action authorization
Where the check runsAfter the action executesBefore the action executes — gates execution
Signal sourceBehavioral patterns, statistical modelsCryptographic handshake + named human signoff
False-positive costLegitimate transactions blocked or delayedAdds a signoff step on Tier-2 actions only
False-negative costFunds gone; recovery rareAction does not execute without valid handshake
Effectiveness on AI-voice / deepfakeDegrades — model-driven attacks evade behavior baselinesIndependent of attack channel — binds the action, not the actor channel
Effectiveness on insider misuseLimited — insider patterns look normalHandshake binds authority chain at request time
Audit evidenceAlert + post-hoc investigationSelf-verifying trust receipt issued at the gate
Composes withEP, MFA, audit logsDetection (defense in depth)

Defense in depth, not replacement

EP and detection compose. Detection is still the right control for Tier-0 reads, login risk scoring, fraud pattern discovery across the long tail, and downstream forensics. EP is the right control for the irreversible Tier-2 actions where post-hoc detection doesn't return your money.

A community bank running EP on wire releases keeps its existing transaction-monitoring stack. Most transactions never see EP — they're below the action-binding threshold. The wire-out-to-new-beneficiary action does. The handshake refuses to clear until a named officer signs off on the exact destination and amount.

Where this matters most

Financial use caseFinGuard
Pre-Action Authorization vs Post-Action Fraud Detection