Datos Insights’ Sixth Annual Financial Crime & Cybersecurity Forum: Fortifying Defenses for a Secure Tomorrow

Contending with rapidly evolving risks and an increasingly volatile world, financial crime fighters require innovative ideas to build stronger defenses, extend intelligence sharing, and optimize investments.

Datos Insights’ sixth annual Financial Crime & Cybersecurity Forum included over 350 registered attendees, with over 60 fraud, anti-money laundering, and cybersecurity experts and thought leaders from financial institutions, insurers, fintech companies, e-commerce merchants, and other organizations speaking on 30 individual panels and other thought leadership sessions. The discussions spanned critical topics, such as elevating the defenses against scams, mule activity, check fraud, and internal fraud, and prioritizing customer identity and risk-based approaches.

This report explores the key themes across fraud, authentication, and AML that emerged over the two-day event as well as the opportunities, lessons learned, and insights shared by the panelists. Datos Insights’ Cybersecurity practice published a companion report exploring the key themes and insights that emerged from the cybersecurity thought leadership sessions.

Clients of Datos Insights’ Cybersecurity and Fraud & AML services can download this report.

This report mentions Alloy, Anonybit, ARGO Data, Arkose Labs, AuthenticID, Biocatch, Bottomline, Callsign, Celebrus, DataVisor, Early Warning, Effectiv, Entersekt, Featurespace, Feedzai, Fenergo, FICO, Field Effect, Greenway Solutions, Guidehouse, HAWK:AI, IDology, IDverse (formerly OCR Labs), Innovis, IronVest, Kevari, LexisNexis Risk Solutions, Mastercard, Mission Omega, Mitek Systems, Napier, Neustar/TransUnion, NICE Actimize, Nuance, Okta, OrboGraph, Outseer, Pindrop, PricewaterhouseCoopers (PwC), Prove, Quantifind, SAS, Sayari, Sentilink, Socure, Spycloud, The Knoble, ThreatMark, TTEC, and Verafin.

Related Content

Get Summary Report

"*" indicates required fields

This field is for validation purposes and should be left unchanged.