Couverture de Who Should Own AI Risk With StackAware

Who Should Own AI Risk With StackAware

Who Should Own AI Risk With StackAware

Écouter gratuitement

Voir les détails

Offres de saison | 0,99 € par mois pendant les 3 premiers mois

5,99 €/mois par la suite. Des conditions s’appliquent. Annulation mensuelle possible.
À propos de ce contenu audio

Who should accept the risk of an AI system when the benefits belong to the business but security and compliance teams are expected to manage the consequences?

In this episode of Business of Cybersecurity, I speak with Walter Haydock, founder and CEO of StackAware, about the decisions behind responsible AI adoption. Walter's background spans Marine Corps reconnaissance and intelligence, national security and enterprise technology. He explains how those experiences shaped his approach to uncertainty and why delaying a decision can create risks of its own.

We discuss his argument that the business leader benefiting from an AI system should own the associated risk decision. Security, legal and compliance teams bring expertise to that assessment, but Walter questions what happens when they are asked to accept responsibility without receiving the business benefit. I also ask what evidence a board should request before approving autonomous AI. Walter recommends comparing expected value, operating costs and error rates with the existing process, alongside the effects on confidentiality, integrity and availability.

The conversation includes his account of working with Embold Health on governance, risk assessment and security testing for EVA, its virtual assistant for healthcare navigation. We consider how natural language can help people find appropriate providers and why the controls around an application need to support its intended purpose. Walter also outlines questions smaller organizations can ask AI suppliers about data use, retention and output quality, while recognizing that the answers depend on the service and agreement involved.

We then discuss governance as ongoing work. Models, interfaces and integrations can change after a system is approved, so teams need a way to notice different behavior and reassess whether the service still meets their expectations. Walter describes how a tiered approach can give lower-risk activities a clearer path forward while reserving greater scrutiny for more consequential uses. For leaders trying to make decisions without waiting for perfect certainty, the discussion connects opportunity with responsibility. How is your organization deciding which AI risks to accept, and who remains accountable afterward? Please share your thoughts with me.

adbl_web_anon_alc_button_suppression_t1
Aucun commentaire pour le moment