Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

6/20/2019
02:00 PM
Cleber Martins
Cleber Martins
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
50%
50%

'Democratizing' Machine Learning for Fraud Prevention & Payments Intelligence

How fraud experts can fight cybercrime by 'downloading' their knowledge and experience into computer models.

Throughout the financial industry, executives are acknowledging that machine learning can quickly and successfully process the vast volume and variety of data within a bank's operations — a task that's nearly impossible for humans to do at the same speed and scale. However, only about half of enterprises are using machine learning. Why? A bank-wide machine learning project is a huge undertaking, requiring major investment in technology and human resources.

Moreover, past projects that have failed to deliver a return on investment (ROI) have led to internal disappointment and, in some cases, mistrust in the technology. However, with smaller, more tactical machine learning projects that can be rapidly deployed, banks can reap the benefits from Day One. One such project is fraud prevention.

The current barrier to delivering fraud protection through machine learning often lies in the solutions themselves, which require data scientists to create the initial models. A fraud expert knows that a specific correlation between transaction types in a sequence is a strong fraud indicator, but the data scientist will need many more interactions with the same data to draw the same conclusion.

Fraud Experts or Data Scientists?
A machine learning model is only as good as the instructions it is given. This can be particularly challenging while setting up fraud prevention algorithms because fraud is a relatively small percentage of successful transactions, which means the model has fewer opportunities to learn. As a result, solutions that enable fraud experts, instead of data scientists, to input the initial correlations will deliver results faster in terms of identifying new correlations across different data sets as they're more familiar with the instances where fraud is likely to occur. This allows the organization to reduce the time to ROI of their machine learning projects.

This "democratization of machine learning" empowers fraud experts to "download" their knowledge and experience into computer models. It's particularly effective in areas where fraud has not yet reached critical mass to support fraud experts as they use their experience and instincts to investigate certain transactions or customer behaviors, even if they are not yet fraudulent or highly indicative of fraud. Feedback based on these kinds of instincts will aid the machine learning model to fine-tune itself, and improve accuracy and consistency in identifying more complex fraud indicators.

Teaching the Machine
Continuous involvement of fraud experts is key to developing the machine learning model over time. By bringing fraud experts closer to machine learning, they have transparent views into the models and can apply strategies and controls to best leverage the outcome of the intelligence from the models. As they input to the model, they're able to investigate the output as the model generates intelligence and use their human expertise to confirm fraud instances. They can also combine their all-encompassing customer view with insights correctly generated by the model.

If the "human intelligence" confirms the insights, these can be fed back into the model. If the model consistently flags a correlation between data sets as potential fraud and the analysts consistently confirm this as fraud, then a strategy and control based on this information can be added to underpin the model. These can, in turn, be used to automate the decisions that fraud analysts themselves have consistently made, and, ultimately, reduce the need for automatic actions that impact the customer experience, such as freezing a credit card when a suspicious purchase is made — even though the purchase is legitimate.

Related Content:

Cleber Martins is head of payments intelligence, ACI Worldwide. He has nearly two decades' experience in fraud prevention and anti-money laundering strategies. View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
Black Hat Q&A: Hacking a '90s Sports Car
Black Hat Staff, ,  11/7/2019
The State of Email Security and Protection
Mike Flouton, Vice President of Email Security at Barracuda Networks,  11/5/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprise
Assessing Cybersecurity Risk in Today's Enterprise
Security leaders are struggling to understand their organizations risk exposure. While many are confident in their security strategies and processes, theyre also more concerned than ever about getting breached. Download this report today and get insights on how today's enterprises assess and perceive the risks they face in 2019!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18881
PUBLISHED: 2019-11-12
WSO2 IS as Key Manager 5.7.0 allows unauthenticated reflected XSS in the dashboard user profile.
CVE-2019-18882
PUBLISHED: 2019-11-12
WSO2 IS as Key Manager 5.7.0 allows stored XSS in download-userinfo.jag because Content-Type is mishandled.
CVE-2019-18873
PUBLISHED: 2019-11-12
FUDForum 3.0.9 is vulnerable to Stored XSS via the User-Agent HTTP header. This may result in remote code execution. An attacker can use a user account to fully compromise the system via a GET request. When the admin visits user information under "User Manager" in the control panel, the pa...
CVE-2019-18874
PUBLISHED: 2019-11-12
psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object.
CVE-2019-18862
PUBLISHED: 2019-11-11
maidag in GNU Mailutils before 3.8 is installed setuid and allows local privilege escalation in the url mode.