From the start the controller should determine and document its approach to bias and demographic differentials, set policies on training and pilot data so it represents the population the system will be used on, engage vendors on how they prevented technical bias, choose suitable camera resolution and lighting, test the equipment fully, be able to tell true from false matches, record false positive and false negative rates and adjust the system where they are too high, and explain its mitigations in the DPIA.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.