Article 22. Algorithm Integrity: Third party assurance
Failed to add items
Sorry, we are unable to add the item because your shopping cart is already at capacity.
Add to Cart failed.
Please try again later
Add to Wish List failed.
Please try again later
Remove from wishlist failed.
Please try again later
Adding to library failed
Please try again
Follow podcast failed
Please try again
Unfollow podcast failed
Please try again
Article 22. Algorithm Integrity: Third party assurance
-
Narrated by:
-
By:
About this listen
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).
No reviews yet