Why do we use mobile devices? Simple – they’re easy to use and very convenient. So, why do we make it so hard for mobile consumers to do business with us by confronting them with multiple login screens and passwords? While security is essential to protecting mobile usage, convenience cannot be sacrificed.
With the release of the CA Layer 7 Mobile Access Gateway 2.0 and its Mobile SDK, organizations can now achieve faster mobile consumer engagement, end-to-end mobile app security and convenient mobile Single Sign-On (SSO). In this webinar, Tyson Whitten and Leif Bildoy of CA Technologies explore the why and how of mobile SSO and the Mobile Access Gateway.
You will learn
• The mobile app choices you need to make to enable better consumer engagement
• The connectivity and security implications of these choices
• The mobile security solutions that balance security and convenience
ICT role in 21st century education and its challenges
Mobile SSO: Give App Users a Break from Typing Passwords
1. Mobile SSO: Give App Users a
Break from Typing Passwords
September 19th 2013
Tyson Whitten
Director, Mobile Solutions Marketing
CA Technologies
Leif Bildoy
Sr. Security Product Manager
CA Technologies
9. Different mobile apps require different security solutions
Web API
Custom App COTS AppWeb Browser
3rd Party
10. Different mobile apps require different security solutions
Web API
Custom App COTS AppWeb Browser
3rd Party
• Access Management
• Federation
• API Security/Management
• SDK: Advanced Auth, SSO
• App Wrapping
11. App Wrapping
End-to-end Mobile Security
Web
API
Identity / Device
Management
Adaptation
Optimize
Traffic
Protect
Data
Notification
Services
Centralized
Security Policy
Mobile SDK
Web Access
Enterprise
App Store
Browser
COTS Mobile
Apps
Custom Mobile
Apps Developer
Portal
13. Who’s involved in a new mobile app project?
App DevelopersEnterprise Architect
Information Security
Chief Mobility Officer
Product Manager
How does it
fit into my
mobile
strategy?
How will it
enable better
customer
engagement?
How will it
create a
great user
experience?
How will it
connect to
my
enterprise
data?
How will it
expose my
enterprise
data?
14. The challenges - how do you bridge the gap?
Security
- Control access to assets
- Focus on restricting access
- Don’t understand app dev requirements
App Development
- Get to market quickly
- Measured on number of downloads
- Security is something that obstructs UX
- Speed vs. stability?
User Experience
- Improve user app experience
- Don’t have time for evolving security standards
17. How are APIs fundamental to enabling a convenient app experience?
18. The MAG SDK Section
Backend Security
Mobile Apps
Internet of Things
Developer Community
19. Mobile API Security and Management
Backend Security
API Management at Edge of Network
DMZ deployment
Hardware appliance, virtual appliance or
software
Enterprise
Network
API/Service
Servers
…
Firewall 2
Firewall 1
Partners
Mobile Devices
Cloud
API/Service
Client
Directory
21. The Essence of the Problem:
Secure Mobile Access to Apps and Data
How Do We Make APIs Available?
Firewall mazes
Diversity of clients and back end systems
Clients and servers change at different
rates
Enterprise
Network
API/Service
Client
API/Service
Servers
Firewall 2
Firewall 1
Internet
Directory
Of Particular Interest:
Authentication, Authorization & SSO
Secure Transmission
22. We Want Classic SSO In An Active Profile For REST
Could leverage WS-Fed here
SAML’s second act?
API/Service
Servers
Apps making
RESTful API
calls
Internet
Directory
23. But We Also Want Local App SSO
Single Sign On App Group
(these apps will share sign-
on sessions)
A B C
API/Service
Servers
So now it’s getting
interesting…
Like a VPN… but with a better experience
25. Solution: MAG+SDK for end-to-end mobile app security and management
Enterprise
Network
iPhone
Android
iPad
API Servers
Optional Client Component
iOS and Android libraries to simplify
secure access
CA Layer 7 Gateway at Network Edge
Server-side security and API management
Optimized for mobile use cases
26. Native Single Sign-On SDK For Mobile Developers
Enterprise
Network
iPhone
Android
iPad
App-sharable Secure
Key Store
One time PIN
SMS, APNS, call
API Servers
Strong Security for Mobile Apps
Cross-platform and built for a consumer or BYOD world
100% Standards-based using OAuth+OpenID Connect
X-app SSO with multi-factor auth & secure channel
X.509 Certificate provisioning for strong auth and transaction signing
27. Client Deployment Strategy
— Don’t make me work hard
− But give me a strong and extensible security model
— Transfer of security responsibility
− Let developers do what they do best
— Simple SDK
− Align with common development time environments
• iOS, Android, Javascript, etc
— Mirror REST frameworks
— Future
− Aspects, wrapping, etc.
31. Protocol Strategy
A B C
username/password
ID Token
Access Token/Refresh Token
Per app
Authorization
Server
OAuth + OpenID Connect + PKI
Profiled for mobile
Clear distinction between device, user and app
MAG
Signed Cert
Certificate Signing
Request
33. Mobile SDK Benefits
— Single Sign-On for Mobile apps
− Simplified & Consistent UX across all
Enterprise apps
− Remove password typing on devices (as
much as possible)
− No insecure browser redirects
− Will leverage advanced auth schemes in
the future
— Secure Transport
− Configure mutual SSL for API calls help
ensure apps use secure access to
enterprise data
— PKI Provisioning
− Keys available for 2-factor auth or
transaction signing
— Easy to use SSO admin console
− SSO Admin console allowing easy
configuration and management of Users,
Apps, and Devices
− SSO Self Service portal – providing a
simple UI where Users can manage their
enterprise app entitlements and token
sharing
— Improved Developer experience
− Simple device API for apps to participate in
SSO session & decorate API calls with
appropriate security mechanism
− Easily benefit from cryptographic-based
security leveraging standards OAuth,
OpenID Connect, JWT and PKI
34. Mobile Access Gateway 2.0
•Surface legacy data source as RESTful APIs
•XML and JSON transforms
•Recompose & virtualize APIs to specific mobile
identities, apps and devices
•Orchestrate API mashups with configurable workflow
Adaptation: Translate & Orchestrate Data
& APIs
•Cache calls to backend applications
•Aggregated mobile requests
•Compress traffic to reduce bandwidth costs and
improve user experience
•Pre-fetch content for hypermedia-based API calls
Optimization: Handle Scale
• Protect REST and SOAP APIs against DoS and API attacks
• Proxy API streaming protocols like HTML5 Websocket
and XMPP messaging
• Enforce FIPS 140-2 grade data privacy and integrity
• Validate data exchanges, including all JSON, XML,
header and parameter content
Security: Mobile Application Firewalling
• Apple Push Notifications Service
• Android Cloud to Device Messaging Framework
• Proxy and manage app interactions with social networks
Integration: Centralize Cloud Connectivity
•Mobile SSO
•Multi-layered security
•Granular access policies at user, app and device levels
•OAuth 2.0
•OpenID Connect
Identity: Extending Enterprise Identity to Mobile
35. When is the Mobile Access Gateway relevant?
Are you:
- exposing backend APIs?
- writing mobile apps that consume the exposed APIs?
- requiring mobile SSO for enterprise apps?
- requiring mutual SSL for secure consumption of APIs?
- integrating cloud services into mobile apps?
- integrating backend or legacy data into mobile apps?
- requiring location-based access control?