The problem with internal device IDs
By André Ferraz, CEO and Co-Founder at Incognia
I’ve been hearing from a lot of companies that they’re looking for new fraud prevention solutions.
When I ask about their device ID solution, many tell me it was built internally.
But unfortunately, many downstream fraud issues occur because companies use an unreliable device ID that makes it nearly impossible for them to recognize bad actors.
Why is the ‘build-your-own’ device ID problematic?
First, building a reliable device ID is extremely difficult. Re-identifying good users is pretty straightforward. But bad actors are constantly working to conceal themselves–and this is getting easier for them due to new privacy controls created by operating systems and browsers.
Another factor that makes it particularly difficult is that the OS-provided device fingerprints that teams often use when building an internal device ID weren’t designed for fraud prevention. They’re a shaky foundation to build on.
But even if you do manage to build a working device ID solution, there’s a third problem that many don’t consider as much as they should:
The endless maintenance and upgrading you’ll have to do to ensure it remains effective in the face of constantly evolving fraudster tactics.
At first, your new device ID may seem like it’s doing a pretty good job of defending against fraud.
But once fraudsters detect your new defense, they adapt and quickly pivot to new evasion methods.
When they find a vulnerability in your solution, they exploit it and find ways to automate that process. And then they often share their tactics with their community so that other fraudsters can follow suit.
This turns security into a continuous game of catch-up.