Algorithmic bias: what it is and how compliance programmes address it
Algorithmic bias is a systematic and unfair difference in outcomes produced by an AI system, caused by training data, feature selection or design choices that disadvantage one group over another. The EU AI Act, ISO 42001 and the NIST AI RMF all treat bias as a risk that must be assessed and mitigated.
Where algorithmic bias comes from
Bias can enter an AI system at every stage. Historical data reflects past decisions, including unfair ones. Feature selection can use proxies for protected characteristics. Model architecture can amplify small imbalances. And evaluation metrics can hide disparities by averaging across groups.
Because the causes are varied, there is no single fix. A compliance programme treats bias as a risk: assess it, apply controls, test for it and monitor after deployment.
What the frameworks say
The EU AI Act requires providers of high-risk AI systems to take steps to detect and correct bias in training data and to test for it before and after deployment. ISO 42001 addresses bias through the risk assessment process and the controls in Annex A. The NIST AI RMF's Measure function includes fairness metrics.
- EU AI Act: data governance and bias testing for high-risk systems
- ISO 42001: risk assessment covering harm to individuals
- NIST AI RMF: fairness as a dimension of trustworthy AI
- All three: monitoring after deployment to catch drift
Addressing bias in your programme
In Certifyi, bias is a risk in the AI risk register, linked to the AI system it applies to. The controls that treat it — data audits, testing, monitoring, human review — sit in the control set and carry evidence like any other control.
- AI risk management: register the risk and link it to controls.
- Human oversight: a person reviews high-stakes decisions.
- AI transparency: disclose limitations and known biases.
Working through this for an audit?
Talk it through with someone who has run the audit before, or look up another term.
- Each customer workspace has its own database
- Every change written to a tamper-evident activity log
- Auditors get scoped, read-only access
- AI suggestions wait for a person to accept them