Law / Frameworks / NIST Privacy Framework / Identify-P
NIST Privacy Framework, Identify-PID.RA-P2
Data analytic inputs and outputs are identified and evaluated for bias.NIST Privacy Framework, version 1.0, January 2020, ID.RA-P2
We read each law below as bearing on this control. That does not mean the control, done well, meets the law: what each law asks is on its own page. Law library as of .
- 8
- laws
- 7
- jurisdictions
- 0
- with court rulings behind them
- 3
- not yet in force
Related controls in other frameworks the same duties, in at least two laws we track, reach both
- NIST AI RMFMEASURE 2.11 Fairness and bias – as identified in the MAP function – are evaluated and..., 4 laws
- NIST AI RMFMAP 2.3 Scientific integrity and TEVV considerations are identified and documented,..., 3 laws
- NIST AI 600-1GAI-RISK-07 Human-AI Configuration, 3 laws
- NIST AI 200-22.3 Apply & Measure, 3 laws
- NIST AI 200-24.3 Composing a TEVV Toolbox, 3 laws
- OWASP LLM Top 10LLM03:2026 Excessive Agency, 3 laws
- OWASP Agentic Top 10ASI09 Human-Agent Trust Exploitation, 3 laws
- MIT mitigations1.1 Board Structure & Oversight, 3 laws
- MIT mitigations1.2 Risk Management, 3 laws
- MIT mitigations3.5 Post-deployment Monitoring, 3 laws
- 1 more in the MIT mitigations
- FINOS AIGFAIR-PREV-005 System Acceptance Testing, 3 laws
- FINOS AIGFAIR-PREV-006 Data Quality & Classification/Sensitivity, 3 laws
- FINOS AIGFAIR-PREV-024 Human-in-the-Loop Action Approval Gate, 3 laws
- 3 more in the FINOS AIGF
- ETSI EN 304 2235.1.4-1 Capability for human oversight designed in and maintained., 3 laws
- ETSI EN 304 2235.2.1-1 Full inventory of assets, including their dependencies and connections., 3 laws
- ETSI EN 304 2235.2.4-1 Developers keep an audit trail of system design and post-deployment..., 3 laws
- 1 more in the ETSI EN 304 223
A law in force is unmarked; the rest wear their state: not yet in force
AI sector rules
3 laws, 3 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| FSC Fintech Series Guidance Notes 4, responsible use of artificial intelligence in financial services |
The Commission advises you to identify and mitigate biases in AI algorithms and datasets, and to perform regular audits to assess and address biases in AI models. |
|
| Guidance Note on the Consumer Protection and Responsible Adoption and Use of Artificial Intelligence and Machine Learning by Licensed Financial Institutions in the U.A.E. |
Make sure AI and ML systems do not result in discriminatory or manipulative outcomes, train models on data that is sufficiently accurate, relevant and representative of the customer populations they are applied to, and test AI once a year or each time a model is upgraded, materially changed or introduced to identify and remediate undue or unintended biases (Sections 3(a) to 3(c)). |
|
| Model risk management principles for banks |
Develop models under documented standards: a clear statement of purpose and design objectives, development data shown to be suitable, representative and free of inappropriate bias and used in compliance with data privacy and other relevant data regulations, development testing against the design objectives including for material changes in dynamic models that adapt, recalibrate or change autonomously, justified and recorded expert-judgement adjustments, and documentation detailed enough for an independent third party to understand and replicate the model (Principle 3). |
AI risk obligations
2 laws, 2 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Clinical Decision Support Systems Bias Mitigation Act (SB 503) from , in 7 weeks |
Make reasonable efforts to identify any clinical decision support system you develop or deploy that is known or has a reasonably foreseeable risk of biased impacts in health programs or activities |
|
| AI Act, Article 10 (data and data governance) from , in 13 months |
Apply data governance and management practices appropriate to the system's intended purpose, covering your design choices; how you collected the data and, for personal data, why you originally collected it; your data-preparation operations, such as annotation, labelling, cleaning, updating, enrichment and aggregation; the assumptions you made about what the data measures and represents; an assessment of whether the data sets you need are available, sufficient in quantity, and suitable; examination of the data for biases likely to affect health and safety, harm fundamental rights, or lead to discrimination prohibited under Union law, especially where one operation's data outputs become a later operation's inputs; and measures to detect, prevent and mitigate any bias you find. |
Sensitive categories
2 laws, 2 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Law No. 133/V/2001 on the Protection of Personal Data, sensitive data categories |
Do not use profiling that leads to discrimination against individuals on the basis of the special categories of personal data. |
|
| Anti-Money-Laundering Regulation, Special Categories and Criminal Offence Data Processed by Obliged Entities (Articles 76 and 77(3)) from , in 8 months |
Do not take decisions that would lead to biased and discriminatory outcomes on the basis of personal data covered by Article 9 of Regulation (EU) 2016/679 (Article 76(2), point (c)). |
Data subject rights
1 law, 1 jurisdiction| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Personal Information Protection Law, automated decisions |
Ensure transparency and non-discriminatory treatment in any automated decision made using personal information, and do not use it for unreasonable differential pricing. |
Full text of the NIST Privacy Framework, public domain (a US government work). Every control of the framework.