{"id":60492,"date":"2023-11-13T15:10:53","date_gmt":"2023-11-13T20:10:53","guid":{"rendered":"https:\/\/fidodev.wpengine.com\/?page_id=60492"},"modified":"2025-12-18T12:30:26","modified_gmt":"2025-12-18T17:30:26","slug":"fdo-certification-process-overview","status":"publish","type":"page","link":"https:\/\/fidoalliance.org\/fdo-certification-process-overview\/","title":{"rendered":"FDO Certification Process"},"content":{"rendered":"\n

FIDO Device Onboard Certification Process Steps and Requirements<\/h2>\n\n\n\n

Coming soon: A new journey for the FIDO laboratory pages. Stay tuned.<\/h3>\n\n\n\n

FDO Certification is independent of other FIDO Alliance certification programs. <\/p>\n\n\n\n

The path to achieving FDO certification<\/a> begins following product development.  Product development is out of the scope of the FDO Certification. Read all FDO specifications, certification requirements, and policies prior to applying for certification. Implementer guidance documentation and the FDO Developer Forum are available resources for product development support.<\/p>\n\n\n\n

The following table indicates the required steps for certification of each product. Select a step for more information.<\/p>\n\n\n\n

\n

FDO Implementation Class<\/strong><\/h3>\n<\/div>\n\n\n\n
<\/td>Device Onboarding (DO) Service<\/td>Device\/FDO-Enabled Device<\/td>Rendezvous Server (RV)<\/td><\/tr>
Step 1: Application<\/strong><\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Certification NDA<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Step 2: Conformance Testing<\/strong><\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Step 3: Interoperability Testing<\/strong><\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Step 4: Security Evaluation<\/strong><\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>Not Applicable<\/td><\/tr>
Level 1 (L1) VQ<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>Not Applicable<\/td><\/tr>
Step 5: Certification Request<\/strong><\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Certification Fee Invoicing and Payment<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Step 6: Certificate Issuance<\/strong><\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
TMLA<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Step 7: Certification Maintenance<\/strong><\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Derivative<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td><\/tr>
Delta<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>Not Applicable<\/td><\/tr>
Recertification<\/td>\"\u2705\"<\/td>\"\u2705\"<\/td>Not Applicable<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Step 1: Application<\/a><\/h2>\n\n\n\n
\n\n
\n
\"FIDO<\/figure>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

To begin the FDO Certification process, the Vendor must complete the FDO Certification Application, and the FIDO Certification Secretariat<\/a> will approve and confirm receipt. The application is intended to provide FIDO Certification with administrative details about the certifying Vendor, as well as provide general information about the implementation(s) seeking FDO Certification.<\/p>\n\n\n\n

The certification application is available here<\/a>.<\/p>\n\n\n\n

Additionally, if not already completed by the certifying Company, the Vendor must complete and submit a FIDO Certification Non-Disclosure Agreement (NDA) to the Certification Secretariat at: certification@fidoalliance.org<\/a>.<\/p>\n\n\n\n

Step 2: Conformance Testing<\/a><\/h2>\n\n\n\n
\n\n
\n
\"FIDO<\/figure>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

The Vendor self-administers and successfully completes FDO Conformance Testing by using the test tools and submitting results to the FIDO Certification Secretariat for any implementation seeking FDO Certification.<\/p>\n\n\n\n

Please reference the Functional Certification program page for more information about FDO Conformance Testing.<\/p>\n\n\n\n

Step 3: Interoperability Testing<\/a><\/h2>\n\n\n\n
\n\n
\n
\"FIDO<\/figure>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

Following successful completion of FDO Conformance Testing, the Vendor registers and successfully completes FDO Interoperability Testing for any implementation seeking FDO Certification.<\/p>\n\n\n\n

Please reference the Functional Certification program page for more information about FDO Interoperability Testing, including a schedule for upcoming FDO Interoperability Testing Events and a link for event registration.<\/p>\n\n\n\n

Step 4: Security Evaluation<\/a><\/h2>\n\n\n\n
\n\n
\n
\"FIDO<\/figure>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

The Security Evaluation step is required for certifying Device Onboarding Services<\/a> and Devices. Rendezvous Servers are exempt from completing Security Certification.<\/p>\n\n\n\n

After completing FDO Interoperability Testing, the Vendor must complete one FDO Vendor Questionnaire (VQ) per certifying product. Completed VQ(s) are to be submitted to:\u00a0fdo-security-evaluation@fidoalliance.org<\/a>.\u00a0<\/p>\n\n\n\n

The FIDO Security Secretariat will confirm submission receipt and review each VQ based on the order for which it was received. The Security Secretariat might request additional clarification and sometimes details. Upon successful evaluation, the Security Secretariat will mark the VQ approved and notify the Vendor and the Certification Secretariat.<\/p>\n\n\n\n

Step 5: Certification Request<\/a><\/h2>\n\n\n\n
\n\n
\n
\"FIDO<\/figure>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

The Vendor is requested by the FIDO Certification Secretariat to submit a Certification Request once all applicable certification testing and\/or evaluation steps are completed.<\/p>\n\n\n\n

Rendezvous Servers<\/strong><\/h3>\n\n\n\n

Following successful completion of Functional Certification requirements, the Certification Secretariat will send an email verifying all completed certification steps and request the Vendor to complete a Certification Request.<\/p>\n\n\n\n

Device Onboarding Services and FDO-Enabled Devices<\/strong><\/h3>\n\n\n\n

Following the successful completion of Functional and Security Requirements, the Certification Secretariat will send an email verifying all completed certification steps and request the Vendor to complete a Certification Request.

Certification Requests trigger an invoicing process to be completed between the Vendor and FIDO Alliance<\/a>. Upon receipt of payment by the Vendor, the Certification Secretariat will complete Certificate Issuance.<\/p>\n\n\n\n

Step 6: Certificate Issuance<\/a><\/h2>\n\n\n\n
\n\n
\n
\"FIDO<\/figure>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

Upon receipt of payment, the Certification Secretariat will assemble an FDO Certificate per certified product and issue each certificate to the Vendor by email. At this time, and if not already completed by the certifying Company, the Vendor is requested to complete a FIDO Trademark License Agreement (TMLA) in the event the Vendor wishes to use FIDO\u24c7 Certified logos. A fully executed TMLA is required per company per version of the TMLA. The Certification Secretariat will also request the Vendor to confirm the accuracy of the product and company fields that are enclosed as part of the FDO Certificate(s). If changes are required, the Vendor is asked to respond within 3 business days by email, noting any modifications.<\/p>\n\n\n\n

Following confirmation of the FDO Certificate details, the Certification Secretariat will upload the FDO Certified Product Certificate to the FIDO Certified Product Database.<\/p>\n\n\n\n

Step 7: Certification Maintenance<\/a><\/h2>\n\n\n\n
\n\n
\n
\"FIDO<\/figure>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

From time to time, there are changes that can occur with a FIDO\u00ae Certified Product. Rendezvous Servers might be licensed or sold, resulting in a requirement to complete Derivative certification maintenance. Device Onboarding Services and FDO-Enabled Devices might be affected by changes related to FDO Security Requirements, resulting in a requirement to complete an evaluation of such changes that are classified as non-interfering, minor, or major and relate to Derivative, Delta, and Recertification.<\/p>\n\n\n\n

Certification Maintenance includes requirements for all FIDO\u00ae Certified Products, lasting their full product lifecycle. Vendors of FIDO\u00ae Certified Products must adhere to and maintain their certifications through certification maintenance. Reference certification program policy documentation for complete certification maintenance, vendor obligations, and certification revocation information.<\/p>\n\n\n\n

Certification Maintenance processes are delineated by FDO Implementation Class. <\/p>\n\n\n\n

Rendezvous Servers<\/strong><\/h3>\n\n\n\n

Certification Maintenance for FIDO\u00ae Certified Rendezvous Servers comprises a process that verifies changes classified as non-interfering, relating to, and requiring Derivative certification for RV Server components. This process is made up of one step. The benefit of derivative certification is that the certifying implementations are not required to go through Functional Certification testing, and each derivative certification is subject to a lower fee than base certifications. <\/p>\n\n\n\n

The following scenarios are designed to help determine whether an implementation could qualify for a Derivative Certification:<\/p>\n\n\n\n

FIDO\u00ae<\/strong> Certified Implementation \u2013 Rendezvous Server<\/strong><\/td>Derivative?<\/strong><\/td><\/tr>
Company B using a publicly available FIDO\u00ae Certified Rendezvous Server from Company A, the company that completed the base certification, and the implementation used by Company B remains unchanged<\/td>Yes<\/td><\/tr>
Company B using a FIDO\u00ae Certified Rendezvous Server that was licensed or sold by Company A, the company that completed the base certification, and the implementation used by Company B remains unchanged<\/td>Yes<\/td><\/tr>
Company B using a FIDO\u00ae Certified Logo on their website relating to a FIDO\u00ae Certified Rendezvous Server component from another company<\/td>Yes<\/td><\/tr>
Company with FIDO\u00ae Certified implementation [Product v1.0] and introduces new product [New Product v2.0] that is different from Product 1.0, but the FIDO\u00ae Certified Rendezvous Server components have remained unchanged<\/td>Yes<\/td><\/tr>
Company with FIDO\u00ae Certified implementation [Product v1.0] and introduces new product [New Product v2.0] that is different from Product 1.0, including changes made to the FIDO\u00ae Certified Rendezvous Server components<\/td>No<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

To apply for Derivative certification of a FIDO\u00ae Certified Rendezvous Server, the Vendor must complete a Rendezvous Server Derivative Certification Request Form, including the base certificate number of the certified product.<\/p>\n\n\n\n

Device Onboarding Services and FDO-Enabled Devices<\/strong><\/h3>\n\n\n\n

Certification Maintenance for FIDO\u00ae Certified Device Onboarding Services and FDO-Enabled Devices comprises multistep processes that verify changes classified as either non-interfering, minor, or major. These changes may affect the FDO Security Requirements. Such a change might be a patch designed to correct a discovered flaw, an enhancement to a feature, add a new feature or any other change to the FIDO\u00ae Certified FDO Hardware and\/or Software.<\/p>\n\n\n\n

Step #1: Certification Maintenance Evaluation<\/strong><\/h4>\n\n\n\n

To evaluate the impact of these types of changes, the Vendor is required to complete the FDO Impact Analysis Report (FIAR) Form. A description of changes and the source certificate number of the certified product are submitted as part of the FIAR Form, which the FIDO Security Secretariat then evaluates. The described changes are analyzed, and their impact on the FDO Security Requirements coverage is determined. The Security Secretariat will provide a judgment based on the characteristics of the changes made to the certifying product. The outcome would be either that the changes are NON-INTERFERING, MINOR, or MAJOR, resulting in Derivative, Delta, or Recertification, respectively. <\/p>\n\n\n\n

To apply for Device Onboarding Services and FDO-Enabled Devices certification maintenance, the Vendor must complete a FIAR Form.<\/p>\n\n\n\n

The Security Secretariat will confirm submission receipt and review each FIAR Form based on the order for which it was received. The Security Secretariat might request additional clarification and sometimes details. Upon completion of the evaluation, the Security Secretariat will mark and specify the type of classified changes, noting approval or denial.  <\/p>\n\n\n\n

Step #2: Certification Maintenance Request<\/strong><\/h4>\n\n\n\n

Based on the results of the FIAR evaluation:<\/p>\n\n\n\n

For Derivative certification, the Vendor is requested to complete a Derivative\/Delta Certification Request Form.<\/p>\n\n\n\n

For Delta certification, the Vendor is requested to first complete Conformance and Interoperability Testing steps to confirm that the evaluated changes do not impact the functional characteristics of the product. Upon successful completion, the Vendor is requested to complete a Derivative\/Delta Certification Request Form.<\/p>\n\n\n\n

For Recertification, the Vendor is requested to begin the certification process at the start. <\/p>\n\n\n\n

Derivative\/Delta Certification Requests trigger an invoicing process to be completed between the Vendor and FIDO Alliance. Upon receipt of payment by the Vendor, the Certification Secretariat will complete Certificate Issuance.<\/p>\n","protected":false},"excerpt":{"rendered":"

FIDO Device Onboard Certification Process Steps and Requirements Coming soon: A new journey for the FIDO laboratory pages. Stay tuned. FDO Certification is independent of other FIDO Alliance certification programs.  […]<\/p>\n","protected":false},"author":59250,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"_EventAllDay":false,"_EventTimezone":"","_EventStartDate":"","_EventEndDate":"","_EventStartDateUTC":"","_EventEndDateUTC":"","_EventShowMap":false,"_EventShowMapLink":false,"_EventURL":"","_EventCost":"","_EventCostDescription":"","_EventCurrencySymbol":"","_EventCurrencyCode":"","_EventCurrencyPosition":"","_EventDateTimeSeparator":"","_EventTimeRangeSeparator":"","_EventOrganizerID":[],"_EventVenueID":[],"_OrganizerEmail":"","_OrganizerPhone":"","_OrganizerWebsite":"","_VenueAddress":"","_VenueCity":"","_VenueCountry":"","_VenueProvince":"","_VenueState":"","_VenueZip":"","_VenuePhone":"","_VenueURL":"","_VenueStateProvince":"","_VenueLat":"","_VenueLng":"","_VenueShowMap":false,"_VenueShowMapLink":false,"footnotes":""},"content-type":[],"class_list":["post-60492","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/pages\/60492","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/users\/59250"}],"replies":[{"embeddable":true,"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/comments?post=60492"}],"version-history":[{"count":0,"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/pages\/60492\/revisions"}],"wp:attachment":[{"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/media?parent=60492"}],"wp:term":[{"taxonomy":"content-type","embeddable":true,"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/content-type?post=60492"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}