{"id":84416,"date":"2025-04-04T07:35:17","date_gmt":"2025-04-04T11:35:17","guid":{"rendered":"https:\/\/fidoalliance.org\/?page_id=84416"},"modified":"2026-02-17T15:30:25","modified_gmt":"2026-02-17T20:30:25","slug":"passkeypledge","status":"publish","type":"page","link":"https:\/\/fidoalliance.org\/passkeypledge\/","title":{"rendered":"The Passkey Pledge"},"content":{"rendered":"\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"3126\" height=\"626\" src=\"https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner.png\" alt=\"FIDO Alliance\" class=\"wp-image-84453\" srcset=\"https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner.png 3126w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-300x60.png 300w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-1024x205.png 1024w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-768x154.png 768w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-1536x308.png 1536w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-2048x410.png 2048w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-270x54.png 270w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-400x80.png 400w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-600x120.png 600w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-1280x256.png 1280w, https:\/\/fidoalliance.org\/wp-content\/uploads\/2025\/04\/Passkey-Pledge-Banner-500x100.png 500w\" sizes=\"auto, (max-width: 3126px) 100vw, 3126px\" \/><\/figure>\n\n\n\n<p class=\"has-text-align-left\">The Passkey Pledge is a voluntary pledge for online service providers and authentication product and service vendors. Individuals are not scoped in the pledge, though are encouraged to voice their support for passkeys through their preferred channels.&nbsp;<\/p>\n\n\n\n<p>Participation in this pledge means that service providers and vendors commit to make a good-faith effort to work towards the stated goals throughout the year. Companies that make measurable progress towards the pledged goal should publicly document their achievements within one year of signing the pledge. Companies that do not make measurable progress are still encouraged to share their efforts, challenges, and approaches within the same timeframe so that others can learn. This pledge is voluntary and not legally binding.<\/p>\n\n\n\n<p>The FIDO Alliance recognizes and appreciates service providers and vendors who have already implemented passkey support for sign-ins or in their products. Companies that already support passkeys should publicly state their implementation methods and the resulting impacts, if possible.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Take the Passkey Pledge<\/h2>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-a89b3969 wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"#fill-out-the-form\">Take the Pledge<\/a><\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-a89b3969 wp-block-buttons-is-layout-flex\" id=\"signed-pledges\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"#See-Who-Has-Signed-the-Pledge\">See Who Has Signed the Pledge<\/a><\/div>\n<\/div>\n\n\n\n<p>Companies taking the pledge commit to make a good-faith effort to work towards these stated goals throughout the year:<\/p>\n\n\n\n<p><strong>For service providers that have an active implementation of passkeys for sign-in<\/strong><br>Within one year of signing the pledge, demonstrate actions taken to measurably increase the use of passkeys by users when signing into the company\u2019s services.<\/p>\n\n\n\n<p><strong>For service providers that are in the process of implementing passkeys for sign-in<\/strong><br>Within one year of signing the pledge, demonstrate measurable actions taken to enable passkeys for signing into the company\u2019s services.<\/p>\n\n\n\n<p><strong>For vendors with a FIDO-based products and\/or service<\/strong><br>Within one year of signing the pledge, demonstrate actions taken to measurably increase the use of passkeys through adoption of the company\u2019s products and\/or services.<\/p>\n\n\n\n<p><strong>For vendors developing FIDO-based products and\/or services<\/strong><br>Within one year of signing the pledge, demonstrate measurable actions to FIDO certify its products and launch a product or service with passkey sign-in support.<\/p>\n\n\n\n<p><strong>For industry associations and standards organizations&nbsp;<\/strong><br>Within one year of signing the pledge, demonstrate actions to increase the visibility and benefits of passkey sign-ins.<\/p>\n\n\n\n<p><strong>Taking Action: Resources to Help Organizations to Fulfill the Pledge<\/strong><\/p>\n\n\n\n<p>The FIDO Alliance has resources and best practices for Passkey Pledge organizations to take action, including:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sharing their commitment to the Passkey Pledge via external communications channels<\/li>\n\n\n\n<li>Leveraging the guidance on <a href=\"http:\/\/passkeycentral.org\" target=\"_blank\" rel=\"noopener\">passkeycentral.org<\/a> for guidance to plan, implement and expand their passkey rollouts<\/li>\n\n\n\n<li>Implementing the <a href=\"https:\/\/www.passkeycentral.org\/design-guidelines\/\" target=\"_blank\" rel=\"noopener\">FIDO Design Guidelines<\/a>, data-driven UX best practices for passkey rollouts<\/li>\n\n\n\n<li>Getting their products <a href=\"https:\/\/fidoalliance.org\/certification\/\">FIDO Certified<\/a>, to demonstrate that their products are compliant, interoperable and secure<\/li>\n\n\n\n<li>Releasing case studies on their or their customers behalf, to share implementation journeys and business outcomes. Organizations can reach out to <a href=\"mailto:info@fidoalliance.org\">info@fidoalliance.org<\/a> to submit case studies directly to the FIDO Alliance.<\/li>\n\n\n\n<li>Taking part in the FIDO Alliance <a href=\"https:\/\/fidoalliance.org\/members\/become-a-member\/\">member activities<\/a> and working groups to further drive passkey optimization and adoption&nbsp;<\/li>\n\n\n\n<li>Planning and\/or taking steps to <a href=\"https:\/\/www.passkeycentral.org\/passkey-roll-out-guides\/prevent-phishing\/\" target=\"_blank\" rel=\"noopener\">remove passwords as a sign-in option<\/a>.<\/li>\n<\/ul>\n\n\n\n<p><strong>Take the Pledge Today<\/strong><br>Submit this form to sign the pledge. Signers of the pledge agree to have their company name (and not logo) included on marketing materials relating to the pledge. While we collect the names and emails of signatories, they will not be made public.&nbsp;<\/p>\n\n\n\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<h2 class=\"wp-block-heading has-emerald-color has-text-color has-link-color wp-elements-c69c0d2b7ad262cf7785a25f1a71de51\">\u7b7e\u7f72\u901a\u884c\u5bc6\u94a5\u627f\u8bfa\u5021\u8bae<\/h2>\n\n\n<div class=\"gb-container gb-container-1a4b3f8d gb-accordion\">\n<div class=\"gb-container gb-container-68be81ab gb-accordion__item\" data-transition=\"slide\">\n\n<button class=\"gb-button gb-button-4a7683d3 gb-accordion__toggle\" id=\"gb-accordion-toggle-4a7683d3\"><span class=\"gb-button-text\"><\/span><span class=\"gb-icon\"><svg xmlns=\"https:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 448 512\" width=\"1em\" height=\"1em\" ariahidden=\"true\" role=\"img\" class=\"gb-accordion__icon\"><path d=\"M207.029 381.476L12.686 187.132c-9.373-9.373-9.373-24.569 0-33.941l22.667-22.667c9.357-9.357 24.522-9.375 33.901-.04L224 284.505l154.745-154.021c9.379-9.335 24.544-9.317 33.901.04l22.667 22.667c9.373 9.373 9.373 24.569 0 33.941L240.971 381.476c-9.373 9.372-24.569 9.372-33.942 0z\" fill=\"currentColor\"><\/path><\/svg><svg xmlns=\"https:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 448 512\" width=\"1em\" height=\"1em\" ariahidden=\"true\" role=\"img\" class=\"gb-accordion__icon-open\"><path d=\"M240.971 130.524l194.343 194.343c9.373 9.373 9.373 24.569 0 33.941l-22.667 22.667c-9.357 9.357-24.522 9.375-33.901.04L224 227.495 69.255 381.516c-9.379 9.335-24.544 9.317-33.901-.04l-22.667-22.667c-9.373-9.373-9.373-24.569 0-33.941L207.03 130.525c9.372-9.373 24.568-9.373 33.941-.001z\" fill=\"currentColor\"><\/path><\/svg><\/span><\/button>\n\n\n<div id=\"gb-accordion-content-e8f81abf\" class=\"gb-accordion__content\"><div class=\"gb-container gb-container-e8f81abf\">\n\n<p>\u901a\u884c\u5bc6\u94a5\u627f\u8bfa\u5021\u8bae\u662f\u9762\u5411\u5728\u7ebf\u670d\u52a1\u63d0\u4f9b\u5546\u4ee5\u53ca\u8eab\u4efd\u9a8c\u8bc1\u4ea7\u54c1\u548c\u670d\u52a1\u4f9b\u5e94\u5546\u7684\u81ea\u613f\u6027\u627f\u8bfa\u5021\u8bae\u3002 \u4e2a\u4eba\u867d\u4e0d\u5728\u6b64\u627f\u8bfa\u5021\u8bae\u7684\u53c2\u4e0e\u8303\u56f4\u5185\uff0c\u4f46\u6211\u4eec\u9f13\u52b1\u4e2a\u4eba\u901a\u8fc7\u5176\u9996\u9009\u6e20\u9053\u53d1\u58f0\u652f\u6301\u901a\u884c\u5bc6\u94a5\u3002<\/p>\n\n\n\n<p>\u52a0\u5165\u6b64\u627f\u8bfa\u5021\u8bae\u8868\u793a\u670d\u52a1\u63d0\u4f9b\u5546\u548c\u4f9b\u5e94\u5546\u627f\u8bfa\u5c06\u5728\u4e00\u5e74\u5185\u4ee5\u6700\u5927\u8bda\u610f\u63a8\u8fdb\u5b9e\u73b0\u65e2\u5b9a\u76ee\u6807\u3002 \u5bf9\u4e8e\u5728\u5b9e\u73b0\u627f\u8bfa\u76ee\u6807\u8fc7\u7a0b\u4e2d\u53d6\u5f97\u663e\u8457\u6210\u679c\u7684\u516c\u53f8\uff0c\u5e94\u5728\u7b7e\u7f72\u6b64\u627f\u8bfa\u5021\u8bae\u4e00\u5e74\u5185\u516c\u5f00\u53d1\u6587\u8bb0\u5f55\u5176\u53d6\u5f97\u7684\u6210\u5c31\u3002 \u5bf9\u4e8e\u672a\u53d6\u5f97\u663e\u8457\u6210\u679c\u7684\u516c\u53f8\uff0c\u6211\u4eec\u4ecd\u9f13\u52b1\u5176\u5728\u7b7e\u7f72\u627f\u8bfa\u5021\u8bae\u4e00\u5e74\u5185\u5206\u4eab\u5176\u4ed8\u8bf8\u7684\u52aa\u529b\u3001\u9762\u4e34\u7684\u6311\u6218\u548c\u5e94\u5bf9\u65b9\u5f0f\uff0c\u4ee5\u4f9b\u4ed6\u4eba\u501f\u9274\u3002 \u6b64\u627f\u8bfa\u5021\u8bae\u662f\u81ea\u613f\u7b7e\u7f72\u7684\uff0c\u4e0d\u5177\u6709\u6cd5\u5f8b\u7ea6\u675f\u529b\u3002<\/p>\n\n\n\n<p>FIDO Alliance \u5bf9\u5df2\u652f\u6301\u91c7\u7528\u901a\u884c\u5bc6\u94a5\u767b\u5f55\u6216\u5c06\u901a\u884c\u5bc6\u94a5\u6280\u672f\u52a0\u5165\u5176\u4ea7\u54c1\u7684\u670d\u52a1\u63d0\u4f9b\u5546\u548c\u4f9b\u5e94\u5546\u8868\u793a\u8ba4\u53ef\u5e76\u81f4\u8c22\u3002 \u5df2\u652f\u6301\u901a\u884c\u5bc6\u94a5\u7684\u516c\u53f8\u5e94\u5c3d\u53ef\u80fd\u516c\u5f00\u5176\u5b9e\u73b0\u65b9\u6cd5\u548c\u53d6\u5f97\u7684\u6210\u679c\u3002<br>\u7b7e\u7f72\u901a\u884c\u5bc6\u94a5\u627f\u8bfa\u5021\u8bae<br>\u7b7e\u7f72\u6b64\u627f\u8bfa\u5021\u8bae\u7684\u516c\u53f8\u627f\u8bfa\u5c06\u5728\u4e00\u5e74\u5185\u4ee5\u6700\u5927\u8bda\u610f\u63a8\u8fdb\u5b9e\u73b0\u4ee5\u4e0b\u65e2\u5b9a\u76ee\u6807\uff1a<\/p>\n\n\n\n<p>\u5bf9\u4e8e\u73b0\u5df2\u5b9e\u73b0\u901a\u884c\u5bc6\u94a5\u767b\u5f55\u7684\u670d\u52a1\u63d0\u4f9b\u5546<br>\u5728\u7b7e\u7f72\u672c\u627f\u8bfa\u5021\u8bae\u4e00\u5e74\u5185\uff0c\u91c7\u53d6\u5177\u4f53\u884c\u52a8\u663e\u8457\u63d0\u5347\u7528\u6237\u767b\u5f55\u516c\u53f8\u670d\u52a1\u65f6\u4f7f\u7528\u901a\u884c\u5bc6\u94a5\u7684\u5360\u6bd4\u3002<\/p>\n\n\n\n<p>\u5bf9\u4e8e\u6b63\u5728\u5b9e\u73b0\u901a\u884c\u5bc6\u94a5\u767b\u5f55\u7684\u670d\u52a1\u63d0\u4f9b\u5546<br>\u5728\u7b7e\u7f72\u672c\u627f\u8bfa\u5021\u8bae\u4e00\u5e74\u5185\uff0c\u901a\u8fc7\u53ef\u91cf\u5316\u7684\u884c\u52a8\u5728\u516c\u53f8\u670d\u52a1\u4e2d\u5b9e\u73b0\u901a\u884c\u5bc6\u94a5\u767b\u5f55\u3002<\/p>\n\n\n\n<p>\u5bf9\u4e8e\u63d0\u4f9b\u57fa\u4e8e FIDO \u7684\u4ea7\u54c1\u548c\/\u6216\u670d\u52a1\u7684\u4f9b\u5e94\u5546<br>\u5728\u7b7e\u7f72\u672c\u627f\u8bfa\u5021\u8bae\u4e00\u5e74\u5185\uff0c\u91c7\u53d6\u5177\u4f53\u884c\u52a8\u5728\u516c\u53f8\u4ea7\u54c1\u548c\/\u6216\u670d\u52a1\u4e2d\u91c7\u7528\u901a\u884c\u5bc6\u94a5\uff0c\u4ee5\u663e\u8457\u63d0\u5347\u901a\u884c\u5bc6\u94a5\u7684\u4f7f\u7528\u7387\u3002<\/p>\n\n\n\n<p>\u5bf9\u4e8e\u6b63\u5728\u5f00\u53d1\u57fa\u4e8e FIDO \u7684\u4ea7\u54c1\u548c\/\u6216\u670d\u52a1\u7684\u4f9b\u5e94\u5546<br>\u5728\u7b7e\u7f72\u672c\u627f\u8bfa\u5021\u8bae\u4e00\u5e74\u5185\uff0c\u91c7\u53d6\u53ef\u91cf\u5316\u7684\u884c\u52a8\u5b8c\u6210 FIDO \u4ea7\u54c1\u8ba4\u8bc1\uff0c\u5e76\u63a8\u51fa\u652f\u6301\u901a\u884c\u5bc6\u94a5\u767b\u5f55\u7684\u4ea7\u54c1\u6216\u670d\u52a1\u3002<\/p>\n\n\n\n<p>\u5bf9\u4e8e\u884c\u4e1a\u534f\u4f1a\u548c\u6807\u51c6\u7ec4\u7ec7<br>\u5728\u7b7e\u7f72\u672c\u627f\u8bfa\u5021\u8bae\u4e00\u5e74\u5185\uff0c\u91c7\u53d6\u5177\u4f53\u884c\u52a8\u63d0\u5347\u901a\u884c\u5bc6\u94a5\u767b\u5f55\u7684\u53ef\u89c1\u6027\u548c\u4f18\u52bf\u3002<\/p>\n\n\n\n<p>\u7acb\u5373\u7b7e\u7f72\u901a\u884c\u5bc6\u94a5\u627f\u8bfa\u5021\u8bae<br>\u627f\u8bfa\u5021\u8bae\u7b7e\u7f72\u65b9\u540c\u610f\u5c06\u516c\u53f8\u540d\u79f0\uff08\u4e0d\u5305\u542b\u5fbd\u6807\uff09\u5217\u5165\u4e0e\u672c\u627f\u8bfa\u5021\u8bae\u76f8\u5173\u7684\u5ba3\u4f20\u6750\u6599\u4e2d\u3002 \u6211\u4eec\u6536\u96c6\u7b7e\u7f72\u65b9\u7684\u540d\u79f0\u4e0e\u7535\u5b50\u90ae\u4ef6\u5730\u5740\uff0c\u4f46\u4e0d\u4f1a\u5c06\u5176\u5bf9\u5916\u516c\u5f00\u3002&nbsp;<\/p>\n\n<\/div><\/div>\n<\/div>\n<\/div>\n\n<div class=\"gb-container gb-container-c436ce51\">\n\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why should my company consider joining the FIDO Alliance?<\/summary>\n<p>There are significant benefits to taking part in FIDO Alliance as a member, whether your company is a vendor looking to bring FIDO-based solutions to market, or if your organization is a service provider seeking to understand the most effective ways to deploy FIDO Authentication to your customers and\/or employees. You can learn more <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">here<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What\u2019s the process for joining the FIDO Alliance?<\/summary>\n<p>Please see the required steps on the FIDO Alliance membership <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">web page<\/a>.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does FIDO compare with PKI?<\/summary>\n<p>FIDO takes a \u201clightweight\u201d approach to asymmetric public-key cryptography, which offers service providers a way to extend the security benefits of public-key cryptography to a wider array of applications, domains, and devices \u2013 especially where traditional PKI has proven difficult or impossible. FIDO is not a replacement for PKI but rather complements it, enabling a greater number of users and applications to be protected using asymmetric encryption. This is especially important in situations where the alternative has been a username and password.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What devices and platforms have FIDO support?<\/summary>\n<p>The FIDO Alliance developed its FIDO2 specifications with the W3C to enable FIDO Authentication capabilities to be built into a wider array of devices, platforms, and web browsers. FIDO is currently supported in Google Chrome, Mozilla Firefox, Microsoft Edge, and Apple Safari (MacOS), iOS web browsers, as well as Windows 10 and Android platforms.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are some examples of FIDO being deployed in-market today?<\/summary>\n<p>Many leading organizations around the world have deployed FIDO Authentication to their employees and users, reducing their security risks and improving user experience. Check out our homepage under \u201cwho\u2019s using FIDO\u201d for a sample.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why did FIDO publish multiple specifications? What are the differences?<\/summary>\n<p>The FIDO Alliance has published three sets of specifications for simpler, stronger authentication \u2013 FIDO U2F, FIDO UAF and FIDO2 \u2013 in order to provide for the widest range of use cases and deployment scenarios:<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>When were the FIDO specifications published?<\/summary>\n<p>From its inception, the FIDO Alliance stated intentions to change the nature of authentication by developing specifications that define an open, scalable, interoperable set of mechanisms that supplant reliance on passwords to securely authenticate users of online services. Two years after its inception, the Alliance delivered the final 1.0 specifications on December 2014 to enable that vision. This was an important milestone on the industry\u2019s road to ubiquitous simpler, stronger authentication, and many deployments brought FIDO Authentication to users around the globe. To further add support for FIDO Authentication across devices and platforms, FIDO Alliance published its second set of specifications, FIDO2, in March 2019. See \u201cWhy did the FIDO Alliance see the need for FIDO2?\u201d for more information.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the FIDO specifications?<\/summary>\n<p>The FIDO Alliance has published three sets of specifications for simpler, stronger authentication: FIDO Universal Second Factor (FIDO U2F), FIDO Universal Authentication Framework (FIDO UAF) and the Client to Authenticator Protocols (CTAP). CTAP is complementary to the <a href=\"https:\/\/www.w3.org\/TR\/2018\/CR-webauthn-20180320\/\" target=\"_blank\" rel=\"noopener\">W3C\u2019s Web Authentication (WebAuthn) specification<\/a>; together, they are known as FIDO2.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What\u2019s the best way to follow FIDO\u2019s progress?<\/summary>\n<p>The <a href=\"https:\/\/fidoalliance.org\/\">FIDO Alliance website<\/a> provides comprehensive information about the Alliance, its <a href=\"https:\/\/fidoalliance.org\/specifications\/\">specifications<\/a>, <a href=\"https:\/\/fidoalliance.org\/certification\/fido-certified-products\/\">FIDO Certified products<\/a> and <a href=\"https:\/\/fidoalliance.org\/content\/fido-in-the-news\/\">general progress<\/a>. You can also <a href=\"https:\/\/fidoalliance.org\/newsletter-sign-up\/\">sign up<\/a> to receive updates and invitations to future events, many of which are open to the public. You can also follow <a href=\"https:\/\/twitter.com\/FIDOAlliance\" target=\"_blank\" rel=\"noopener\">@FIDOalliance<\/a> on Twitter and\/or on <a href=\"https:\/\/www.linkedin.com\/company\/the-fido-alliance\" target=\"_blank\" rel=\"noopener\">LinkedIn<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is the FIDO Alliance a non-profit organization? What is the scope?<\/summary>\n<p>The FIDO (Fast IDentity Online) Alliance is a 501(c)6 non-profit organization incorporated in mid-2012 to develop standards that address the lack of interoperability among strong authentication devices as well as the problems users face with creating and remembering multiple usernames and passwords. To learn more about the FIDO Alliance governance and structure, please refer to the <a href=\"https:\/\/fidoalliance.org\/overview\/\">About FIDO page<\/a> and the <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">Membership Details page.<\/a><\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Do the FIDO specifications enable anyone to begin using the specs to develop and offer FIDO certified products?<\/summary>\n<p>FIDO\u2019s specifications are public and available for anyone to read and analyze. But only FIDO Alliance Members benefit from \u201cthe promise\u201d to not assert patent rights against other members\u2019 implementations (see the <a href=\"https:\/\/fidoalliance.org\/wp-content\/uploads\/2019\/12\/FIDO-Alliance-Membership-Agreement.pdf\" target=\"_blank\" rel=\"noopener\">FIDO Alliance Membership Agreement<\/a> for details). Anyone may join the FIDO Alliance; we encourage even very small companies with a very low cost to join at the entry level. Members at all levels not only benefit from the mutual non-assert protection but also participate with FIDO Alliance members, activities, and developments; Associates have more limited participation benefits (https:\/\/fidoalliance.org\/members\/membership-benefits\/). All are invited to join the FIDO Alliance and participate.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is one FIDO token\/dongle\/device better than another? How can I choose which to buy?<\/summary>\n<p>FIDO specifications are device-agnostic and support a full range of authentication technologies, including FIDO Security Keys and biometrics such as fingerprint and iris scanners, voice and facial recognition, as well as PIN or pattern-protected microSD cards. FIDO specifications will also enable existing solutions and communications standards, such as Trusted Platform Module (TPM), USB Security Tokens, embedded Secure Elements (eSE), Smart Cards, Bluetooth Low Energy (BLE), and Near Field Communication (NFC). Because FIDO specifications are open, they are designed to be extensible and to accommodate future innovation, as well as protect existing investments.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Has FIDO made implementation rights available to anyone?<\/summary>\n<p>FIDO Alliance members have all committed to the promise contained within our Membership Agreement to not assert their patents against any other member implementation of FIDO 1.0 final specifications (referred to as \u201cProposed Standard\u201d in our <a href=\"https:\/\/fidoalliance.org\/wp-content\/uploads\/2019\/12\/FIDO-Alliance-Membership-Agreement.pdf\" target=\"_blank\" rel=\"noopener\">Membership Agreement<\/a>). Anyone interested in deploying a FIDO compliant solution can do so without joining the Alliance, and they are strongly encouraged to use FIDO Certified products to enable that deployment.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How can I be sure that the product I\u2019m buying conforms to FIDO standards?<\/summary>\n<p>The FIDO Alliance Certification Working Group is responsible for testing products for conformance to FIDO specifications and interoperability between those implementations. You can learn more about the FIDO\u00ae Certified program <a href=\"https:\/\/fidoalliance.org\/certification\/\">here<\/a>.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why are standards important?<\/summary>\n<p>Open industry standards assure that existing and future products and offerings are compatible and that anyone can evaluate the technology. Users can depend on their FIDO devices working wherever FIDO authentication is supported. Service providers and enterprises can accommodate various devices and <em>services<\/em> without having to make new investments or reverting to proprietary configurations.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can\u2019t someone break into an account if they steal a device?<\/summary>\n<p>No. In order to break into an account, the criminal would need not only the user\u2019s device that was registered as a FIDO Authenticator to the account but also the ability to defeat the user identification challenge used by the Authenticator to protect the private keys \u2013 such as a username and PIN or a biometric. This makes it extremely difficult to break into a FIDO-enabled account.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO approach to biometric authentication make a user safer? Could anyone steal my biometric information from a device or online service?<\/summary>\n<p>When used in FIDO Authentication, user biometric data never leaves the device and is never stored on a central server where it could be stolen in a breach. FIDO\u2019s on-device model for authentication eliminates the risk of a remote attack. If a would-be attacker had access to the user\u2019s actual device, a successful spoof would be quite difficult. First, the attacker must obtain a perfectly formed, complete latent print that is also enrolled on the target user\u2019s device. Then, the attacker must gain access to the user\u2019s device in order to control only that one device. The single spoof, even if accomplished, doesn\u2019t approach the potential harm done by today\u2019s typical mass-scale attack, which can result in harvesting millions and hundreds of millions of users\u2019 credentials.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does FIDO Authentication make users safer on the web?<\/summary>\n<p>Unlike current password-based authentication models that have proven vulnerable to mass-scale attacks and fraud, FIDO authentication credentials are never shared or stored in centralized databases. FIDO credentials are known and maintained only by the user\u2019s own device. All that is ever stored by the service provider are the public keys paired to the user\u2019s device where the private keys are stored. For additional security and privacy, biometrics used in FIDO Authentication never leave the device. This security model eliminates the risks of phishing, all forms of password theft and replay attacks. A would-be attacker would need the user\u2019s physical device to even attempt a hack (see below, \u201ccan\u2019t someone break into an account if they steal a device?\u201d for more information). The password ecosystem has afforded attackers with great return on investment with relatively limited risk; the FIDO ecosystem is far more difficult, expensive and risky for attackers to profit from.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do you protect against root kits and malware attacks on the embedded fingerprint sensor?<\/summary>\n<p>The FIDO Alliance recently launched the Authenticator Certification Program. This program introduces Authenticator Security Requirements to the FIDO Certification Program specifically for authenticators. Each authenticator that is certified under the FIDO Certification program is validated to meet specific security assurance levels depending on the level of security the vendor is seeking. The higher the level, the greater the security assurance. More information about this program can be found here: <a href=\"https:\/\/fidoalliance.org\/certification\/authenticator-certification-levels\/\">https:\/\/fidoalliance.org\/certification\/authenticator-certification-levels\/<\/a>.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>If I use the same device with multiple websites, can one site know that I use it with another site?<\/summary>\n<p>No, this type of information exchange is prevented with FIDO Authentication. Each device\/website pairing requires separate registration and a separate cryptographic key pair. Once registered, a user can easily authenticate to multiple sites from the same device, yet each site has no knowledge of the user interactions with other sites. FIDO does not introduce any new tracking mechanism that could be used to correlate user activity online.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Does FIDO get any of my personal information?<\/summary>\n<p>No. FIDO Alliance only specifies standards for strong authentication and tests implementations for compliance to those standards; the Alliance does not provide services or equip devices or sites. Device manufacturers, online service providers, enterprises, and developers use the FIDO specifications to build products, provide services, and enable sites and browsers with FIDO authentication. Under FIDO specifications, the user\u2019s credentials must remain on the user\u2019s device, and they are never shared with a provider or service.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How can companies get involved in the FIDO Alliance\u2019s new work areas?<\/summary>\n<p>The IDWG and IoT TWG are now open to industry participants. Participation in FIDO Alliance working groups is open to all board and sponsor level members of the FIDO Alliance. For more information on joining the Alliance, visit <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">https:\/\/fidoalliance.org\/members\/membership-benefits<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What will the IoT Technical Working Group do?<\/summary>\n<p>The IoT TWG will provide a comprehensive authentication framework for IoT devices in keeping with the fundamental mission of the Alliance \u2013 passwordless authentication. The IoT TWG will develop use cases, target architectures and specifications covering: IoT device attestation\/authentication profiles to enable interoperability between service providers and IoT devices; automated onboarding, and binding of applications and\/or users to IoT devices; and IoT device authentication and provisioning via smart routers and IoT hubs.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What will the Identity Verification and Binding Working Group do?<\/summary>\n<p>The FIDO Alliance has identified newer remote, possession-based techniques including biometric \u201cselfie\u201d matching and government-issued identity document authentication as having the potential to greatly improve the quality of identity assurance for new account onboarding and account recovery. The IDWG will define criteria for this type of remote identity verification, as well as others, and develop a certification program and educational materials to support the adoption of that criteria.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How will the Alliance fulfill these new standards and certification initiatives?<\/summary>\n<p>The Alliance has formed two new working groups: the Identity Verification and Binding Working Group (IDWG) and the IoT Technical Working Group (IoT TWG) to establish guidelines and certification criteria in these areas. The FIDO Alliance will continue to focus on development and adoption of its user authentication standards and related programs and use them as a foundation for this expanded work, with contributions from current members and new industry participants.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do these new areas related to user authentication?<\/summary>\n<p>Identity verification and IoT security are both adjacent to the FIDO Alliance core focus on user authentication. For accounts protected by FIDO Authentication, identity verification for the account recovery process when a FIDO device is lost or stolen becomes critical to maintaining the integrity of the user\u2019s account. With IoT devices, typical industry practices is to ship them with default password credentials and manual onboarding, which leaves them open to attack. The security gaps in both of these areas can most effectively addressed through industry collaboration and standardization rather than siloed, proprietary approaches.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the FIDO Alliance trying to achieve with these new initiatives?<\/summary>\n<p>Ultimately, the Alliance is striving to increase the efficacy and market adoption of FIDO Authentication by addressing adjacent technology areas that leave security vulnerabilities on the web. There is a gap between the high assurance provided by FIDO Authentication standards and the lower assurance methods used in identity verification for account recovery and IoT authentication. The Alliance aims to strengthen identity verification assurance to support better account recovery and automate secure device onboarding to remove password use from IoT.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the FIDO Alliance new work areas?<\/summary>\n<p>The Alliance announced new work areas to develop standards and certification programs in identity verification and the Internet of Things (IoT).<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is next for the FIDO Alliance and FIDO standards?<\/summary>\n<p>FIDO Alliance\u2019s work is just beginning. The specifications and certification programs are continuing to evolve, and our deployment work is taking on even greater importance. Additionally, the Alliance has just launched new work areas in IoT and identity verification, which leverage the Alliance\u2019s broad coalition of leading organizations from around the world to help standardize technologies adjacent to user authentication. For more information on these work areas, read <a href=\"https:\/\/fidoalliance.org\/fido-alliance-announces-id-and-iot-initiatives\/\">https:\/\/fidoalliance.org\/fido-alliance-announces-id-and-iot-initiatives\/<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO Alliance ensure interoperability with FIDO2?<\/summary>\n<p>FIDO Alliance provides <a href=\"https:\/\/fidoalliance.org\/certification\/interoperability-testing\/\">interoperability testing<\/a> and <a href=\"https:\/\/fidoalliance.org\/certification\/functional-certification\/\">certification<\/a> for servers, clients, and authenticators adhering to FIDO2 specifications. Additionally, the Alliance has introduced a new Universal Server certification for servers that interoperate with all FIDO Authenticator types (UAF, U2F, CTAP). As a best practice, the FIDO Alliance recommends online services and enterprises deploy a Universal Server to ensure support for all FIDO Certified Authenticators.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Does FIDO2 mean that FIDO U2F is dead?<\/summary>\n<p>Not at all. FIDO U2F capabilities have merged into FIDO2\u2019s CTAP2 protocol, and FIDO U2F security keys will continue to work with services that support U2F authentication as well as those that have support FIDO2 authentication.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Does FIDO2 replace the FIDO U2F and FIDO UAF specifications?<\/summary>\n<p>The specifications under FIDO2 support existing passwordless FIDO UAF and FIDO U2F use cases and specifications and expand the availability of FIDO Authentication. Users that already have external FIDO-compliant devices, such as FIDO U2F security keys, will be able to continue to use these devices with web applications that support WebAuthn. Existing FIDO UAF devices can still be used with pre-existing services as well as new service offerings based on the FIDO UAF protocols.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the status of FIDO2 browser and platform implementation?<\/summary>\n<p>Current adoption status is available <a href=\"https:\/\/fidoalliance.org\/fido2\/fido2-web-authentication-webauthn\/\">here<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the status of FIDO2 specifications development?<\/summary>\n<p>FIDO2 standards are published and available for implementation today. WebAuthn reached W3C\u2019s final Recommendation status in March 2019 and is an official web standard. CTAP is a final FIDO Alliance specification.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why did FIDO Alliance submit specifications to the W3C?<\/summary>\n<p>FIDO Alliance partnered with W3C to standardize FIDO Authentication for the entire web platform so the FIDO ecosystem could grow by an entire community of web browsers and web application servers supporting the standard. W3C is where the web community produces their standards, so it was more practical to work in that forum.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the relationship between FIDO2 and W3C\u2019s WebAuthn?<\/summary>\n<p>A good rule of thumb is to remember this simple equation:<\/p>\n  <p>FIDO2 = W3C WebAuthn + CTAP<\/p>\n  <p>This is the full story of FIDO2\u2019s development:<\/p>\n  <p>After the release of the FIDO UAF and FIDO U2F specifications, FIDO Alliance focused on making FIDO Authentication more accessible to users worldwide. The Alliance developed three technical specifications that defined one web-based API, enabling FIDO Authentication to be built directly into browsers and platforms. These specifications were submitted to the W3C, the international standards organization for the World Wide Web, in November of 2015. FIDO Alliance member companies worked within the W3C\u2019s Web Authentication Working Group to finalize the API, which became known as WebAuthn. WebAuthn was officially recognized as a W3C web standard in March 2019.<\/p>\n  <p>In the same time period, the FIDO Alliance created and finalized a complementary specification to WebAuthn: the Client to Authenticator Protocol (CTAP). CTAP makes WebAuthn even more accessible to users by allowing them to use the devices they already own, such as their mobile phone, security key or Windows 10 PC to authenticate to WebAuthn-enabled browsers and platforms.<\/p>\n  <p>Together, WebAuthn and CTAP are called FIDO2. The FIDO Alliance manages and maintains the certification program to ensure interoperability of all the FIDO2 implementations in the market \u2013 clients, servers and authentication devices.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why did the FIDO Alliance see the need for FIDO2?<\/summary>\n<p>The FIDO Alliance goal has always been ubiquitous strong authentication across the web. That means building support for FIDO Authentication into every device that people use every day. The Alliance made notable progress with its initial FIDO U2F and FIDO UAF specifications, especially on mobile platforms. FIDO2 expands the reach of FIDO Authentication by making it a built-in feature across browsers and web platforms, which is a significant step toward the Alliance\u2019s overall goal.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is it \u201cFIDO2\u201d or \u201cFIDO 2.0\u201d?<\/summary>\n<p>FIDO2 is the official name for the complete set of FIDO\u2019s latest standards.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What specifications are included in FIDO2?<\/summary>\n<p>FIDO2 includes two specifications:<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is FIDO2?<\/summary>\n<p>FIDO2 is the overarching term for FIDO Alliance\u2019s newest set of strong authentication standards. FIDO2 includes two specifications: W3C\u2019s Web Authentication (WebAuthn) and FIDO Alliance\u2019s Client to Authenticator Protocol (CTAP).<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can I use the same FIDO device with multiple websites? Can I use multiple FIDO devices with the same website?<\/summary>\n<p>Yes, you can use multiple websites from one FIDO device. Each device\/website pairing requires a separate registration and a separate cryptographic key pair. Once registered, a user can easily authenticate to multiple sites from the same device, yet each site has no knowledge of the user interactions with other sites.<\/p>\n  <p>If a user acquires a new device or wants to use multiple FIDO devices, the user needs only register each of the devices at the sites where he wants to use them. Once a device is registered at a site, it will be recognized whenever the user needs to authenticate at that site. When a user visits a site with a new device that hasn\u2019t been registered, and thus isn\u2019t automatically recognized, the user will be prompted to register the new FIDO device to enable FIDO authentication with the new device at that site.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Will FIDO devices work when I don\u2019t have Internet connectivity?<\/summary>\n<p>The purpose of the FIDO model is to provide a secure and simple authentication experience for online services. The authentication involves a user with a device connecting to a service over a network.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the Certificate number format of the FIDO Alliance issued Certificates?<\/summary>\n<p>The FIDO Alliance Certificate number format is: AA-NNNNN-SSSSS, where AA is the Program Identifier, NNNNN is the Certification number, and SSSSS is the Product Identifier. The Program Identifier corresponds to the certification program under which the Certificate was issued.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the audit process for products in the market?<\/summary>\n<p>The FIDO Alliance staff will audit on a monthly basis the usage of FIDO Certified logos and published claims of certification. Auditing of actual implementations will be driven by market feedback. Should any concerns arise, feedback can be submitted through the <a href=\"https:\/\/fidoalliance.org\/certified-logo-violation\/\">Certified Logo Violation <\/a>form.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Must I certify a product in order to market it?<\/summary>\n<p>No. But a product must be certified to claim to be FIDO Certified and use the FIDO Certified logo.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO Alliance certify derivative products?<\/summary>\n<p>Derivative certification was created to streamline the certification process for implementers that have a large volume of certifications that are essentially all based on the same implementation. In this case, implementers may certify one implementation and the rest may be registered as \u201cderivatives\u201d of that base certification. Derivatives don\u2019t require attending interoperability events to achieve certification, but they do require that the derivative implementation run and pass conformance testing. The implementation cannot change in any substantial way from the original certification earned via our test tools and interoperability testing. If there are changes to the implementation, then it will need to go through the FIDO Impact Analysis to determine if the implementation requires a Delta Certification or Recertification.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How often do testing events occur?<\/summary>\n<p>Interoperability events occur at least every 90 days, but may occur more frequently based on implementer demand.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the costs associated with certification?<\/summary>\n<p>Fees are per implementation certified and must be paid before a Certificate will be issued.<\/p>\n    <p>For an overview of the FIDO Certification Fees per program, please go to the <a href=\"https:\/\/fidoalliance.org\/certification\/certification-fees\/\" target=\"_blank\" rel=\"noopener\">Certification Fees<\/a> page.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can I become FIDO Certified if I am not a FIDO Alliance Member?<\/summary>\n<p>Yes. Non-members are welcome to certify their implementations.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is a Vendor ID and who needs one?<\/summary>\n<p>The UAF authenticator specification defines an AAID field that is half Vendor ID and half Device ID used to uniquely identify each authenticator. The Vendor ID is a unique identifier assigned by FIDO to each company implementing a UAF authenticator. The other half of the AAID field, the Device ID, is assigned to the authenticator by the implementing company. Only UAF Authenticators require a Vendor ID.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How long is a product certified, and is recertification required when protocols change?<\/summary>\n<p>A product is certified indefinitely as long as the code base of its FIDO implementation doesn\u2019t change in any substantial way. Certification can only be terminated in rare instances, such as determining that an implementation improperly passed test tools or interoperability events. Certification only applies to a specific specification and implementation class (i.e. \u201cUAF Authenticator\u201d). If new major versions of specifications are released (as determined by the FIDO Certification Working Group) and an implementation would like to claim conformance with that specification, new certification will be required.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is there a Trademark License Agreement (TMLA) requirement for logo use?<\/summary>\n<p>Use of the FIDO Certified logo will require signing a TMLA. There is a streamlined process for Relying Parties that wish to use the certification logo on their websites, which includes a <a href=\"https:\/\/fidoalliance.org\/overview\/legal\/fido-trademark-and-service-mark-usage-agreement-for-websites\/\">\u201cclickless\u201d license agreement.<\/a><\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Will there be a FIDO Certified logo?<\/summary>\n<p>Yes. There is a recognizable FIDO Certified logo for vendors to include with their websites, product materials, packaging, etc.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do I get started?<\/summary>\n<p>Start by making sure your implementation passes the <a href=\"https:\/\/fidoalliance.org\/certification\/functional-certification\/conformance\/\">conformance tests<\/a> (registration required). After you\u2019ve validated your implementation, <a href=\"https:\/\/fidoalliance.org\/certification\/interoperability-testing\/interop-registration\/\">register<\/a> for an Interoperability event and you\u2019re on your way to certifying your product.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the FIDO Alliance Metadata Service?<\/summary>\n<p>The FIDO Alliance Metadata Service (MDS) is a web-based tool where FIDO authenticator vendors can publish metadata statements for FIDO servers to download. This provides organizations deploying FIDO servers with a centralized and trusted source of information about FIDO authenticators.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What kinds of companies should get involved?<\/summary>\n<p>Vendor companies looking to bring FIDO-based solutions to market and\/or organization service providers seeking to understand the most effective ways to deploy FIDO Authentication will benefit the most from participating in FIDO Alliance working groups.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do companies benefit from joining the working groups?<\/summary>\n<p>By taking part in FIDO Alliance\u2019s technical working groups, members have the ability to shape and have early visibility into FIDO\u2019s technical output \u2013 which can help accelerate product and service development. Participating in the working groups will also enable your team to get peer-based feedback to aid with your own implementations, while also creating an opportunity to have your company\u2019s vision reflected in deployment guidelines and recommendations.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can you describe the functional testing process?<\/summary>\n<p>There are four major testing steps:<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How is the testing done?<\/summary>\n<p>Certification starts with self-assessment of specification conformance through the use of FIDO Alliance provided test tools, followed by interoperability testing with at least three test partners at FIDO Alliance-proctored test events. At this time, there is no lab aspect to the certification program, but the Certification Working Group is currently reviewing requirements to develop and implement a Functional Lab Accreditation program. See the <a href=\"https:\/\/fidoalliance.org\/certification\/getting-started\/\">Getting Started<\/a> web page to learn more.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Are there separate submission fees for testing against each of the FIDO Alliance specifications?<\/summary>\n<p>Yes. Implementations must request certification (and pay the certification fees) for each implementation class they are seeking to certify. For example, if an implementation certifies for both a FIDO UAF Server and a FIDO2 Server, that implementation must follow the certification process for both (and pay the certification fees for both). The implementation would ultimately receive two certifications. The primary difference between testing for different specifications is they have different test tools and the different interoperability events.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Our company just built a new product but we haven\u2019t gotten it certified yet. Can we say that it is FIDO Certified while we are working on achieving our certification?<\/summary>\n<p>No. Only products that have passed through FIDO Certification program and have been granted a certification number can claim to be FIDO Certified.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the Certificate number format of the FIDO Alliance issued Certificates?<\/summary>\n<p>The FIDO Alliance issued Certificates have the following numerical format:<\/p>\n    <p>SSSXYZAYYYYMMDD####<\/p>\n    <p>SSS \u2013 Specification number (UAF or U2F)<\/p>\n    <p>X \u2013 Specification number<\/p>\n    <p>Y \u2013 Specification minor number<\/p>\n    <p>Z \u2013 Specification revision number<\/p>\n    <p>A \u2013 Specification errata number<\/p>\n    <p>YYYY \u2013 Year issued<\/p>\n    <p>MM \u2013 Month issued<\/p>\n    <p>DD \u2013 Day issued<\/p>\n    <p>#### \u2013 The number of the certificate issued today<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the audit process for products in the market?<\/summary>\n<p>The FIDO Alliance staff will audit on a monthly basis the usage of FIDO Certified logos and published claims of certification. Auditing of actual implementations will be driven by market feedback. Should any concerns arise, feedback can be submitted through the <a href=\"https:\/\/fidoalliance.org\/certified-logo-violation\/\">Certified Logo Violation <\/a>form.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Must I certify a product in order to market it?<\/summary>\n<p>No. But a product must be certified to claim to be FIDO Certified and use the FIDO Certified logo.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO Alliance certify derivative products?<\/summary>\n<p>Derivative certification was created to streamline the certification process for implementers that have a large volume of certifications that are essentially all based on the same implementation. In this case, implementers may certify one implementation and the rest may be registered as \u201cderivatives\u201d of that base certification. Derivatives don\u2019t require attending interoperability events to achieve certification, but they do require that the derivative implementation run and pass conformance testing. The implementation cannot change in any substantial way from the original certification earned via our test tools and interoperability testing. If there are changes to the implementation, then it will need to go through the FIDO Impact Analysis to determine if the implementation requires a Delta Certification or Recertification.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How often do testing events occur?<\/summary>\n<p>Interoperability events occur at least every 90 days, but may occur more frequently based on implementer demand.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the costs associated with certification?<\/summary>\n<p>Fees are per implementation certified and must be paid before a Certificate will be issued.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can I become FIDO Certified if I am not a FIDO Alliance Member?<\/summary>\n<p>Yes. Non-members are welcome to certify their implementations.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is a Vendor ID and who needs one?<\/summary>\n<p>The UAF authenticator specification defines an AAID field that is half Vendor ID and half Device ID used to uniquely identify each authenticator. The Vendor ID is a unique identifier assigned by FIDO to each company implementing a UAF authenticator. The other half of the AAID field, the Device ID, is assigned to the authenticator by the implementing company. Only UAF Authenticators require a Vendor ID.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How long is a product certified, and is recertification required when protocols change?<\/summary>\n<p>A product is certified indefinitely as long as the code base of its FIDO implementation doesn\u2019t change in any substantial way. Certification can only be terminated in rare instances, such as determining that an implementation improperly passed test tools or interoperability events. Certification only applies to a specific specification and implementation class (i.e. \u201cUAF Authenticator\u201d). If new major versions of specifications are released (as determined by the FIDO Certification Working Group) and an implementation would like to claim conformance with that specification, new certification will be required.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is there a Trademark License Agreement (TMLA) requirement for logo use?<\/summary>\n<p>Use of the FIDO Certified logo will require signing a TMLA. There is a streamlined process for Relying Parties that wish to use the certification logo on their websites, which includes a <a href=\"https:\/\/fidoalliance.org\/overview\/legal\/fido-trademark-and-service-mark-usage-agreement-for-websites\/\">\u201cclickless\u201d license agreement.<\/a><\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Will there be a FIDO Certified logo?<\/summary>\n<p>Yes. There is a recognizable FIDO Certified logo for vendors to include with their websites, product materials, packaging, etc.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do I get started?<\/summary>\n<p>Start by making sure your implementation passes the <a href=\"https:\/\/fidoalliance.org\/certification\/functional-certification\/conformance\/\">conformance tests<\/a> (registration required). After you\u2019ve validated your implementation, <a href=\"https:\/\/fidoalliance.org\/certification\/interoperability-testing\/interop-registration\/\">register<\/a> for an Interoperability event and you\u2019re on your way to certifying your product.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the FIDO Alliance Metadata Service?<\/summary>\n<p>The FIDO Alliance Metadata Service (MDS) is a web-based tool where FIDO authenticator vendors can publish metadata statements for FIDO servers to download. This provides organizations deploying FIDO servers with a centralized and trusted source of information about FIDO authenticators.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What kinds of companies should get involved?<\/summary>\n<p>Vendor companies looking to bring FIDO-based solutions to market and\/or organization service providers seeking to understand the most effective ways to deploy FIDO Authentication will benefit the most from participating in FIDO Alliance working groups.<\/p>\n<\/details>\n<\/div>\n\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<h2 class=\"wp-block-heading has-emerald-color has-text-color has-link-color wp-elements-127055abf7807b447636962905f59201\">\u30d1\u30b9\u30ad\u30fc\u5ba3\u8a00<\/h2>\n\n\n<div class=\"gb-container gb-container-b39f4add gb-accordion\">\n<div class=\"gb-container gb-container-c775a108 gb-accordion__item\" data-transition=\"slide\">\n\n<button class=\"gb-button gb-button-3fcfe4ea gb-accordion__toggle\" id=\"gb-accordion-toggle-3fcfe4ea\"><span class=\"gb-button-text\"><\/span><span class=\"gb-icon\"><svg xmlns=\"https:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 448 512\" width=\"1em\" height=\"1em\" ariahidden=\"true\" role=\"img\" class=\"gb-accordion__icon\"><path d=\"M207.029 381.476L12.686 187.132c-9.373-9.373-9.373-24.569 0-33.941l22.667-22.667c9.357-9.357 24.522-9.375 33.901-.04L224 284.505l154.745-154.021c9.379-9.335 24.544-9.317 33.901.04l22.667 22.667c9.373 9.373 9.373 24.569 0 33.941L240.971 381.476c-9.373 9.372-24.569 9.372-33.942 0z\" fill=\"currentColor\"><\/path><\/svg><svg xmlns=\"https:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 448 512\" width=\"1em\" height=\"1em\" ariahidden=\"true\" role=\"img\" class=\"gb-accordion__icon-open\"><path d=\"M240.971 130.524l194.343 194.343c9.373 9.373 9.373 24.569 0 33.941l-22.667 22.667c-9.357 9.357-24.522 9.375-33.901.04L224 227.495 69.255 381.516c-9.379 9.335-24.544 9.317-33.901-.04l-22.667-22.667c-9.373-9.373-9.373-24.569 0-33.941L207.03 130.525c9.372-9.373 24.568-9.373 33.941-.001z\" fill=\"currentColor\"><\/path><\/svg><\/span><\/button>\n\n\n<div id=\"gb-accordion-content-9d450da3\" class=\"gb-accordion__content\"><div class=\"gb-container gb-container-9d450da3\">\n\n<p>\u30d1\u30b9\u30ad\u30fc\u5ba3\u8a00\u3068\u306f\u3001\u30aa\u30f3\u30e9\u30a4\u30f3\u30b5\u30fc\u30d3\u30b9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u304a\u3088\u3073\u8a8d\u8a3c\u306b\u95a2\u3059\u308b\u88fd\u54c1\u30fb\u30b5\u30fc\u30d3\u30b9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u30fb\u30d9\u30f3\u30c0\u30fc\u3092\u5bfe\u8c61\u3068\u3059\u308b\u81ea\u4e3b\u7684\u306a\u5ba3\u8a00\u3067\u3059\u3002 \u500b\u4eba\u306f\u672c\u5ba3\u8a00\u306e\u5bfe\u8c61\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u304c\u3001\u304a\u597d\u307f\u306e\u30c1\u30e3\u30cd\u30eb\u3092\u901a\u3058\u3066\u30d1\u30b9\u30ad\u30fc\u306b\u5bfe\u3059\u308b\u30b5\u30dd\u30fc\u30c8\u3092\u8868\u660e\u3059\u308b\u3053\u3068\u304c\u63a8\u5968\u3055\u308c\u3066\u3044\u307e\u3059\u3002&nbsp;<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306b\u53c2\u52a0\u3059\u308b\u3053\u3068\u3067\u3001\u30b5\u30fc\u30d3\u30b9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u3068\u30d9\u30f3\u30c0\u30fc\u306f\u63b2\u3052\u3089\u308c\u305f\u76ee\u6a19\u306b\u5411\u304b\u3063\u30661\u5e74\u9593\u3001\u8aa0\u5fc3\u8aa0\u610f\u53d6\u308a\u7d44\u3080\u3053\u3068\u3092\u7d04\u675f\u3057\u307e\u3059\u3002 \u7d04\u675f\u3057\u305f\u76ee\u6a19\u306b\u5bfe\u3057\u3066\u76ee\u306b\u898b\u3048\u308b\u5177\u4f53\u7684\u306a\u9032\u6357\u3092\u9054\u6210\u3057\u305f\u4f01\u696d\u306f\u3001\u5ba3\u8a00\u306b\u7f72\u540d\u3057\u3066\u304b\u30891\u5e74\u4ee5\u5185\u306b\u305d\u306e\u6210\u679c\u3092\u516c\u8868\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 \u5177\u4f53\u7684\u306a\u9032\u6357\u304c\u5f97\u3089\u308c\u306a\u304b\u3063\u305f\u4f01\u696d\u3082\u3001\u540c\u671f\u9593\u5185\u306b\u5b9f\u65bd\u3057\u305f\u53d6\u308a\u7d44\u307f\u3084\u8ab2\u984c\u3001\u30a2\u30d7\u30ed\u30fc\u30c1\u3092\u5171\u6709\u3059\u308b\u3053\u3068\u304c\u5968\u52b1\u3055\u308c\u3066\u3044\u307e\u3059\u3002\u3053\u308c\u306b\u3088\u308a\u3001\u4ed6\u306e\u4f01\u696d\u304c\u5b66\u3076\u6a5f\u4f1a\u3092\u5f97\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 \u672c\u5ba3\u8a00\u306f\u3042\u304f\u307e\u3067\u3082\u81ea\u4e3b\u7684\u306a\u3082\u306e\u3067\u3042\u308a\u3001\u6cd5\u7684\u62d8\u675f\u529b\u3092\u6709\u3059\u308b\u3082\u306e\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u3002<\/p>\n\n\n\n<p>FIDO\u30a2\u30e9\u30a4\u30a2\u30f3\u30b9\u306f\u3001\u30b5\u30a4\u30f3\u30a4\u30f3\u6a5f\u80fd\u307e\u305f\u306f\u81ea\u793e\u88fd\u54c1\u306b\u5bfe\u3057\u3066\u65e2\u306b\u30d1\u30b9\u30ad\u30fc\u3092\u5c0e\u5165\u3057\u3066\u3044\u308b\u30b5\u30fc\u30d3\u30b9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u3068\u30d9\u30f3\u30c0\u30fc\u3092\u8a55\u4fa1\u3057\u3066\u304a\u308a\u3001\u611f\u8b1d\u306e\u610f\u3092\u8868\u3057\u305f\u3044\u3068\u601d\u3044\u307e\u3059\u3002 \u65e2\u306b\u30d1\u30b9\u30ad\u30fc\u306b\u5bfe\u5fdc\u3057\u3066\u3044\u308b\u4f01\u696d\u306f\u3001\u53ef\u80fd\u3067\u3042\u308c\u3070\u3001\u305d\u306e\u5b9f\u88c5\u624b\u6bb5\u3084\u5f71\u97ff\u306e\u7d50\u679c\u306b\u3064\u3044\u3066\u516c\u958b\u3057\u3066\u3044\u305f\u3060\u3051\u307e\u3059\u3068\u5e78\u3044\u3067\u3059\u3002<\/p>\n\n\n\n<p>\u30d1\u30b9\u30ad\u30fc\u5ba3\u8a00\u306b\u53c2\u52a0\u3059\u308b<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306b\u53c2\u52a0\u3059\u308b\u4f01\u696d\u306f\u3001\u4ee5\u4e0b\u306b\u63b2\u3052\u308b\u76ee\u6a19\u306b\u5411\u3051\u30661\u5e74\u9593\u3001\u8aa0\u5fc3\u8aa0\u610f\u53d6\u308a\u7d44\u3080\u3053\u3068\u3092\u7d04\u675f\u3059\u308b\u3082\u306e\u3068\u3057\u307e\u3059\u3002<\/p>\n\n\n\n<p>\u5bfe\u8c61\uff1a\u65e2\u306b\u30b5\u30a4\u30f3\u30a4\u30f3\u306b\u30d1\u30b9\u30ad\u30fc\u3092\u5b9f\u88c5\u3057\u3066\u3044\u308b\u30b5\u30fc\u30d3\u30b9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306b\u7f72\u540d\u3057\u3066\u304b\u30891\u5e74\u4ee5\u5185\u306b\u3001\u30e6\u30fc\u30b6\u30fc\u304c\u81ea\u793e\u30b5\u30fc\u30d3\u30b9\u306b\u30b5\u30a4\u30f3\u30a4\u30f3\u3059\u308b\u969b\u306e\u30d1\u30b9\u30ad\u30fc\u5229\u7528\u7387\u3092\u5177\u4f53\u7684\u306b\u5411\u4e0a\u3055\u305b\u308b\u305f\u3081\u306b\u5b9f\u65bd\u3057\u305f\u884c\u52d5\u3092\u793a\u3059\u3002<\/p>\n\n\n\n<p>\u5bfe\u8c61\uff1a\u30b5\u30a4\u30f3\u30a4\u30f3\u306b\u30d1\u30b9\u30ad\u30fc\u306e\u5b9f\u88c5\u3092\u8a66\u307f\u3066\u3044\u308b\u30b5\u30fc\u30d3\u30b9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306b\u7f72\u540d\u3057\u3066\u304b\u30891\u5e74\u4ee5\u5185\u306b\u3001\u81ea\u793e\u30b5\u30fc\u30d3\u30b9\u306e\u30b5\u30a4\u30f3\u30a4\u30f3\u306b\u30d1\u30b9\u30ad\u30fc\u3092\u5c0e\u5165\u3059\u308b\u305f\u3081\u306b\u5b9f\u65bd\u3057\u305f\u6e2c\u5b9a\u53ef\u80fd\u306a\u884c\u52d5\u3092\u793a\u3059\u3002<\/p>\n\n\n\n<p>\u5bfe\u8c61\uff1aFIDO\u30d9\u30fc\u30b9\u306e\u88fd\u54c1\u3084\u30b5\u30fc\u30d3\u30b9\u3092\u63d0\u4f9b\u3059\u308b\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306b\u7f72\u540d\u3057\u3066\u304b\u30891\u5e74\u4ee5\u5185\u306b\u3001\u81ea\u793e\u306e\u88fd\u54c1\u3084\u30b5\u30fc\u30d3\u30b9\u3067\u306e\u30d1\u30b9\u30ad\u30fc\u306e\u63a1\u7528\u3092\u901a\u3058\u3066\u30d1\u30b9\u30ad\u30fc\u5229\u7528\u7387\u3092\u5177\u4f53\u7684\u306b\u62e1\u5927\u3055\u305b\u308b\u305f\u3081\u306b\u5b9f\u65bd\u3057\u305f\u884c\u52d5\u3092\u793a\u3059\u3002<\/p>\n\n\n\n<p>\u5bfe\u8c61\uff1aFIDO\u30d9\u30fc\u30b9\u306e\u88fd\u54c1\u3084\u30b5\u30fc\u30d3\u30b9\u3092\u958b\u767a\u3059\u308b\u30d9\u30f3\u30c0\u30fc<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306b\u7f72\u540d\u3057\u3066\u304b\u30891\u5e74\u4ee5\u5185\u306b\u3001\u81ea\u793e\u88fd\u54c1\u3092FIDO\u8a8d\u8a3c\uff08\u30d1\u30b9\u30ad\u30fc\u8a8d\u8a3c\uff09\u306b\u5bfe\u5fdc\u3057\u3001\u30d1\u30b9\u30ad\u30fc\u3067\u306e\u30b5\u30a4\u30f3\u30a4\u30f3\u306b\u5bfe\u5fdc\u3057\u305f\u5099\u3048\u305f\u88fd\u54c1\u307e\u305f\u306f\u30b5\u30fc\u30d3\u30b9\u3092\u958b\u59cb\u3059\u308b\u305f\u3081\u306b\u5b9f\u65bd\u3057\u305f\u6e2c\u5b9a\u53ef\u80fd\u306a\u884c\u52d5\u3092\u793a\u3059\u3002<\/p>\n\n\n\n<p>\u5bfe\u8c61\uff1a\u696d\u754c\u56e3\u4f53\u304a\u3088\u3073\u6a19\u6e96\u5316\u56e3\u4f53<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306b\u7f72\u540d\u3057\u3066\u304b\u30891\u5e74\u4ee5\u5185\u306b\u3001\u30d1\u30b9\u30ad\u30fc\u306b\u3088\u308b\u30b5\u30a4\u30f3\u30a4\u30f3\u306e\u8a8d\u77e5\u5ea6\u3068\u5229\u70b9\u3092\u5411\u4e0a\u3055\u305b\u308b\u305f\u3081\u306b\u5b9f\u65bd\u3057\u305f\u884c\u52d5\u3092\u793a\u3059\u3002<\/p>\n\n\n\n<p>\u4eca\u3059\u3050\u30d1\u30b9\u30ad\u30fc\u8a93\u7d04\u306b\u7f72\u540d\u3059\u308b<\/p>\n\n\n\n<p>\u672c\u5ba3\u8a00\u306e\u7f72\u540d\u8005\u306f\u3001\u672c\u53d6\u7d44\u306b\u95a2\u9023\u3059\u308b\u30de\u30fc\u30b1\u30c6\u30a3\u30f3\u30b0\u8cc7\u6599\u306b\u4f01\u696d\u540d\uff08\u30ed\u30b4\u306f\u542b\u307e\u306a\u3044\uff09\u3092\u63b2\u8f09\u3059\u308b\u3053\u3068\u306b\u540c\u610f\u3059\u308b\u3082\u306e\u3068\u3057\u307e\u3059\u3002&nbsp;<\/p>\n\n\n\n<p>\u5f53\u56e3\u4f53\u3067\u306f\u7f72\u540d\u8005\u306e\u6c0f\u540d\u304a\u3088\u3073\u30e1\u30fc\u30eb\u30a2\u30c9\u30ec\u30b9\u3092\u53ce\u96c6\u3057\u307e\u3059\u304c\u3001\u3053\u308c\u3089\u304c\u516c\u958b\u3055\u308c\u308b\u3053\u3068\u306f\u3042\u308a\u307e\u305b\u3093\u3002<\/p>\n\n<\/div><\/div>\n<\/div>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<h2 class=\"wp-block-heading has-emerald-color has-text-color has-link-color wp-elements-ad810ada86a7a07591db3d4ce8d69097\">\ud328\uc2a4\ud0a4 \uc11c\uc57d<\/h2>\n\n\n<div class=\"gb-container gb-container-abe02133 gb-accordion\">\n<div class=\"gb-container gb-container-d5aa7221 gb-accordion__item\" data-transition=\"slide\">\n\n<button class=\"gb-button gb-button-d0a49558 gb-accordion__toggle\" id=\"gb-accordion-toggle-d0a49558\"><span class=\"gb-button-text\"><\/span><span class=\"gb-icon\"><svg xmlns=\"https:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 448 512\" width=\"1em\" height=\"1em\" ariahidden=\"true\" role=\"img\" class=\"gb-accordion__icon\"><path d=\"M207.029 381.476L12.686 187.132c-9.373-9.373-9.373-24.569 0-33.941l22.667-22.667c9.357-9.357 24.522-9.375 33.901-.04L224 284.505l154.745-154.021c9.379-9.335 24.544-9.317 33.901.04l22.667 22.667c9.373 9.373 9.373 24.569 0 33.941L240.971 381.476c-9.373 9.372-24.569 9.372-33.942 0z\" fill=\"currentColor\"><\/path><\/svg><svg xmlns=\"https:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 448 512\" width=\"1em\" height=\"1em\" ariahidden=\"true\" role=\"img\" class=\"gb-accordion__icon-open\"><path d=\"M240.971 130.524l194.343 194.343c9.373 9.373 9.373 24.569 0 33.941l-22.667 22.667c-9.357 9.357-24.522 9.375-33.901.04L224 227.495 69.255 381.516c-9.379 9.335-24.544 9.317-33.901-.04l-22.667-22.667c-9.373-9.373-9.373-24.569 0-33.941L207.03 130.525c9.372-9.373 24.568-9.373 33.941-.001z\" fill=\"currentColor\"><\/path><\/svg><\/span><\/button>\n\n\n<div id=\"gb-accordion-content-03a7c3f7\" class=\"gb-accordion__content\"><div class=\"gb-container gb-container-03a7c3f7\">\n\n<p>\ud328\uc2a4\ud0a4 \uc11c\uc57d\uc740 \uc628\ub77c\uc778 \uc11c\ube44\uc2a4 \uc81c\uacf5\uc5c5\uccb4\uc640 \uc778\uc99d \uad00\ub828 \uc194\ub8e8\uc158\/\uc11c\ube44\uc2a4 \uacf5\uae09\uc5c5\uccb4\ub97c \uc704\ud55c \uc790\ubc1c\uc801\uc778 \uc11c\uc57d\uc785\ub2c8\ub2e4. \uac1c\uc778\uc740 \uc11c\uc57d \ub300\uc0c1\uc5d0\ub294 \ud3ec\ud568\ub418\uc9c0 \uc54a\uc9c0\ub9cc, \uc120\ud638\ud558\ub294 \ucc44\ub110\uc744 \ud1b5\ud574 \ud328\uc2a4\ud0a4\uc5d0 \ub300\ud55c \uc9c0\uc9c0\ub97c \ud45c\uba85\ud558\ub294 \uac83\uc774 \uad8c\uc7a5\ub429\ub2c8\ub2e4.<\/p>\n\n\n\n<p>\uc774 \uc11c\uc57d\uc5d0 \ucc38\uc5ec\ud55c\ub2e4\ub294 \uac83\uc740, \uc11c\ube44\uc2a4 \uc81c\uacf5\uc5c5\uccb4\uc640 \uacf5\uae09\uc5c5\uccb4\uac00 1\ub144 \ub3d9\uc548 \uba85\uc2dc\ub41c \ubaa9\ud45c\ub97c \ud5a5\ud574 \uc131\uc2e4\ud558\uac8c \ub178\ub825\ud560 \uac83\uc744 \uc57d\uc18d\ud55c\ub2e4\ub294 \uc758\ubbf8\uc785\ub2c8\ub2e4. \uc11c\uc57d \ubaa9\ud45c\uc5d0 \ub300\ud574 \uce21\uc815 \uac00\ub2a5\ud55c \uc9c4\uc804\uc744 \uc774\ub8ec \uae30\uc5c5\uc740 \uc11c\uc57d\uc77c\ub85c\ubd80\ud130 1\ub144 \uc774\ub0b4\uc5d0 \uadf8 \uc131\uacfc\ub97c \uacf5\uac1c\uc801\uc73c\ub85c \ubb38\uc11c\ud654\ud574\uc57c \ud569\ub2c8\ub2e4. \uce21\uc815 \uac00\ub2a5\ud55c \uc9c4\uc804\uc744 \uc774\ub8e8\uc9c0 \ubabb\ud55c \uae30\uc5c5\ub3c4 \ub3d9\uc77c\ud55c \uae30\uac04 \ub0b4\uc5d0 \uc790\uc0ac\uc758 \ub178\ub825, \uc9c1\uba74\ud55c \uacfc\uc81c, \uc811\uadfc \ubc29\uc2dd\uc744 \uacf5\uc720\ud558\uc5ec \ub2e4\ub978 \uae30\uc5c5\ub4e4\uc774 \ubc30\uc6b8 \uc218 \uc788\ub3c4\ub85d \ud558\ub294 \uac83\uc774 \uad8c\uc7a5\ub429\ub2c8\ub2e4. \uc774 \uc11c\uc57d\uc740 \uc790\ubc1c\uc801\uc778 \ucc38\uc5ec\ub97c \uae30\ubc18\uc73c\ub85c \ud558\uba70, \ubc95\uc801 \uad6c\uc18d\ub825\uc740 \uc5c6\uc2b5\ub2c8\ub2e4.<\/p>\n\n\n\n<p>FIDO \uc5bc\ub77c\uc774\uc5b8\uc2a4\ub294 \uc774\ubbf8 \ud328\uc2a4\ud0a4 \ub85c\uadf8\uc778\uc744 \uc9c0\uc6d0\ud558\uac70\ub098 \uc790\uc0ac \uc81c\ud488\uc5d0 \ub3c4\uc785\ud55c \uc11c\ube44\uc2a4 \uc81c\uacf5\uc5c5\uccb4 \ubc0f \uc194\ub8e8\uc158 \uc81c\uacf5 \uc5c5\uccb4\uc758 \ub178\ub825\uc744 \ub192\uc774 \ud3c9\uac00\ud569\ub2c8\ub2e4. \uc774\ubbf8 \ud328\uc2a4\ud0a4\ub97c \uc9c0\uc6d0\ud558\uace0 \uc788\ub294 \uae30\uc5c5\uc740, \uac00\ub2a5\ud55c \uacbd\uc6b0, \uad6c\ud604 \ubc29\uc2dd\uacfc \uadf8\ub85c \uc778\ud55c \ud6a8\uacfc\ub97c \uacf5\uac1c\uc801\uc73c\ub85c \uba85\uc2dc\ud574 \uc8fc\uc2dc\uae30 \ubc14\ub78d\ub2c8\ub2e4.<br>\ud328\uc2a4\ud0a4 \uc11c\uc57d \ucc38\uc5ec<br>\uc11c\uc57d\uc5d0 \ucc38\uc5ec\ud55c \uae30\uc5c5\uc740, 1\ub144 \ub3d9\uc548 \ub2e4\uc74c\uc758 \uba85\uc2dc\ub41c \ubaa9\ud45c\ub97c \ud5a5\ud574 \uc120\uc758\uc758 \ub178\ub825\uc744 \uae30\uc6b8\uc77c \uac83\uc744 \uc57d\uc18d\ud569\ub2c8\ub2e4.<\/p>\n\n\n\n<p>\ud328\uc2a4\ud0a4 \uae30\ubc18 \ub85c\uadf8\uc778 \uae30\ub2a5\uc744 \uc774\ubbf8 \uad6c\ud604\ud55c \uc11c\ube44\uc2a4 \uc81c\uacf5\uc5c5\uccb4\uc758 \uacbd\uc6b0<br>\uc11c\uc57d\uc77c\ub85c\ubd80\ud130 1\ub144 \uc774\ub0b4\uc5d0 \ud68c\uc0ac \uc11c\ube44\uc2a4\uc5d0 \ub85c\uadf8\uc778\ud560 \ub54c \uc0ac\uc6a9\uc790\uc758 \ud328\uc2a4\ud0a4 \uc0ac\uc6a9\ub960\uc744 \uce21\uc815 \uac00\ub2a5\ud55c \ubc29\uc2dd\uc73c\ub85c \uc99d\uac00\uc2dc\ud0a4\uae30 \uc704\ud574 \ucde8\ud55c \uc870\uce58\ub4e4\uc744 \uacf5\uc720\ud574\uc57c \ud569\ub2c8\ub2e4.<\/p>\n\n\n\n<p>\ud328\uc2a4\ud0a4 \uae30\ubc18 \ub85c\uadf8\uc778 \uae30\ub2a5\uc744 \uad6c\ud604\uc744 \uc900\ube44\uc911\uc778 \uc11c\ube44\uc2a4 \uc81c\uacf5\uc5c5\uccb4\uc758 \uacbd\uc6b0<br>\uc11c\uc57d\uc77c\ub85c\ubd80\ud130 1\ub144 \uc774\ub0b4\uc5d0, \uc790\uc0ac \uc11c\ube44\uc2a4\uc5d0 \ud328\uc2a4\ud0a4 \ub85c\uadf8\uc778\uc744 \ud65c\uc131\ud654\ud558\uae30 \uc704\ud574 \ucde8\ud55c \uce21\uc815 \uac00\ub2a5\ud55c \uc870\uce58\ub97c \uacf5\uc720\ud574\uc57c \ud569\ub2c8\ub2e4.<\/p>\n\n\n\n<p>FIDO \uae30\ubc18 \uc81c\ud488 \ubc0f\/\ub610\ub294 \uc11c\ube44\uc2a4\ub97c \ubcf4\uc720\ud55c \uc194\ub8e8\uc158 \uacf5\uae09\uc5c5\uccb4\uc758 \uacbd\uc6b0<br>\uc11c\uc57d\uc77c\ub85c\ubd80\ud130 1\ub144 \uc774\ub0b4\uc5d0, \uc790\uc0ac\uc758 \uc194\ub8e8\uc158 \ubc0f\/\ub610\ub294 \uc11c\ube44\uc2a4\ub97c \ud1b5\ud55c \ud328\uc2a4\ud0a4 \uc0ac\uc6a9 \ud655\ub300\ub97c \uc704\ud574 \ucde8\ud55c \uc870\uce58\ub97c \uc785\uc99d\ud574\uc57c \ud569\ub2c8\ub2e4.<\/p>\n\n\n\n<p>FIDO \uae30\ubc18 \uc81c\ud488 \ubc0f\/\ub610\ub294 \uc11c\ube44\uc2a4\ub97c \uac1c\ubc1c \uc911\uc778 \uc194\ub8e8\uc158 \uacf5\uae09\uc5c5\uccb4\uc758 \uacbd\uc6b0<br>\uc11c\uc57d\uc77c\ub85c\ubd80\ud130 1\ub144 \uc774\ub0b4\uc5d0, \uc81c\ud488\uc758 FIDO \uc2dc\ud5d8\uc778\uc99d\uc744 \ud68d\ub4dd\ud558\uace0, \ud328\uc2a4\ud0a4 \ub85c\uadf8\uc778\uc744 \uc9c0\uc6d0\ud558\ub294 \uc81c\ud488 \ub610\ub294 \uc11c\ube44\uc2a4\ub97c \ucd9c\uc2dc\ud558\uae30 \uc704\ud574 \ucde8\ud55c \uce21\uc815 \uac00\ub2a5\ud55c \uc870\uce58\ub97c \uacf5\uc720\ud574\uc57c \ud569\ub2c8\ub2e4.<\/p>\n\n\n\n<p>\uc5c5\uacc4 \ud611\ud68c \ubc0f \ud45c\uc900\ud654 \uae30\uad6c\uc758 \uacbd\uc6b0<br>\uc11c\uc57d\uc77c\ub85c\ubd80\ud130 1\ub144 \uc774\ub0b4\uc5d0, \ud328\uc2a4\ud0a4 \ub85c\uadf8\uc778\uc758 \uc778\uc9c0\ub3c4\uc640 \ud61c\ud0dd\uc744 \ub192\uc774\uae30 \uc704\ud574 \ucde8\ud55c \uc870\uce58\ub97c \uacf5\uc720\ud574\uc57c \ud569\ub2c8\ub2e4.<\/p>\n\n\n\n<p>\uc9c0\uae08 \ud328\uc2a4\ud0a4 \uc11c\uc57d\uc5d0 \ucc38\uc5ec\ud558\uc138\uc694<br>\uc11c\uc57d\uc5d0 \uc11c\uba85\ud55c \uae30\uc5c5\uc740, \ud68c\uc0ac\uba85(\ub85c\uace0\ub294 \ubbf8\ud3ec\ud568)\uc774 \ud574\ub2f9 \uc11c\uc57d \uad00\ub828 \ub9c8\ucf00\ud305 \uc790\ub8cc\uc5d0 \ud3ec\ud568\ub418\ub294 \uac83\uc5d0 \ub3d9\uc758\ud558\uac8c \ub429\ub2c8\ub2e4. \uc11c\uba85\uc790\uc758 \uc774\ub984\uacfc \uc774\uba54\uc77c \uc8fc\uc18c\ub294 \uc218\uc9d1\ub418\uc9c0\ub9cc \uacf5\uac1c\ub418\uc9c0 \uc54a\uc2b5\ub2c8\ub2e4.<\/p>\n\n<\/div><\/div>\n<\/div>\n<\/div><\/div>\n<\/div>\n\n\n\n<p id=\"fill-out-the-form\"><strong>Complete the form<\/strong><\/p>\n\n\n\n\n<div class=\"gb-container gb-container-084581af\">\n\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why should my company consider joining the FIDO Alliance?<\/summary>\n<p>There are significant benefits to taking part in FIDO Alliance as a member, whether your company is a vendor looking to bring FIDO-based solutions to market, or if your organization is a service provider seeking to understand the most effective ways to deploy FIDO Authentication to your customers and\/or employees. You can learn more <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">here<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What\u2019s the process for joining the FIDO Alliance?<\/summary>\n<p>Please see the required steps on the FIDO Alliance membership <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">web page<\/a>.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does FIDO compare with PKI?<\/summary>\n<p>FIDO takes a \u201clightweight\u201d approach to asymmetric public-key cryptography, which offers service providers a way to extend the security benefits of public-key cryptography to a wider array of applications, domains, and devices \u2013 especially where traditional PKI has proven difficult or impossible. FIDO is not a replacement for PKI but rather complements it, enabling a greater number of users and applications to be protected using asymmetric encryption. This is especially important in situations where the alternative has been a username and password.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What devices and platforms have FIDO support?<\/summary>\n<p>The FIDO Alliance developed its FIDO2 specifications with the W3C to enable FIDO Authentication capabilities to be built into a wider array of devices, platforms, and web browsers. FIDO is currently supported in Google Chrome, Mozilla Firefox, Microsoft Edge, and Apple Safari (MacOS), iOS web browsers, as well as Windows 10 and Android platforms.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are some examples of FIDO being deployed in-market today?<\/summary>\n<p>Many leading organizations around the world have deployed FIDO Authentication to their employees and users, reducing their security risks and improving user experience. Check out our homepage under \u201cwho\u2019s using FIDO\u201d for a sample.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why did FIDO publish multiple specifications? What are the differences?<\/summary>\n<p>The FIDO Alliance has published three sets of specifications for simpler, stronger authentication \u2013 FIDO U2F, FIDO UAF and FIDO2 \u2013 in order to provide for the widest range of use cases and deployment scenarios:<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>When were the FIDO specifications published?<\/summary>\n<p>From its inception, the FIDO Alliance stated intentions to change the nature of authentication by developing specifications that define an open, scalable, interoperable set of mechanisms that supplant reliance on passwords to securely authenticate users of online services. Two years after its inception, the Alliance delivered the final 1.0 specifications on December 2014 to enable that vision. This was an important milestone on the industry\u2019s road to ubiquitous simpler, stronger authentication, and many deployments brought FIDO Authentication to users around the globe. To further add support for FIDO Authentication across devices and platforms, FIDO Alliance published its second set of specifications, FIDO2, in March 2019. See \u201cWhy did the FIDO Alliance see the need for FIDO2?\u201d for more information.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the FIDO specifications?<\/summary>\n<p>The FIDO Alliance has published three sets of specifications for simpler, stronger authentication: FIDO Universal Second Factor (FIDO U2F), FIDO Universal Authentication Framework (FIDO UAF) and the Client to Authenticator Protocols (CTAP). CTAP is complementary to the <a href=\"https:\/\/www.w3.org\/TR\/2018\/CR-webauthn-20180320\/\" target=\"_blank\" rel=\"noopener\">W3C\u2019s Web Authentication (WebAuthn) specification<\/a>; together, they are known as FIDO2.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What\u2019s the best way to follow FIDO\u2019s progress?<\/summary>\n<p>The <a href=\"https:\/\/fidoalliance.org\/\">FIDO Alliance website<\/a> provides comprehensive information about the Alliance, its <a href=\"https:\/\/fidoalliance.org\/specifications\/\">specifications<\/a>, <a href=\"https:\/\/fidoalliance.org\/certification\/fido-certified-products\/\">FIDO Certified products<\/a> and best practices and <a href=\"https:\/\/fidoalliance.org\/content\/fido-in-the-news\/\">general progress<\/a>. You can also <a href=\"https:\/\/fidoalliance.org\/newsletter-sign-up\/\">sign up<\/a> to receive updates and invitations to future events, many of which are open to the public. You can also follow <a href=\"https:\/\/twitter.com\/FIDOAlliance\" target=\"_blank\" rel=\"noopener\">@FIDOalliance<\/a> on Twitter and\/or on <a href=\"https:\/\/www.linkedin.com\/company\/the-fido-alliance\" target=\"_blank\" rel=\"noopener\">LinkedIn<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is the FIDO Alliance a non-profit organization? What is the scope?<\/summary>\n<p>The FIDO (Fast IDentity Online) Alliance is a 501(c)6 non-profit organization incorporated in mid-2012 to develop standards that address the lack of interoperability among strong authentication devices as well as the problems users face with creating and remembering multiple usernames and passwords. To learn more about the FIDO Alliance governance and structure, please refer to the <a href=\"https:\/\/fidoalliance.org\/overview\/\">About FIDO page<\/a> and the <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">Membership Details page.<\/a><\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Do the FIDO specifications enable anyone to begin using the specs to develop and offer FIDO certified products?<\/summary>\n<p>FIDO\u2019s specifications are public and available for anyone to read and analyze. But only FIDO Alliance Members benefit from \u201cthe promise\u201d to not assert patent rights against other members\u2019 implementations (see the <a href=\"https:\/\/fidoalliance.org\/wp-content\/uploads\/2019\/12\/FIDO-Alliance-Membership-Agreement.pdf\" target=\"_blank\" rel=\"noopener\">FIDO Alliance Membership Agreement<\/a> for details). Anyone may join the FIDO Alliance; we encourage even very small companies with a very low cost to join at the entry level. Members at all levels not only benefit from the mutual non-assert protection but also participate with FIDO Alliance members, activities, and developments; Associates have more limited participation benefits (https:\/\/fidoalliance.org\/members\/membership-benefits\/). All are invited to join the FIDO Alliance and participate.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is one FIDO token\/dongle\/device better than another? How can I choose which to buy?<\/summary>\n<p>FIDO specifications are device-agnostic and support a full range of authentication technologies, including FIDO Security Keys and biometrics such as fingerprint and iris scanners, voice and facial recognition, as well as PIN or pattern-protected microSD cards. FIDO specifications will also enable existing solutions and communications standards, such as Trusted Platform Module (TPM), USB Security Tokens, embedded Secure Elements (eSE), Smart Cards, Bluetooth Low Energy (BLE), and Near Field Communication (NFC). Because FIDO specifications are open, they are designed to be extensible and to accommodate future innovation, as well as protect existing investments.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Has FIDO made implementation rights available to anyone?<\/summary>\n<p>FIDO Alliance members have all committed to the promise contained within our Membership Agreement to not assert their patents against any other member implementation of FIDO 1.0 final specifications (referred to as \u201cProposed Standard\u201d in our <a href=\"https:\/\/fidoalliance.org\/wp-content\/uploads\/2019\/12\/FIDO-Alliance-Membership-Agreement.pdf\" target=\"_blank\" rel=\"noopener\">Membership Agreement<\/a>). Anyone interested in deploying a FIDO compliant solution can do so without joining the Alliance, and they are strongly encouraged to use FIDO Certified products to enable that deployment.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How can I be sure that the product I\u2019m buying conforms to FIDO standards?<\/summary>\n<p>The FIDO Alliance Certification Working Group is responsible for testing products for conformance to FIDO specifications and interoperability between those implementations. You can learn more about the FIDO\u00ae Certified program <a href=\"https:\/\/fidoalliance.org\/certification\/\">here<\/a>.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why are standards important?<\/summary>\n<p>Open industry standards assure that existing and future products and offerings are compatible and that anyone can evaluate the technology. Users can depend on their FIDO devices working wherever FIDO authentication is supported. Service providers and enterprises can accommodate various devices and <em>services<\/em> without having to make new investments or reverting to proprietary configurations.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can\u2019t someone break into an account if they steal a device?<\/summary>\n<p>No. In order to break into an account, the criminal would need not only the user\u2019s device that was registered as a FIDO Authenticator to the account but also the ability to defeat the user identification challenge used by the Authenticator to protect the private keys \u2013 such as a username and PIN or a biometric. This makes it extremely difficult to break into a FIDO-enabled account.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO approach to biometric authentication make a user safer? Could anyone steal my biometric information from a device or online service?<\/summary>\n<p>When used in FIDO Authentication, user biometric data never leaves the device and is never stored on a central server where it could be stolen in a breach. FIDO\u2019s on-device model for authentication eliminates the risk of a remote attack. If a would-be attacker had access to the user\u2019s actual device, a successful spoof would be quite difficult. First, the attacker must obtain a perfectly formed, complete latent print that is also enrolled on the target user\u2019s device. Then, the attacker must gain access to the user\u2019s device in order to control only that one device. The single spoof, even if accomplished, doesn\u2019t approach the potential harm done by today\u2019s typical mass-scale attack, which can result in harvesting millions and hundreds of millions of users\u2019 credentials.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does FIDO Authentication make users safer on the web?<\/summary>\n<p>Unlike current password-based authentication models that have proven vulnerable to mass-scale attacks and fraud, FIDO authentication credentials are never shared or stored in centralized databases. FIDO credentials are known and maintained only by the user\u2019s own device. All that is ever stored by the service provider are the public keys paired to the user\u2019s device where the private keys are stored. For additional security and privacy, biometrics used in FIDO Authentication never leave the device. This security model eliminates the risks of phishing, all forms of password theft and replay attacks. A would-be attacker would need the user\u2019s physical device to even attempt a hack (see below, \u201ccan\u2019t someone break into an account if they steal a device?\u201d for more information). The password ecosystem has afforded attackers with great return on investment with relatively limited risk; the FIDO ecosystem is far more difficult, expensive and risky for attackers to profit from.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do you protect against root kits and malware attacks on the embedded fingerprint sensor?<\/summary>\n<p>The FIDO Alliance recently launched the Authenticator Certification Program. This program introduces Authenticator Security Requirements to the FIDO Certification Program specifically for authenticators. Each authenticator that is certified under the FIDO Certification program is validated to meet specific security assurance levels depending on the level of security the vendor is seeking. The higher the level, the greater the security assurance. More information about this program can be found here: <a href=\"https:\/\/fidoalliance.org\/certification\/authenticator-certification-levels\/\">https:\/\/fidoalliance.org\/certification\/authenticator-certification-levels\/<\/a>.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>If I use the same device with multiple websites, can one site know that I use it with another site?<\/summary>\n<p>No, this type of information exchange is prevented with FIDO Authentication. Each device\/website pairing requires separate registration and a separate cryptographic key pair. Once registered, a user can easily authenticate to multiple sites from the same device, yet each site has no knowledge of the user interactions with other sites. FIDO does not introduce any new tracking mechanism that could be used to correlate user activity online.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Does FIDO get any of my personal information?<\/summary>\n<p>No. FIDO Alliance only specifies standards for strong authentication and tests implementations for compliance to those standards; the Alliance does not provide services or equip devices or sites. Device manufacturers, online service providers, enterprises, and developers use the FIDO specifications to build products, provide services, and enable sites and browsers with FIDO authentication. Under FIDO specifications, the user\u2019s credentials must remain on the user\u2019s device, and they are never shared with a provider or service.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How can companies get involved in the FIDO Alliance\u2019s new work areas?<\/summary>\n<p>The IDWG and IoT TWG are now open to industry participants. Participation in FIDO Alliance working groups is open to all board and sponsor level members of the FIDO Alliance. For more information on joining the Alliance, visit <a href=\"https:\/\/fidoalliance.org\/members\/membership-benefits\/\">https:\/\/fidoalliance.org\/members\/membership-benefits<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What will the IoT Technical Working Group do?<\/summary>\n<p>The IoT TWG will provide a comprehensive authentication framework for IoT devices in keeping with the fundamental mission of the Alliance \u2013 passwordless authentication. The IoT TWG will develop use cases, target architectures and specifications covering: IoT device attestation\/authentication profiles to enable interoperability between service providers and IoT devices; automated onboarding, and binding of applications and\/or users to IoT devices; and IoT device authentication and provisioning via smart routers and IoT hubs.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What will the Identity Verification and Binding Working Group do?<\/summary>\n<p>The FIDO Alliance has identified newer remote, possession-based techniques including biometric \u201cselfie\u201d matching and government-issued identity document authentication as having the potential to greatly improve the quality of identity assurance for new account onboarding and account recovery. The IDWG will define criteria for this type of remote identity verification, as well as others, and develop a certification program and educational materials to support the adoption of that criteria.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How will the Alliance fulfill these new standards and certification initiatives?<\/summary>\n<p>The Alliance has formed two new working groups: the Identity Verification and Binding Working Group (IDWG) and the IoT Technical Working Group (IoT TWG) to establish guidelines and certification criteria in these areas. The FIDO Alliance will continue to focus on development and adoption of its user authentication standards and related programs and use them as a foundation for this expanded work, with contributions from current members and new industry participants.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do these new areas related to user authentication?<\/summary>\n<p>Identity verification and IoT security are both adjacent to the FIDO Alliance core focus on user authentication. For accounts protected by FIDO Authentication, identity verification for the account recovery process when a FIDO device is lost or stolen becomes critical to maintaining the integrity of the user\u2019s account. With IoT devices, typical industry practices is to ship them with default password credentials and manual onboarding, which leaves them open to attack. The security gaps in both of these areas can most effectively addressed through industry collaboration and standardization rather than siloed, proprietary approaches.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the FIDO Alliance trying to achieve with these new initiatives?<\/summary>\n<p>Ultimately, the Alliance is striving to increase the efficacy and market adoption of FIDO Authentication by addressing adjacent technology areas that leave security vulnerabilities on the web. There is a gap between the high assurance provided by FIDO Authentication standards and the lower assurance methods used in identity verification for account recovery and IoT authentication. The Alliance aims to strengthen identity verification assurance to support better account recovery and automate secure device onboarding to remove password use from IoT.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the FIDO Alliance new work areas?<\/summary>\n<p>The Alliance announced new work areas to develop standards and certification programs in identity verification and the Internet of Things (IoT).<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is next for the FIDO Alliance and FIDO standards?<\/summary>\n<p>FIDO Alliance\u2019s work is just beginning. The specifications and certification programs are continuing to evolve, and our deployment work is taking on even greater importance. Additionally, the Alliance has just launched new work areas in IoT and identity verification, which leverage the Alliance\u2019s broad coalition of leading organizations from around the world to help standardize technologies adjacent to user authentication. For more information on these work areas, read <a href=\"https:\/\/fidoalliance.org\/fido-alliance-announces-id-and-iot-initiatives\/\">https:\/\/fidoalliance.org\/fido-alliance-announces-id-and-iot-initiatives\/<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO Alliance ensure interoperability with FIDO2?<\/summary>\n<p>FIDO Alliance provides <a href=\"https:\/\/fidoalliance.org\/certification\/interoperability-testing\/\">interoperability testing<\/a> and <a href=\"https:\/\/fidoalliance.org\/certification\/functional-certification\/\">certification<\/a> for servers, clients, and authenticators adhering to FIDO2 specifications. Additionally, the Alliance has introduced a new Universal Server certification for servers that interoperate with all FIDO Authenticator types (UAF, U2F, CTAP). As a best practice, the FIDO Alliance recommends online services and enterprises deploy a Universal Server to ensure support for all FIDO Certified Authenticators.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Does FIDO2 mean that FIDO U2F is dead?<\/summary>\n<p>Not at all. FIDO U2F capabilities have merged into FIDO2\u2019s CTAP2 protocol, and FIDO U2F security keys will continue to work with services that support U2F authentication as well as those that have support FIDO2 authentication.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Does FIDO2 replace the FIDO U2F and FIDO UAF specifications?<\/summary>\n<p>The specifications under FIDO2 support existing passwordless FIDO UAF and FIDO U2F use cases and specifications and expand the availability of FIDO Authentication. Users that already have external FIDO-compliant devices, such as FIDO U2F security keys, will be able to continue to use these devices with web applications that support WebAuthn. Existing FIDO UAF devices can still be used with pre-existing services as well as new service offerings based on the FIDO UAF protocols.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the status of FIDO2 browser and platform implementation?<\/summary>\n<p>Current adoption status is available <a href=\"https:\/\/fidoalliance.org\/fido2\/fido2-web-authentication-webauthn\/\">here<\/a>.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the status of FIDO2 specifications development?<\/summary>\n<p>FIDO2 standards are published and available for implementation today. WebAuthn reached W3C\u2019s final Recommendation status in March 2019 and is an official web standard. CTAP is a final FIDO Alliance specification.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why did FIDO Alliance submit specifications to the W3C?<\/summary>\n<p>FIDO Alliance partnered with W3C to standardize FIDO Authentication for the entire web platform so the FIDO ecosystem could grow by an entire community of web browsers and web application servers supporting the standard. W3C is where the web community produces their standards, so it was more practical to work in that forum.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the relationship between FIDO2 and W3C\u2019s WebAuthn?<\/summary>\n<p>A good rule of thumb is to remember this simple equation:<\/p>\n  <p>FIDO2 = W3C WebAuthn + CTAP<\/p>\n  <p>This is the full story of FIDO2\u2019s development:<\/p>\n  <p>After the release of the FIDO UAF and FIDO U2F specifications, FIDO Alliance focused on making FIDO Authentication more accessible to users worldwide. The Alliance developed three technical specifications that defined one web-based API, enabling FIDO Authentication to be built directly into browsers and platforms. These specifications were submitted to the W3C, the international standards organization for the World Wide Web, in November of 2015. FIDO Alliance member companies worked within the W3C\u2019s Web Authentication Working Group to finalize the API, which became known as WebAuthn. WebAuthn was officially recognized as a W3C web standard in March 2019.<\/p>\n  <p>In the same time period, the FIDO Alliance created and finalized a complementary specification to WebAuthn: the Client to Authenticator Protocol (CTAP). CTAP makes WebAuthn even more accessible to users by allowing them to use the devices they already own, such as their mobile phone, security key or Windows 10 PC to authenticate to WebAuthn-enabled browsers and platforms.<\/p>\n  <p>Together, WebAuthn and CTAP are called FIDO2. The FIDO Alliance manages and maintains the certification program to ensure interoperability of all the FIDO2 implementations in the market \u2013 clients, servers and authentication devices.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Why did the FIDO Alliance see the need for FIDO2?<\/summary>\n<p>The FIDO Alliance goal has always been ubiquitous strong authentication across the web. That means building support for FIDO Authentication into every device that people use every day. The Alliance made notable progress with its initial FIDO U2F and FIDO UAF specifications, especially on mobile platforms. FIDO2 expands the reach of FIDO Authentication by making it a built-in feature across browsers and web platforms, which is a significant step toward the Alliance\u2019s overall goal.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is it \u201cFIDO2\u201d or \u201cFIDO 2.0\u201d?<\/summary>\n<p>FIDO2 is the official name for the complete set of FIDO\u2019s latest standards.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What specifications are included in FIDO2?<\/summary>\n<p>FIDO2 includes two specifications:<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is FIDO2?<\/summary>\n<p>FIDO2 is the overarching term for FIDO Alliance\u2019s newest set of strong authentication standards. FIDO2 includes two specifications: W3C\u2019s Web Authentication (WebAuthn) and FIDO Alliance\u2019s Client to Authenticator Protocol (CTAP).<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can I use the same FIDO device with multiple websites? Can I use multiple FIDO devices with the same website?<\/summary>\n<p>Yes, you can use multiple websites from one FIDO device. Each device\/website pairing requires a separate registration and a separate cryptographic key pair. Once registered, a user can easily authenticate to multiple sites from the same device, yet each site has no knowledge of the user interactions with other sites.<\/p>\n  <p>If a user acquires a new device or wants to use multiple FIDO devices, the user needs only register each of the devices at the sites where he wants to use them. Once a device is registered at a site, it will be recognized whenever the user needs to authenticate at that site. When a user visits a site with a new device that hasn\u2019t been registered, and thus isn\u2019t automatically recognized, the user will be prompted to register the new FIDO device to enable FIDO authentication with the new device at that site.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Will FIDO devices work when I don\u2019t have Internet connectivity?<\/summary>\n<p>The purpose of the FIDO model is to provide a secure and simple authentication experience for online services. The authentication involves a user with a device connecting to a service over a network.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the Certificate number format of the FIDO Alliance issued Certificates?<\/summary>\n<p>The FIDO Alliance Certificate number format is: AA-NNNNN-SSSSS, where AA is the Program Identifier, NNNNN is the Certification number, and SSSSS is the Product Identifier. The Program Identifier corresponds to the certification program under which the Certificate was issued.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the audit process for products in the market?<\/summary>\n<p>The FIDO Alliance staff will audit on a monthly basis the usage of FIDO Certified logos and published claims of certification. Auditing of actual implementations will be driven by market feedback. Should any concerns arise, feedback can be submitted through the <a href=\"https:\/\/fidoalliance.org\/certified-logo-violation\/\">Certified Logo Violation <\/a>form.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Must I certify a product in order to market it?<\/summary>\n<p>No. But a product must be certified to claim to be FIDO Certified and use the FIDO Certified logo.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO Alliance certify derivative products?<\/summary>\n<p>Derivative certification was created to streamline the certification process for implementers that have a large volume of certifications that are essentially all based on the same implementation. In this case, implementers may certify one implementation and the rest may be registered as \u201cderivatives\u201d of that base certification. Derivatives don\u2019t require attending interoperability events to achieve certification, but they do require that the derivative implementation run and pass conformance testing. The implementation cannot change in any substantial way from the original certification earned via our test tools and interoperability testing. If there are changes to the implementation, then it will need to go through the FIDO Impact Analysis to determine if the implementation requires a Delta Certification or Recertification.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How often do testing events occur?<\/summary>\n<p>Interoperability events occur at least every 90 days, but may occur more frequently based on implementer demand.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the costs associated with certification?<\/summary>\n<p>Fees are per implementation certified and must be paid before a Certificate will be issued.<\/p>\n    <p>For an overview of the FIDO Certification Fees per program, please go to the <a href=\"https:\/\/fidoalliance.org\/certification\/certification-fees\/\" target=\"_blank\" rel=\"noopener\">Certification Fees<\/a> page.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can I become FIDO Certified if I am not a FIDO Alliance Member?<\/summary>\n<p>Yes. Non-members are welcome to certify their implementations.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is a Vendor ID and who needs one?<\/summary>\n<p>The UAF authenticator specification defines an AAID field that is half Vendor ID and half Device ID used to uniquely identify each authenticator. The Vendor ID is a unique identifier assigned by FIDO to each company implementing a UAF authenticator. The other half of the AAID field, the Device ID, is assigned to the authenticator by the implementing company. Only UAF Authenticators require a Vendor ID.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How long is a product certified, and is recertification required when protocols change?<\/summary>\n<p>A product is certified indefinitely as long as the code base of its FIDO implementation doesn\u2019t change in any substantial way. Certification can only be terminated in rare instances, such as determining that an implementation improperly passed test tools or interoperability events. Certification only applies to a specific specification and implementation class (i.e. \u201cUAF Authenticator\u201d). If new major versions of specifications are released (as determined by the FIDO Certification Working Group) and an implementation would like to claim conformance with that specification, new certification will be required.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is there a Trademark License Agreement (TMLA) requirement for logo use?<\/summary>\n<p>Use of the FIDO Certified logo will require signing a TMLA. There is a streamlined process for Relying Parties that wish to use the certification logo on their websites, which includes a <a href=\"https:\/\/fidoalliance.org\/overview\/legal\/fido-trademark-and-service-mark-usage-agreement-for-websites\/\">\u201cclickless\u201d license agreement.<\/a><\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Will there be a FIDO Certified logo?<\/summary>\n<p>Yes. There is a recognizable FIDO Certified logo for vendors to include with their websites, product materials, packaging, etc.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do I get started?<\/summary>\n<p>Start by making sure your implementation passes the <a href=\"https:\/\/fidoalliance.org\/certification\/functional-certification\/conformance\/\">conformance tests<\/a> (registration required). After you\u2019ve validated your implementation, <a href=\"https:\/\/fidoalliance.org\/certification\/interoperability-testing\/interop-registration\/\">register<\/a> for an Interoperability event and you\u2019re on your way to certifying your product.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the FIDO Alliance Metadata Service?<\/summary>\n<p>The FIDO Alliance Metadata Service (MDS) is a web-based tool where FIDO authenticator vendors can publish metadata statements for FIDO servers to download. This provides organizations deploying FIDO servers with a centralized and trusted source of information about FIDO authenticators.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What kinds of companies should get involved?<\/summary>\n<p>Vendor companies looking to bring FIDO-based solutions to market and\/or organization service providers seeking to understand the most effective ways to deploy FIDO Authentication will benefit the most from participating in FIDO Alliance working groups.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do companies benefit from joining the working groups?<\/summary>\n<p>By taking part in FIDO Alliance\u2019s technical working groups, members have the ability to shape and have early visibility into FIDO\u2019s technical output \u2013 which can help accelerate product and service development. Participating in the working groups will also enable your team to get peer-based feedback to aid with your own implementations, while also creating an opportunity to have your company\u2019s vision reflected in deployment guidelines and recommendations.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can you describe the functional testing process?<\/summary>\n<p>There are four major testing steps:<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How is the testing done?<\/summary>\n<p>Certification starts with self-assessment of specification conformance through the use of FIDO Alliance provided test tools, followed by interoperability testing with at least three test partners at FIDO Alliance-proctored test events. At this time, there is no lab aspect to the certification program, but the Certification Working Group is currently reviewing requirements to develop and implement a Functional Lab Accreditation program. See the <a href=\"https:\/\/fidoalliance.org\/certification\/getting-started\/\">Getting Started<\/a> web page to learn more.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Are there separate submission fees for testing against each of the FIDO Alliance specifications?<\/summary>\n<p>Yes. Implementations must request certification (and pay the certification fees) for each implementation class they are seeking to certify. For example, if an implementation certifies for both a FIDO UAF Server and a FIDO2 Server, that implementation must follow the certification process for both (and pay the certification fees for both). The implementation would ultimately receive two certifications. The primary difference between testing for different specifications is they have different test tools and the different interoperability events.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Our company just built a new product but we haven\u2019t gotten it certified yet. Can we say that it is FIDO Certified while we are working on achieving our certification?<\/summary>\n<p>No. Only products that have passed through FIDO Certification program and have been granted a certification number can claim to be FIDO Certified.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the Certificate number format of the FIDO Alliance issued Certificates?<\/summary>\n<p>The FIDO Alliance issued Certificates have the following numerical format:<\/p>\n    <p>SSSXYZAYYYYMMDD####<\/p>\n    <p>SSS \u2013 Specification number (UAF or U2F)<\/p>\n    <p>X \u2013 Specification number<\/p>\n    <p>Y \u2013 Specification minor number<\/p>\n    <p>Z \u2013 Specification revision number<\/p>\n    <p>A \u2013 Specification errata number<\/p>\n    <p>YYYY \u2013 Year issued<\/p>\n    <p>MM \u2013 Month issued<\/p>\n    <p>DD \u2013 Day issued<\/p>\n    <p>#### \u2013 The number of the certificate issued today<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the audit process for products in the market?<\/summary>\n<p>The FIDO Alliance staff will audit on a monthly basis the usage of FIDO Certified logos and published claims of certification. Auditing of actual implementations will be driven by market feedback. Should any concerns arise, feedback can be submitted through the <a href=\"https:\/\/fidoalliance.org\/certified-logo-violation\/\">Certified Logo Violation <\/a>form.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Must I certify a product in order to market it?<\/summary>\n<p>No. But a product must be certified to claim to be FIDO Certified and use the FIDO Certified logo.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How does the FIDO Alliance certify derivative products?<\/summary>\n<p>Derivative certification was created to streamline the certification process for implementers that have a large volume of certifications that are essentially all based on the same implementation. In this case, implementers may certify one implementation and the rest may be registered as \u201cderivatives\u201d of that base certification. Derivatives don\u2019t require attending interoperability events to achieve certification, but they do require that the derivative implementation run and pass conformance testing. The implementation cannot change in any substantial way from the original certification earned via our test tools and interoperability testing. If there are changes to the implementation, then it will need to go through the FIDO Impact Analysis to determine if the implementation requires a Delta Certification or Recertification.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How often do testing events occur?<\/summary>\n<p>Interoperability events occur at least every 90 days, but may occur more frequently based on implementer demand.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What are the costs associated with certification?<\/summary>\n<p>Fees are per implementation certified and must be paid before a Certificate will be issued.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can I become FIDO Certified if I am not a FIDO Alliance Member?<\/summary>\n<p>Yes. Non-members are welcome to certify their implementations.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is a Vendor ID and who needs one?<\/summary>\n<p>The UAF authenticator specification defines an AAID field that is half Vendor ID and half Device ID used to uniquely identify each authenticator. The Vendor ID is a unique identifier assigned by FIDO to each company implementing a UAF authenticator. The other half of the AAID field, the Device ID, is assigned to the authenticator by the implementing company. Only UAF Authenticators require a Vendor ID.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How long is a product certified, and is recertification required when protocols change?<\/summary>\n<p>A product is certified indefinitely as long as the code base of its FIDO implementation doesn\u2019t change in any substantial way. Certification can only be terminated in rare instances, such as determining that an implementation improperly passed test tools or interoperability events. Certification only applies to a specific specification and implementation class (i.e. \u201cUAF Authenticator\u201d). If new major versions of specifications are released (as determined by the FIDO Certification Working Group) and an implementation would like to claim conformance with that specification, new certification will be required.<\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is there a Trademark License Agreement (TMLA) requirement for logo use?<\/summary>\n<p>Use of the FIDO Certified logo will require signing a TMLA. There is a streamlined process for Relying Parties that wish to use the certification logo on their websites, which includes a <a href=\"https:\/\/fidoalliance.org\/overview\/legal\/fido-trademark-and-service-mark-usage-agreement-for-websites\/\">\u201cclickless\u201d license agreement.<\/a><\/p>\n<\/details>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Will there be a FIDO Certified logo?<\/summary>\n<p>Yes. There is a recognizable FIDO Certified logo for vendors to include with their websites, product materials, packaging, etc.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>How do I get started?<\/summary>\n<p>Start by making sure your implementation passes the <a href=\"https:\/\/fidoalliance.org\/certification\/functional-certification\/conformance\/\">conformance tests<\/a> (registration required). After you\u2019ve validated your implementation, <a href=\"https:\/\/fidoalliance.org\/certification\/interoperability-testing\/interop-registration\/\">register<\/a> for an Interoperability event and you\u2019re on your way to certifying your product.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is the FIDO Alliance Metadata Service?<\/summary>\n<p>The FIDO Alliance Metadata Service (MDS) is a web-based tool where FIDO authenticator vendors can publish metadata statements for FIDO servers to download. This provides organizations deploying FIDO servers with a centralized and trusted source of information about FIDO authenticators.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What kinds of companies should get involved?<\/summary>\n<p>Vendor companies looking to bring FIDO-based solutions to market and\/or organization service providers seeking to understand the most effective ways to deploy FIDO Authentication will benefit the most from participating in FIDO Alliance working groups.<\/p>\n<\/details>\n<\/div>\n\n<\/div><\/div>\n\n\n<p><iframe src=\"https:\/\/cdn.forms-content.sg-form.com\/b57633dc-0595-11f0-98e8-d2afb8abfb0b\" style=\"width:600px; height:900px !important;\" frameborder=\"3\"><\/iframe><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"See-Who-Has-Signed-the-Pledge\">See Who Has Signed the Pledge<\/h2>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-28f84493 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<ul class=\"wp-block-list\">\n<li>1Kosmos<\/li>\n\n\n\n<li>1Password<\/li>\n\n\n\n<li>A&amp;M Insulations Ltd.<\/li>\n\n\n\n<li>A4 Technology Pty Ltd.<\/li>\n\n\n\n<li>ABANCA<\/li>\n\n\n\n<li>Accertify, Inc.<\/li>\n\n\n\n<li>AcuitySecurity.io Ltd.<\/li>\n\n\n\n<li>Aflac<\/li>\n\n\n\n<li>ALLEN TATE<\/li>\n\n\n\n<li>Allied Universal Security<\/li>\n\n\n\n<li>Allthenticate<\/li>\n\n\n\n<li>Amazon<\/li>\n\n\n\n<li>ANZ Bank<\/li>\n\n\n\n<li>Apple Inc<\/li>\n\n\n\n<li>Aspen Aire<\/li>\n\n\n\n<li>Atlancube<\/li>\n\n\n\n<li>Atomworks LLC<\/li>\n\n\n\n<li>AuthenTrend<\/li>\n\n\n\n<li>Authgear<\/li>\n\n\n\n<li>Authsignal<\/li>\n\n\n\n<li>AYANWORKS<\/li>\n\n\n\n<li>BankID BankAxept<\/li>\n\n\n\n<li>Baylor Scott and White<\/li>\n\n\n\n<li>Big Idea Technology<\/li>\n\n\n\n<li>BRJU InfoSec Inc<\/li>\n\n\n\n<li>Broadcom, Inc.<\/li>\n\n\n\n<li>Burlington Community Schools<\/li>\n\n\n\n<li>Buypass<\/li>\n\n\n\n<li>Cancer Services Limited<\/li>\n\n\n\n<li>Capital One<\/li>\n\n\n\n<li>Caravel Autism Health<\/li>\n\n\n\n<li>CardLab Innovation ApS<\/li>\n\n\n\n<li>CGM Software GmbH<\/li>\n\n\n\n<li>CHANGING<\/li>\n\n\n\n<li>Chart Art<\/li>\n\n\n\n<li>City of Phoenix<\/li>\n\n\n\n<li>coc00n Cyber Limited<\/li>\n\n\n\n<li>Cognizant Technology Solutions Corp<\/li>\n\n\n\n<li>Coinbase<\/li>\n\n\n\n<li>Corbado<\/li>\n\n\n\n<li>Coretech Knowledge Inc.<\/li>\n\n\n\n<li>Costco Wholesale<\/li>\n\n\n\n<li>CPXI Indonesia<\/li>\n\n\n\n<li>Credenti, LLC<\/li>\n\n\n\n<li>Criticality Sciences<\/li>\n\n\n\n<li>Crossroads Marine Inc<\/li>\n\n\n\n<li>CyberArk<\/li>\n\n\n\n<li>CyberHoot<\/li>\n\n\n\n<li>CyberSolve<\/li>\n\n\n\n<li>Daon<\/li>\n\n\n\n<li>Dashlane<\/li>\n\n\n\n<li>Dapple Security<\/li>\n\n\n\n<li>Datasec Solutions<\/li>\n\n\n\n<li>Deepnet Security<\/li>\n\n\n\n<li>Descope<\/li>\n\n\n\n<li>DLZ Corp<\/li>\n\n\n\n<li>Durkan<\/li>\n\n\n\n<li>DXC Technology<\/li>\n\n\n\n<li>E-CARD ID Products Ltd.<\/li>\n\n\n\n<li>Easy Dynamics Corporation<\/li>\n\n\n\n<li>Egis Technology Inc.<\/li>\n\n\n\n<li>Encore<\/li>\n\n\n\n<li>Equity Clinic<\/li>\n\n\n\n<li>Erciyes University<\/li>\n\n\n\n<li>Eslite Spectrum Corporation<\/li>\n\n\n\n<li>Ethos power<\/li>\n\n\n\n<li>Expert Furnace Solutions, LLC.<\/li>\n\n\n\n<li>Fayetteville State University<\/li>\n\n\n\n<li>FEITIAN Technologies US<\/li>\n\n\n\n<li>Finartz<\/li>\n\n\n\n<li>Footprint<\/li>\n\n\n\n<li>G+D Netcetera<\/li>\n\n\n\n<li>Giesecke+Devrient<\/li>\n\n\n\n<li>Google<\/li>\n\n\n\n<li>GoTrustID Inc.<\/li>\n\n\n\n<li>HIAS<\/li>\n\n\n\n<li>HID Global<\/li>\n<\/ul>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<ul class=\"wp-block-list\">\n<li>Hideez<\/li>\n\n\n\n<li>Hippo<\/li>\n\n\n\n<li>Hirsch<\/li>\n\n\n\n<li>HiTRUST<\/li>\n\n\n\n<li>Holden<\/li>\n\n\n\n<li>Hope College<\/li>\n\n\n\n<li>Houston Methodist Hospital<\/li>\n\n\n\n<li>HubSpot<\/li>\n\n\n\n<li>HYPR<\/li>\n\n\n\n<li>IBM<\/li>\n\n\n\n<li>Icart Cabinetry and Trim<\/li>\n\n\n\n<li>IDEMIA Public Security<\/li>\n\n\n\n<li>Identita Inc.<\/li>\n\n\n\n<li>The Identity Salon<\/li>\n\n\n\n<li>IdentityXP<\/li>\n\n\n\n<li>IDmelon<\/li>\n\n\n\n<li>IEBC<\/li>\n\n\n\n<li>IEEE<\/li>\n\n\n\n<li>Ikea<\/li>\n\n\n\n<li>Imprivata, Inc.<\/li>\n\n\n\n<li>Industrial Technology Research Institute<\/li>\n\n\n\n<li>iNET SYSTEMS INC.<\/li>\n\n\n\n<li>Ingenium Biometric Laboratories<\/li>\n\n\n\n<li>Innokreat Technologies Pvt Ltd<\/li>\n\n\n\n<li>INTEL<\/li>\n\n\n\n<li>International Systems Research<\/li>\n\n\n\n<li>IPCube Co., Ltd.<\/li>\n\n\n\n<li>iProov<\/li>\n\n\n\n<li>James Madison University<\/li>\n\n\n\n<li>JD Construction<\/li>\n\n\n\n<li>John M. Concoran &amp; Co<\/li>\n\n\n\n<li>Johnson University<\/li>\n\n\n\n<li>Juspay<\/li>\n\n\n\n<li>Kaizen Secure Voiz<\/li>\n\n\n\n<li>Key9 Identity<\/li>\n\n\n\n<li>Kirloskar Oil engines Ltd.<\/li>\n\n\n\n<li>KSI Keyboards<\/li>\n\n\n\n<li>Lcjss.com<\/li>\n\n\n\n<li>Leanbic Cybersecurity<\/li>\n\n\n\n<li>Lewis Cass<\/li>\n\n\n\n<li>Liberty University<\/li>\n\n\n\n<li>Long Bay Symphony<\/li>\n\n\n\n<li>LY Corporation<\/li>\n\n\n\n<li>M3CORP<\/li>\n\n\n\n<li>MachSol<\/li>\n\n\n\n<li>Managepoint<\/li>\n\n\n\n<li>Marken<\/li>\n\n\n\n<li>Mastercard<\/li>\n\n\n\n<li>McCarley&#8217;s Home Improvements, LLC<\/li>\n\n\n\n<li>Mercari<\/li>\n\n\n\n<li>Metallicus Inc<\/li>\n\n\n\n<li>Michelin SPA<\/li>\n\n\n\n<li>Microsoft<\/li>\n\n\n\n<li>Modebest Buildersltd<\/li>\n\n\n\n<li>Molina Healthcare<\/li>\n\n\n\n<li>MonoCloud<\/li>\n\n\n\n<li>mSIGNIA<\/li>\n\n\n\n<li>Next Identity<\/li>\n\n\n\n<li>NextTech Communications<\/li>\n\n\n\n<li>Nok Nok<\/li>\n\n\n\n<li>North Central University<\/li>\n\n\n\n<li>Novalytics Limited<\/li>\n\n\n\n<li>Novias K.K.<\/li>\n\n\n\n<li>NTT DOCOMO, INC.<\/li>\n\n\n\n<li>NTT TechnoCross Corporation<\/li>\n\n\n\n<li>Nura<\/li>\n\n\n\n<li>Nymi<\/li>\n\n\n\n<li>Okta<\/li>\n\n\n\n<li>Old Dominion University<\/li>\n\n\n\n<li>OneMoreSecurity Inc<\/li>\n\n\n\n<li>OneSpan<\/li>\n\n\n\n<li>Optimal IdM<\/li>\n\n\n\n<li>Optimity Group Limited<\/li>\n<\/ul>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<ul class=\"wp-block-list\">\n<li>PayPal<\/li>\n\n\n\n<li>PC Systems Ltd<\/li>\n\n\n\n<li>PONE Biometrics AS<\/li>\n\n\n\n<li>Pos Digicert Sdn Bhd<\/li>\n\n\n\n<li>Quorum<\/li>\n\n\n\n<li>Rachis Tech Services Private Limited<\/li>\n\n\n\n<li>Rakuten Group Inc.<\/li>\n\n\n\n<li>Red Alert Labs<\/li>\n\n\n\n<li>Reliable Identities, Inc.<\/li>\n\n\n\n<li>Resilinc Solution&#8217;s pvt Ltd<\/li>\n\n\n\n<li>rf IDEAS<\/li>\n\n\n\n<li>Rosy Roadside Recording<\/li>\n\n\n\n<li>Rote Consulting<\/li>\n\n\n\n<li>RSA<\/li>\n\n\n\n<li>Rublon<\/li>\n\n\n\n<li>Rubycat<\/li>\n\n\n\n<li>Salesforce<\/li>\n\n\n\n<li>Samsung Electronics<\/li>\n\n\n\n<li>Secfense<\/li>\n\n\n\n<li>Secretarium<\/li>\n\n\n\n<li>Serve Aire<\/li>\n\n\n\n<li>SGNL<\/li>\n\n\n\n<li>Simple Software LTDA<\/li>\n\n\n\n<li>Simple, Inc<\/li>\n\n\n\n<li>Smartcontactless<\/li>\n\n\n\n<li>Soft-World International<\/li>\n\n\n\n<li>Solvtify Private Limited<\/li>\n\n\n\n<li>Southeastern Commercial Properties LLC<\/li>\n\n\n\n<li>Spark4<\/li>\n\n\n\n<li>SPLAN, Inc.<\/li>\n\n\n\n<li>Starfish &amp; Co.<\/li>\n\n\n\n<li>Step One Automotive<\/li>\n\n\n\n<li>STMicroelectronics International N.V.<\/li>\n\n\n\n<li>Sunrun<\/li>\n\n\n\n<li>Swissbit<\/li>\n\n\n\n<li>Target Corporation<\/li>\n\n\n\n<li>Technic<\/li>\n\n\n\n<li>Telesign<\/li>\n\n\n\n<li>Texas Department of Public Safety<\/li>\n\n\n\n<li>Thales<\/li>\n\n\n\n<li>The Cloud Coop<\/li>\n\n\n\n<li>The Hill Group<\/li>\n\n\n\n<li>TheCapitalNet Inc.<\/li>\n\n\n\n<li>TikTok<\/li>\n\n\n\n<li>Timothy M Dunn Attorney at Law<\/li>\n\n\n\n<li>TOKEN2<\/li>\n\n\n\n<li>ToothPic<\/li>\n\n\n\n<li>Touch Enterprise Ltd.<\/li>\n\n\n\n<li>TPIsoftware<\/li>\n\n\n\n<li>Transmit Security<\/li>\n\n\n\n<li>Trusona<\/li>\n\n\n\n<li>Turner &amp; Townsend<\/li>\n\n\n\n<li>U.S. Army Corps of Engineers<\/li>\n\n\n\n<li>UKRI<\/li>\n\n\n\n<li>United Healthcare &#8211; Optum<\/li>\n\n\n\n<li>VE3<\/li>\n\n\n\n<li>Verizon Communications<\/li>\n\n\n\n<li>Versasec<\/li>\n\n\n\n<li>VicRoads<\/li>\n\n\n\n<li>Visa<\/li>\n\n\n\n<li>Washington State University<\/li>\n\n\n\n<li>Weave Identity<\/li>\n\n\n\n<li>WebComm Technology Co., Ltd.<\/li>\n\n\n\n<li>Wheelhouse CU<\/li>\n\n\n\n<li>Whirly<\/li>\n\n\n\n<li>Wilmington Home Improvements<\/li>\n\n\n\n<li>Wilson Electric<\/li>\n\n\n\n<li>Windsor<\/li>\n\n\n\n<li>Women in Identity<\/li>\n\n\n\n<li>WSP Group<\/li>\n\n\n\n<li>Yubico<\/li>\n\n\n\n<li>ZeroBiometrics<\/li>\n\n\n\n<li>ZeroVuln, LLC<\/li>\n\n\n\n<li>Zoetis<\/li>\n\n\n\n<li>Zoho Corporation<\/li>\n<\/ul>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>The Passkey Pledge is a voluntary pledge for online service providers and authentication product and service vendors. Individuals are not scoped in the pledge, though are encouraged to voice their [&hellip;]<\/p>\n","protected":false},"author":72,"featured_media":0,"parent":0,"menu_order":33,"comment_status":"open","ping_status":"closed","template":"","meta":{"_acf_changed":true,"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-84416","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/pages\/84416","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\/72"}],"replies":[{"embeddable":true,"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/comments?post=84416"}],"version-history":[{"count":0,"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/pages\/84416\/revisions"}],"wp:attachment":[{"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/media?parent=84416"}],"wp:term":[{"taxonomy":"content-type","embeddable":true,"href":"https:\/\/fidoalliance.org\/wp-json\/wp\/v2\/content-type?post=84416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}