Article 22. Algorithm Integrity: Third party assurance
Échec de l'ajout au panier.
Veuillez réessayer plus tard
Échec de l'ajout à la liste d'envies.
Veuillez réessayer plus tard
Échec de la suppression de la liste d’envies.
Veuillez réessayer plus tard
Échec du suivi du balado
Ne plus suivre le balado a échoué
Article 22. Algorithm Integrity: Third party assurance
-
Narrateur(s):
-
Auteur(s):
À propos de cet audio
Spoken by a human version of this article.
One question that comes up often is “How do we obtain assurance about third party products or services?”
Depending on the nature of the relationship, and what you need assurance for, this can vary widely.
This article attempts to lay out the options, considerations, and key steps to take.
TL;DR (TL;DL?)
- Third-party assurance for algorithm integrity varies based on the nature of the relationship and specific needs, with several options.
- Key factors to consider include the importance and risk level of the service/product, regulatory expectations, complexity, transparency, and frequency of updates.
- Standardised assurance frameworks for algorithm integrity are still emerging; adopt a risk-based approach, and consider sector-specific standards like CPS230(Australia).
About this podcast
A podcast for Financial Services leaders, where we discuss fairness and accuracy in the use of data, algorithms, and AI.
Hosted by Yusuf Moolla.
Produced by Risk Insights (riskinsights.com.au).
Ce que les auditeurs disent de Article 22. Algorithm Integrity: Third party assurance
Moyenne des évaluations de clientsÉvaluations – Cliquez sur les onglets pour changer la source des évaluations.
Il n'y a pas encore de critiques pour ce titre.