Podcast
Root Causes 31: Using PKI to Authenticate Phone Callers


Hosted by
Tim Callan
Chief Compliance Officer
Jason Soroko
Fellow
Original broadcast date
August 12, 2019
Few people know that caller ID numbers have no identity value as they are completely self-reported. This fact enables the plague of robocalling scams sweeping our society right now. Join our hosts as they discuss public telephony systems and other environments that suffer from this problem, where this situation creates vulnerabilities, and what can be done about it.
Podcast Transcript
Lightly edited for flow and brevity.
The same thing is true for a caller ID phone number. A lot of people don’t know this but when you get those irritating robocalls on your cell phone, you might hit “block this caller,” but that’s of no consequence because what you’re blocking self-reported caller ID phone number and since that’s just being spoofed anyways that’s just made up, the next time you get that robocall from the same robocaller, it’s just going to be a different number.
Now compare that to other digital systems. You and I have talked in the past about the need for certificates to provide strong identity in, let’s say, a DevOps environment because we have to know that every single task is real and every single container is real. And now compare that to our world of telephony where they’re just saying who they are.
In the phone world, the FCC just recently held a summit for something that’s called SHAKEN/STIR (Signature-based Handling of Asserted Information Using toKENs and Secure Telephone Identity Revisited). This group was talking about using PKI and key-based identity in the telephony system to ensure that those caller ID numbers are accurate. Basically we’re seeing the real number that that caller really has inside of the phone system.
I know that, after years of working, GSMA-type consortium standards that we’ve seen over the years, PKI has been brought to bear on a lot of it. Other choices have been made in the past, typically for devices connecting to a network. But this gets to the heart of who’s calling me.
Using PKI to solve that, I think that the solution that I’ve looked at on the surface seems reasonable. Whether or not a carrier or someone might be, might actually take this on, I'm not sure what kind of consortiums and standards and things that have to be completely baked out, but I think that the proposal definitely makes sense. For this SHAKEN/STIR framework, it’s going to be interesting to see whether or not somebody picks it up and carries it forward into an actual operational format. What this will look like in operation versus just the proposed framework might be a different story. But let’s take a look at what the SHAKEN and STIR actually stand for.
But you know this is a problem. I know a lot of people – and I'm one of them – I do not answer my telephone if I do not recognize that number because it’s just going to be a waste of my time. And what’s the cost of this in terms of human productivity? And what’s the cost of this in terms of our being able to communicate with each other effectively? And then ultimately these robocalls wouldn’t be running if they weren’t economical feasible which means that somebody’s being cheated out of their money. So what’s the cost of that?
And so, I ended up getting a text message saying, “Hey is that you?” Isn’t it interesting? But the solutions for this do exist and I think that the SHAKEN/STIR framework that’s being presented here is completely reasonable. It’s just I would like to talk to the carriers and others who would have to implement this. What does this look like in reality?
You know the concept of splitting workload into various virtual units. Security just becomes more and more and more of a head scratcher, but solving the fundamental problem of who the heck is calling me, that’s all we’re talking about right now, and at least there’s something in front of us that looks reasonable.

