The fraud engine saw transactions, not campaigns. A payments company, before Ollandi: - The fraud engine scored each transaction, not the campaign behind it - Credential stuffing, API abuse and support-account misuse sat in separate systems - Attacks reached the fraud engine only after the attacker had access After Ollandi: - Weak signals across identity, APIs, cloud and endpoints: one threat sequence per attack - Fraud and security teams work from a single case - Containment recommended by Ollandi, approved by an operator, checked so payments keep flowing How it runs: operating mode: Assisted Response; works with: The existing fraud engine, which keeps every transaction decision; coverage: Identity, API gateways, cloud workloads, endpoints and payment channels. In production, our previous generation (PulseADT on ADT-4 Pro) recorded a false positive rate of 1.2%, against an industry average of 23.5%. Results depend on the telemetry available. Read the full story at glemad.com, and request an executive briefing at ollandi.com. #Ollandi #CyberSecurity #AI #Payments #FinTech
0000