How US government can go mobile with FIDO
13 April 2016 09:45 GMT

By Brett McDowell, Executive Director, FIDO Alliance, USA
and 
Paul Grassi, Senior Standards and Technology Advisor, National Institute for Standards and Technology (NIST), USA

The proliferation of mobile devices leaves U.S. government agencies with a tough balancing act between security, usability and effectively performing their missions. How can they accommodate an increasingly mobile workforce that wants to use all of their devices to access online services, while adhering to a plethora of security policies and directives?

To address this challenge, agencies should first consider strong authentication techniques to secure online services. The Office of Management and Budget (OMB) and the National Institute of Standards and Technology (NIST) have provided agencies options, such as derived PIV credentials (guidelines for which are outlined in NIST SP 800-157), which allow the storage of PKI credentials based on having a PIV smartcard on users’ mobile devices, giving them more options to access critical apps and information.

However, deployment of better mobile authentication options has not matched demand. We still aren’t seeing wide deployment of derived PIV credentials; agencies are still looking at many different options for enabling mobile application access. In addition, the U.S. government has not consistently adopted the biometric capabilities built into most mobile device platforms as the private sector has.

There’s good news for government – FIDO authentication standards, and the devices with FIDO capability built-in, can help them go mobile while staying secure and adhering to relevant standards.

Going mobile with FIDO: Better usability, security and privacy

The FIDO Alliance is improving online authentication by developing open, interoperable industry specifications that leverage device-based user verification for better usability and proven public key cryptography for stronger security. With FIDO, agencies don’t have to sacrifice usability and efficiency to obtain strong authentication for mobile access to online services.

For better usability, FIDO standards support a range of interoperable authentication factors and modalities, including biometrics built into many mobile devices today for strong authentication. For example, with FIDO, the user need only touch something (fingerprint sensor) or look at something (iris or facial recognition) on their mobile device to access apps and data securely. While these examples use biometrics, there are other non-biometric modalities supported that are still interoperable – such as a security token using Near Field Communication (NFC) – should a portion of the workforce not choose a biometric option.

There is already a rich set of products ready for FIDO deployment – more than 100 products have been tested and FIDO certified from over 50 different companies, including leading mobile device manufacturers such as Samsung, Lenovo, Sony and LG. This is thanks to the FIDO certification program, which ensures different FIDO implementations interoperate with each other on a technical level, and that the technical specifications are adhered to.

To match the usability with the required strong authentication needed in government, FIDO standards utilize industry standard, tested and vetted cryptographic algorithms and security mechanisms in significant use by the public and private sectors. With FIDO, you can achieve the security benefits of public key cryptography without the traditional and costly certificate authority (CA) model. In other words, it’s public key without the ‘infrastructure’. Additionally, if a biometric authenticator is your choice, rest assured, FIDO mandates that the biometric NEVER leaves the device, increasing privacy and security by effectively limiting the chance of a massive breach of credentials.

How FIDO Registration Works

Registration:

·         User is prompted to choose an available FIDO authenticator that matches the online service’s acceptance policy.

·         User unlocks the FIDO authenticator using a fingerprint reader, a button on a second-factor device, securely-entered PIN or other method.

·         User’s device creates a new public/private key pair unique for the local device, online service and user’s account.

·         Public key is sent to the online service and associated with the user’s account. The private key and any information about the local authentication method (such as biometric measurements or templates) never leave the local device.

How FIDO Fits in: Government Use Cases

FIDO is a strong option for any use case in which government agencies need to provide simple, fast and secure multi-factor, mobile-based authentication to digital services. Some opportunities in federal and local governments for access to government applications include:

●        Derived PIV credentials;

●        Public safety and first responder credentials;

●        Emergency communications personnel credentials;

●        International partner credentials;

●        Business partner credentials;

●        Citizen or beneficiary access to government services;

●        Credentials for contractors and employees that aren’t eligible for a PIV but need secure access to online services;

●        Physical access control applications, i.e. using FIDO along with NFC on a mobile device.

FIDO can provide the necessary usability, security, privacy and utility for all of these use cases, while helping government agencies meet security policies and directives including:

OMB M-04-04. FIDO specifications can be implemented on platforms that support all of the levels of assurance defined in OMB M-04-04. FIDO provides one unified specification; government agencies can support FIDO-based authenticators across a range of levels of assurance (LOA) while deploying a single server-side infrastructure that supports any client-side device.

NIST SP 800-63-2 Electronic Authentication Guidelines. With FIDO, agencies can comply with a host of token types defined in 800-63-2. In addition, FIDO authenticators meet the biometric requirements of the NIST 800-63-2 Electronic Authentication Guidelines because FIDO credentials are used locally only to unlock a strong cryptographic key, and the biometric sample and template never leave the device.

NIST SP 800-157 Guidelines for Derived Personal Identity Verification (PIV) Credentials. FIDO authentication standards meet most of the technical requirements of NIST 800-157, and the workflow specified in 800-157 does not need to be modified to support a FIDO-compliant derived PIV credential. The only difference between a FIDO-compliant solution and the specifications within SP 800-157 is the usage of PKI.

Looking deeper at FIDO for derived PIV credentials, most of the challenges associated with such a deployment will be associated with business process, not technology. Specifically, agencies will need to define workflow that allows a user to associate a FIDO authenticator, specifically the public/private key pair, to their enterprise digital identity – just like they would for a PKI certificate. Due to the way that FIDO creates public/private key pairs in support of privacy, the agency would need to invoke the key generation process as part of an overarching identity solution to ensure the public key is used for all FIDO-compliant applications, e.g. mobile applications.

In this example, the issuing entity would serve as the identity provider and the public key would need to be registered with the digital identity record of the user. From that point on, the user can use the FIDO derived PIV credential. With this type of approach, a FIDO derived PIV credential can operate in parallel and with no disruption to existing PIV- and PKI-based solutions.                                                                                                                                                             

FIDO for citizens, too

FIDO’s combination of usability, security and privacy also makes it a good option for citizen access to government online services. For citizen-facing services, EO 13681 requires agencies that make personal data available online to utilize two-factor authentication. With FIDO, agencies can meet this requirement by allowing citizens to “bring their own authenticator,” thus allowing them to use their FIDO-compliant mobile device or desktop browser to simply and strongly authenticate themselves to government services such as filing taxes, managing social security benefits, applying for student loans or submitting health insurance claims. This is not only a win for the citizen – they use what they like and already have to securely authenticate to government services. This is a win for the government too, as they don’t need to issue specialized credentials just to offer secure, privacy-enhancing multi-factor authentication for the services they provide.

Conclusion

For agencies looking to optimize security, usability, privacy, and effectively performing their missions, deploying mobile authentication for access to online services can be achieved without reinventing the wheel. FIDO’s open, interoperable industry specifications can help them obtain the best of all worlds – device-based user authentication for better usability and proven public key cryptography for stronger security and privacy.

Note:

This article was originally published in the connectID 2016 event guide.