Dana KaufmanHost
Jeroen KempermanHost
Dario SaliceHostTom WilliamsonGuest
In the industry, we deprecate something, we turn it off, and then it's gone, right? We delete the code.

It can be, you know, just basically removing something you've built before in your business.

Well, usually they're what we call legacy features are old, you know, once priority, now not so priority, but... a big reason that I've seen is because it's either being actively exploited by bad actors and usually more bad actors on using those features than, than actual users or the, the usage is kind of declined and you know, it's just sitting there and it's a surface area that is ripe for attack.

And yeah, And then other things you think about is like if it's not core of the business anymore and you're you're putting resources and maintenance into it, right, like it might be a cost sink.

And it might not be the direction you want to go anymore, right? Like it's just a legacy old feature that's no longer valuable.

You might just have a few people using it and there's newer, better ways to do what you need to do.

You know, you want to push everybody to the newer direction rather than the old direction.

Daria, can you help us with some examples, things you've noticed that companies have turned off? Or Tom, things that you've noticed that companies have turned off? You're muted, Daria.

In our space, there's often, for example, support for old devices, like old login flows, old recovery flows that maybe work on older devices that at some point you just stop wanting to support, like as Dana mentioned.

Sometimes the old features or the features you want to deprecate, they're at some point used more by attackers than by good people.

So I've been in a few deprecation projects where, for example, we would disable support for old browser stacks, technology stacks, or old Android versions.

And because one thing we noticed at some point is that the the people who use these old login flows or recovery flows are disproportionately attackers over good users.

Because I'm not saying nobody uses an Android 3.0 device or 5.0 device anymore, but practically nobody does.

It's easier if you have good data to prove that it's mainly attackers because attackers can't call and be upset with you that you deprecated something.

In the industry, we deprecate something, we turn it off, and then it's gone, right? We delete the code.

It can be, you know, just basically removing something you've built before in your business.

Well, usually they're what we call legacy features are old, you know, once priority, now not so priority, but... a big reason that I've seen is because it's either being actively exploited by bad actors and usually more bad actors on using those features than, than actual users or the, the usage is kind of declined and you know, it's just sitting there and it's a surface area that is ripe for attack.

And yeah, And then other things you think about is like if it's not core of the business anymore and you're you're putting resources and maintenance into it, right, like it might be a cost sink.

And it might not be the direction you want to go anymore, right? Like it's just a legacy old feature that's no longer valuable.

You might just have a few people using it and there's newer, better ways to do what you need to do.

You know, you want to push everybody to the newer direction rather than the old direction.

Daria, can you help us with some examples, things you've noticed that companies have turned off? Or Tom, things that you've noticed that companies have turned off? You're muted, Daria.

In our space, there's often, for example, support for old devices, like old login flows, old recovery flows that maybe work on older devices that at some point you just stop wanting to support, like as Dana mentioned.

Sometimes the old features or the features you want to deprecate, they're at some point used more by attackers than by good people.

So I've been in a few deprecation projects where, for example, we would disable support for old browser stacks, technology stacks, or old Android versions.

And because one thing we noticed at some point is that the the people who use these old login flows or recovery flows are disproportionately attackers over good users.

Because I'm not saying nobody uses an Android 3.0 device or 5.0 device anymore, but practically nobody does.

It's easier if you have good data to prove that it's mainly attackers because attackers can't call and be upset with you that you deprecated something.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.