A
Anthony Guethert
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
Sep 8, 2026
InformationWeek Podcast: Repercussions of compliance cascades
12:39
12:51
13:08
17:16

Anthony GuethertGUEST
But I personally feel quite a large obligation on myself if I'm going to choose to onboard or take on a very large vendor.

Anthony GuethertGUEST
I think there is substantially more due diligence needed, and I think you need a very high degree of care and a very high degree of curiosity to uncover what you're really signing up to and your dependency levels on them.

Anthony GuethertGUEST
And so, for example, if you think about the size and scale and speed of some of the AI companies out there building front-end large language models, right? Some of them are pretty large.

Joao-Pierre RuthHOST
When the dust settles after an issue, an incident, how do you go about determining whether or not you want to continue? If you've done the hog border with a vendor, how do you determine whether or not you want to continue with the vendor that might've been at the heart of the liability? Anthony, if you could lead us off again with your thoughts.
