SESSION ID:
#RSAC
William Fisher
IMPROVING MOBILE AUTHENTICATION FOR
PUBLIC SAFETY AND FIRST RESPONDERS
MBS-R02
Security Engineer
National Cybersecurity Center of Excellence
@Billfshr
#RSAC
LET’S TALK ABOUT AUTHENTICATION
Authentication impacts users
Image courtesy of: www.pexels.com
How many of us use Android or iOS devices daily for work?
Image courtesy of: www.pexels.com
How many of our apps require their own passwords?
Need an image for Bio-metrics here
Biometrics help, but…
5am: Please re-enter your password.
Image courtesy of: www.imgflip.com
We know this…
10
Greene, K. K., Gallagher, M. A., Stanton, B. C., Lee, P. Y.: I Can’t Type That! P@$$w0rd Entry on Mobile Devices. In: Human Aspects
of Information, Security, Privacy, and Trust. Lecture Notes in Computer Science, Vol. 8533, pp 160-171. (2014)
What do we get for our troubles?
11
Not much in the way of security…
All tables from the Verizon 2018 DBIR https://www.verizonenterprise.com/verizon-insights-lab/dbir/
Perhaps not all is lost…
What was my
password?
4-8-15-18-23-42?
4-8-15-16-23-48?
Image courtesy of: abc
#RSAC
LETS CONSIDER CONTEXT!
At the office?
Image courtesy of: www.pexels.com
In the shower?
Image courtesy of: www.amazon.com
Driving?
Image courtesy of: www.pexels.com
But, what if you were
trying to do this?
Image courtesy of: www.pexels.com
Or this?
Image courtesy of: www.pexels.com
Or this?
Image courtesy of: Instagram - PCarsenault
I mean,
THIS!
Suddenly, this doesn’t seem so complicated.
Image courtesy of: www.pexels.com
What we really want,
is these folks…
Image courtesy of: Flickr artist Thomas Hawke
…doing more of this…
Filmland: Karl Urban in Dredd 3D
…or this…
Image courtesy of: www.pexels.com
…and less of this.
but wait… we’ll need to account for
these,
Image courtesy of: USAF-E
…and these,
Image courtesy of: www.media.defense.gov
…
…
Image courtesy of: www.spoonuniversity.com
…and these.
Image courtesy of: www.military-media.defense.gov
…and we’re also short on this.
Image courtesy of: www.pexels.com
AND we need to communicate with these,
AND we need to communicate with these,
and these,
AND we need to communicate with these,
and these,
and all of these,
# R S A
C
Requirements:
34
Authentication that is:
Flexible – can handle diverse sets of public safety operational environments
Efficient – can be done quickly during line of duty
Interoperable – promotes cross-jurisdictional informational sharing
“Yeaaa, if you could just
go ahead and audit all of
our user accounts by
Monday that would be
greaaaaat…”
But also…
# R S A
C
Requirements:
36
Authentication that is:
Flexible – can handle diverse sets of public safety operational environments
Efficient – can be done quickly during line of duty
Interoperable – promotes cross-jurisdictional informational sharing
Improve credential and account management:
Mainly by reducing the number of credentials and accounts needed
And finally… Definitely want to
use AES25…hey
bitcoin is over
9000!
# R S A
C
Requirements:
38
Authentication that is:
Flexible – can handle diverse sets of public safety operational environments
Efficient – can be done quickly during line of duty
Interoperable – promotes cross-jurisdictional informational sharing
Improve credential and account management:
Mainly by reducing the number of credentials and accounts needed
Get mobile application developers out of:
Developing custom authentication solutions
Managing users accounts and directory services
Filler Text / Question / Statement
Save
the
world! Image courtesy of: www.pexels.com
Accelerate adoption of secure technologies:
collaborate with innovators to provide real-
world, standards-based cybersecurity
capabilities that address business needs
NIST Public Safety Communication Research Lab (PSCR) is the primary federal
laboratory conducting research, development, testing, and evaluation for
public safety communications technologies
#RSAC
WHAT WE BUILT?
Using standards of course!
# R S A
C
NCCoE Benefits – Standards-Based
43
NCCoE solutions implement standards and best practices:
Using modern commercially available technology:
# R S A
C
44
Core Capabilities
p@$$w0rd +
Multifactor Authentication (MFA) to Mobile Resources
• Biometrics, external hardware authenticators and other
authentication options
Single Sign-on (SSO) to Mobile Resources
• Authenticate once with mobile native app or web apps
• Leverage initial MFA when accessing multiple applications
Identity Federation
• Leverage directory services already in place
• Send identities across jurisdictional boundaries
#RSAC
AUTHENTICATION & SINGLE SIGN-ON DEMO
“don’t tell me, show me!”
# R S A
C
Demo – What you’ll see, MFA + SSO
46
FIDO UAF Authentication
Leverages fingerprint registered to device
No Password Input
FIDO U2F Authentication
Using FIDO key as second factor
Private key pair on the device
Mobile App Single Sign-On
Access to mapping and chat apps without need to re-authenticate
Implements IETF RFC 8252 for SSO on Native Mobile Apps
p1n +
+
Private Key Biometric
# R S A
C
Demo – What you’ll won’t see, federation
47
Identity Federation
We have examples identity federation using both SAML 2.0 and OpenID
Connection 1.0
But as with all federation its “under the hood”
#RSAC
SOLUTION BENEFITS
“is This Good for the COMPANY?”
# R S A
C
Remember password management
challenge?
49
Reduces:
The amount of authentication time and attempts for PSFR personnel
The number of credentials that PSFR personnel and organizations need to
manage
Requirements for complex passwords
# R S A
C
Standards help!
50
Increases:
Interoperability through the use of open, standards-based architecture
—Identity providers can leverage their current active directory
Authenticator flexibility through the FIDO ecosystem
—External hardware authenticators, biometrics, etc…
# R S A
C
Standards based MFA
51
FIDO:
Multifactor authentication in line with NIST 800-63-3 Requirements
No secrets (private keys or biometric templates) are stored server-side
— “verifier compromise resistance”
Phishing resistance
# R S A
C
Standards-Based SSO
52
IETF BCP for Mobile SSO:
User's password and other credentials are never exposed to the SaaS
provider or mobile app
Apps get an OAuth Token with limited scope of authorization - apps only
get access to back-end systems they should be accessing
Reduced number of credentials decreased risk of credential re-use
# R S A
C
53
AppAuth Software Development Kit
Implementation of the “OAuth 2.0 for Native Apps” RFC
Free and open source on GitHub – developed by Google and given to OpenID
Developers can “Drag and Drop” into a mobile app
Oh by the way… its easy for developers
#RSAC
NEW NIST GUIDANCE!
“yes but how?”
# R S A
C
NIST SP 1800-13 out now for public
comment!
55
• NIST Cybersecurity Practice Guide SP 1800-13 includes:
Technical Decisions
Trade-offs
Lessons Learned
Build Instructions
Functional Tests
# R S A
C
Take-aways?
56
1. Everyone, download SP 1800 -13, Available Now!
2. Developers, implement standards-based SSO with AppAuth!
3. Check out the FIDO vendors on the RSA exhibit floor
# R S A
C
References
57
SP 1800-13: https://www.nccoe.nist.gov/projects/use-cases/mobile-sso
IETF RFC 8252: https://tools.ietf.org/html/rfc8252
AppAuth: https://github.com/openid/AppAuth-Android
FIDO: https://fidoalliance.org/about/what-is-fido/
# R S A
C
Any questions?
58
William Fisher, Security Engineer
Email: William.Fisher@nist.gov
Project Updates: https://nccoe.nist.gov/projects/use-cases/mobile-sso

Improving Mobile Authentication for Public Safety and First Responders

  • 1.
    SESSION ID: #RSAC William Fisher IMPROVINGMOBILE AUTHENTICATION FOR PUBLIC SAFETY AND FIRST RESPONDERS MBS-R02 Security Engineer National Cybersecurity Center of Excellence @Billfshr
  • 2.
  • 3.
    Authentication impacts users Imagecourtesy of: www.pexels.com
  • 4.
    How many ofus use Android or iOS devices daily for work? Image courtesy of: www.pexels.com
  • 5.
    How many ofour apps require their own passwords?
  • 6.
    Need an imagefor Bio-metrics here Biometrics help, but…
  • 7.
    5am: Please re-enteryour password. Image courtesy of: www.imgflip.com
  • 10.
    We know this… 10 Greene,K. K., Gallagher, M. A., Stanton, B. C., Lee, P. Y.: I Can’t Type That! P@$$w0rd Entry on Mobile Devices. In: Human Aspects of Information, Security, Privacy, and Trust. Lecture Notes in Computer Science, Vol. 8533, pp 160-171. (2014)
  • 11.
    What do weget for our troubles? 11 Not much in the way of security… All tables from the Verizon 2018 DBIR https://www.verizonenterprise.com/verizon-insights-lab/dbir/
  • 12.
    Perhaps not allis lost… What was my password? 4-8-15-18-23-42? 4-8-15-16-23-48? Image courtesy of: abc
  • 13.
  • 14.
    At the office? Imagecourtesy of: www.pexels.com
  • 15.
    In the shower? Imagecourtesy of: www.amazon.com
  • 16.
  • 17.
    But, what ifyou were trying to do this? Image courtesy of: www.pexels.com
  • 18.
    Or this? Image courtesyof: www.pexels.com
  • 19.
    Or this? Image courtesyof: Instagram - PCarsenault
  • 20.
  • 21.
    Suddenly, this doesn’tseem so complicated. Image courtesy of: www.pexels.com
  • 22.
    What we reallywant, is these folks… Image courtesy of: Flickr artist Thomas Hawke
  • 23.
    …doing more ofthis… Filmland: Karl Urban in Dredd 3D
  • 24.
    …or this… Image courtesyof: www.pexels.com
  • 25.
  • 26.
    but wait… we’llneed to account for these, Image courtesy of: USAF-E
  • 27.
    …and these, Image courtesyof: www.media.defense.gov
  • 28.
    … … Image courtesy of:www.spoonuniversity.com
  • 29.
    …and these. Image courtesyof: www.military-media.defense.gov
  • 30.
    …and we’re alsoshort on this. Image courtesy of: www.pexels.com
  • 31.
    AND we needto communicate with these,
  • 32.
    AND we needto communicate with these, and these,
  • 33.
    AND we needto communicate with these, and these, and all of these,
  • 34.
    # R SA C Requirements: 34 Authentication that is: Flexible – can handle diverse sets of public safety operational environments Efficient – can be done quickly during line of duty Interoperable – promotes cross-jurisdictional informational sharing
  • 35.
    “Yeaaa, if youcould just go ahead and audit all of our user accounts by Monday that would be greaaaaat…” But also…
  • 36.
    # R SA C Requirements: 36 Authentication that is: Flexible – can handle diverse sets of public safety operational environments Efficient – can be done quickly during line of duty Interoperable – promotes cross-jurisdictional informational sharing Improve credential and account management: Mainly by reducing the number of credentials and accounts needed
  • 37.
    And finally… Definitelywant to use AES25…hey bitcoin is over 9000!
  • 38.
    # R SA C Requirements: 38 Authentication that is: Flexible – can handle diverse sets of public safety operational environments Efficient – can be done quickly during line of duty Interoperable – promotes cross-jurisdictional informational sharing Improve credential and account management: Mainly by reducing the number of credentials and accounts needed Get mobile application developers out of: Developing custom authentication solutions Managing users accounts and directory services
  • 39.
    Filler Text /Question / Statement Save the world! Image courtesy of: www.pexels.com
  • 40.
    Accelerate adoption ofsecure technologies: collaborate with innovators to provide real- world, standards-based cybersecurity capabilities that address business needs
  • 41.
    NIST Public SafetyCommunication Research Lab (PSCR) is the primary federal laboratory conducting research, development, testing, and evaluation for public safety communications technologies
  • 42.
    #RSAC WHAT WE BUILT? Usingstandards of course!
  • 43.
    # R SA C NCCoE Benefits – Standards-Based 43 NCCoE solutions implement standards and best practices: Using modern commercially available technology:
  • 44.
    # R SA C 44 Core Capabilities p@$$w0rd + Multifactor Authentication (MFA) to Mobile Resources • Biometrics, external hardware authenticators and other authentication options Single Sign-on (SSO) to Mobile Resources • Authenticate once with mobile native app or web apps • Leverage initial MFA when accessing multiple applications Identity Federation • Leverage directory services already in place • Send identities across jurisdictional boundaries
  • 45.
    #RSAC AUTHENTICATION & SINGLESIGN-ON DEMO “don’t tell me, show me!”
  • 46.
    # R SA C Demo – What you’ll see, MFA + SSO 46 FIDO UAF Authentication Leverages fingerprint registered to device No Password Input FIDO U2F Authentication Using FIDO key as second factor Private key pair on the device Mobile App Single Sign-On Access to mapping and chat apps without need to re-authenticate Implements IETF RFC 8252 for SSO on Native Mobile Apps p1n + + Private Key Biometric
  • 47.
    # R SA C Demo – What you’ll won’t see, federation 47 Identity Federation We have examples identity federation using both SAML 2.0 and OpenID Connection 1.0 But as with all federation its “under the hood”
  • 48.
    #RSAC SOLUTION BENEFITS “is ThisGood for the COMPANY?”
  • 49.
    # R SA C Remember password management challenge? 49 Reduces: The amount of authentication time and attempts for PSFR personnel The number of credentials that PSFR personnel and organizations need to manage Requirements for complex passwords
  • 50.
    # R SA C Standards help! 50 Increases: Interoperability through the use of open, standards-based architecture —Identity providers can leverage their current active directory Authenticator flexibility through the FIDO ecosystem —External hardware authenticators, biometrics, etc…
  • 51.
    # R SA C Standards based MFA 51 FIDO: Multifactor authentication in line with NIST 800-63-3 Requirements No secrets (private keys or biometric templates) are stored server-side — “verifier compromise resistance” Phishing resistance
  • 52.
    # R SA C Standards-Based SSO 52 IETF BCP for Mobile SSO: User's password and other credentials are never exposed to the SaaS provider or mobile app Apps get an OAuth Token with limited scope of authorization - apps only get access to back-end systems they should be accessing Reduced number of credentials decreased risk of credential re-use
  • 53.
    # R SA C 53 AppAuth Software Development Kit Implementation of the “OAuth 2.0 for Native Apps” RFC Free and open source on GitHub – developed by Google and given to OpenID Developers can “Drag and Drop” into a mobile app Oh by the way… its easy for developers
  • 54.
  • 55.
    # R SA C NIST SP 1800-13 out now for public comment! 55 • NIST Cybersecurity Practice Guide SP 1800-13 includes: Technical Decisions Trade-offs Lessons Learned Build Instructions Functional Tests
  • 56.
    # R SA C Take-aways? 56 1. Everyone, download SP 1800 -13, Available Now! 2. Developers, implement standards-based SSO with AppAuth! 3. Check out the FIDO vendors on the RSA exhibit floor
  • 57.
    # R SA C References 57 SP 1800-13: https://www.nccoe.nist.gov/projects/use-cases/mobile-sso IETF RFC 8252: https://tools.ietf.org/html/rfc8252 AppAuth: https://github.com/openid/AppAuth-Android FIDO: https://fidoalliance.org/about/what-is-fido/
  • 58.
    # R SA C Any questions? 58 William Fisher, Security Engineer Email: William.Fisher@nist.gov Project Updates: https://nccoe.nist.gov/projects/use-cases/mobile-sso