T
Tom Williamson
1
APPEARANCES
1
PODCASTS
012
DEC 30
JAN 6
JAN 13
JAN 20
JAN 27
FEB 3
FEB 10
FEB 17
FEB 24
MAR 3
MAR 10
MAR 17
MAR 24
MAR 31
APR 7
APR 14
APR 21
APR 28
MAY 5
MAY 12
MAY 19
MAY 26
JUN 2
JUN 9
JUN 16
JUN 23
JUN 30
JUL 7
JUL 14
JUL 21
JUL 28
AUG 4
AUG 11
AUG 18
AUG 25
SEP 1
SEP 8
SEP 15
SEP 22
SEP 29
OCT 6
OCT 13
OCT 20
OCT 27
NOV 3
NOV 10
NOV 17
NOV 24
DEC 1
DEC 8
DEC 15
DEC 22
DEC 29
JAN 5
JAN 12
JAN 19
JAN 26
FEB 2
FEB 9
FEB 16
FEB 23
MAR 2
MAR 9
MAR 16
MAR 23
MAR 30
APR 6
APR 13
APR 20
APR 27
MAY 4
MAY 11
MAY 18
MAY 25
JUN 1
JUN 8
JUN 15
JUN 22
JUN 29
JUL 6
JUL 13
JUL 20
JUL 27
AUG 3
AUG 10
AUG 17
AUG 24
AUG 31
SEP 7
SEP 14
SEP 21
SEP 28
OCT 5
OCT 12
OCT 19
OCT 26
NOV 2
NOV 9
NOV 16
Nov 17, 2026
Episode #1 - Hot to turn stuff off
4:12

Dario SaliceHOST
But obviously, it's harder when you deprecate something that is still being used by good users and puts them at risk of getting locked out.
T
4:21Tom WilliamsonGUEST
I would give an example from my professional life, which is kind of tangential in the sense that it's not the deprecation of an end-user facing feature, but in the infrastructure world, obviously the pace of acceleration of, for example, deprecation of cryptography standards and algorithms is something that often happens.
T
4:44Tom WilliamsonGUEST
So you'll see, like, you know, for example, deep within like a managed server estate, like, you know, someone from a CISO function will come out and say, Well, you've got about a bunch of SHA-1 in operation throughout this kind of application or server portfolio, and that's going to have to go.
T
5:01Tom WilliamsonGUEST
And then, you know, it's always the case of kind of doing a lot of digging and inventory management and kind of like, you know, build materials to know exactly where all of that cryptography is in use and managing the graceful, let's say, upgrade towards a more secure standard.
T
9:08Tom WilliamsonGUEST
we've touched on in previous podcasts to a certain extent, which is when you talk about these really large platform ecosystem vendors, to what extent do they have an obligation or a mandate to push wider security best practice to a certain extent against, with friction towards users? Because obviously in security, often there's a trade-off between usability and security, right? So in the case that you described there, of course, it's more convenient for people with programmatic connections just to use Basic Auth.
T
9:45Tom WilliamsonGUEST
You don't have to insert a human in the loop for any kind of second factor prompts for a machine logon or so.
