How Accredited Certification Bodies differ from the Accelerator

The DIFC Reg 10 Accredited Certification Body Framework defines an Accredited Certification Body as an entity with the ability to certify a Certification Applicant's System for High Risk Processing. Part 1 of that framework is what an Accredited Certification Body applicant has to prove: independence, expertise, written undertakings, established procedures, conflicts of interest, and so on.

The Accelerator Framework is a different instrument entirely. It is a sandbox for Participants (developers, deployers and operators) to test their own systems for privacy-by-design compliance. The Accelerator Testing Team is the reviewer, not an Accredited Certification Body. The framework explicitly lets Participants pick the assessment model, whether Open Loop, OECD, Humane Intelligence or Bespoke, and can run as a bolt-on to UAE Reg Lab, UK ICO or EU AI Act Article 57 sandboxes.

Nowhere in the Accelerator Framework does a Participant need to be, or to use, an Accredited Certification Body. Accredited Certification Body certification is what an entity does for commercial deployment under Reg 10.3.3. It is not what an entity does to enter the sandbox. The entire Part 1 of the Accredited Certification Body Framework is orthogonal to Accelerator participation.

The only place the Accredited Certification Body criteria intersect with the Accelerator is on the tester side, in abbreviated form, as part of Accelerator Testing Team qualification. That is the DIFC Commissioner's selection problem, not the Participant's.