Article 22. Algorithm Integrity: Third party assurance
No se pudo agregar al carrito
Solo puedes tener X títulos en el carrito para realizar el pago.
Add to Cart failed.
Por favor prueba de nuevo más tarde
Error al Agregar a Lista de Deseos.
Por favor prueba de nuevo más tarde
Error al eliminar de la lista de deseos.
Por favor prueba de nuevo más tarde
Error al añadir a tu biblioteca
Por favor intenta de nuevo
Error al seguir el podcast
Intenta nuevamente
Error al dejar de seguir el podcast
Intenta nuevamente
Article 22. Algorithm Integrity: Third party assurance
-
Narrado por:
-
De:
Acerca de esta escucha
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).
adbl_web_global_use_to_activate_T1_webcro805_stickypopup
Todavía no hay opiniones