IBM Security Access Manager (ISAM)

IBM Mobile Security
Secure mobile interactions with risk-based
access control
Jason Keenaghan
Program Director, Offering Management
IAM & z Systems Security
Scott Exton
Chief Programmer
IBM Security Access Manager (ISAM)
September 25, 2015
© 2015 IBM Corporation
Agenda
 Introduction to the IBM Mobile Security Framework
 Scenarios: Adopting a risk-based security posture for mobile access management
 Demos: IBM Security Access Manager (ISAM) for mobile workloads
 Open discussion, Q & A
© 2015 IBM Corporation
2
IBM Mobile Security Framework
Protect
Devices
• Manage multi-OS BYOD
environment
Secure Content
and Collaboration
• Separate enterprise and
personal data
Safeguard
Applications and Data
• Distribute and control
enterprise apps
MobileFirst
• Mitigate risks
of lost and
compromised
devices
Protect (MaaS360)
AppScan,
M; secure apps and
• Enforce
complianceArxan,
with Trusteer
• Build and
security policies bile SDK
protect them
“in the wild”
AirWatch, MobileIron, Good,
HP Fortify, Veracode, Proguard
Citrix, Microsoft, Mocana
Extend Security Intelligence
Manage Access
and Fraud
• Provide secure web,
mobile, API access and
identify device risk
• Meet authentication easeof-use expectation
CA, Oracle, RSA
• Extend security information and event management (SIEM) to mobile platform
• Incorporate mobile log management, anomaly detection, configuration and vulnerability management
© 2015 IBM Corporation
3
Executing a strategy with IBM Mobile Security
IBM
MobileFirst
Protect
MaaS360
IBM
Security
Trusteer
IBM
Security
AppScan
IBM Security
Access
Manager
IBM
QRadar
Security
Intelligence
Platform
Arxan
Application
Protection
for IBM
Solutions
IBM
Mobile
Security
Services
IBM
MobileFirst
Platform
IBM
BigFix
IBM
DataPower
Gateway
© 2015 IBM Corporation
4
Agenda
 Introduction to the IBM Mobile Security Framework
 Scenarios: Adopting a risk-based security posture for mobile access management
 Demos: IBM Security Access Manager (ISAM) for mobile workloads
 Open discussion, Q & A
© 2015 IBM Corporation
5
Take back control of Access Management
Consumers
Employees
Partners &
Contractors
ISAM
Enterprise Applications
Cloud Workloads
SaaS Applications
© 2015 IBM Corporation
6
Adopt a graded trust posture to help achieve secure
transactions & risk-based enforcement
Security Team
Manage consistent
security policies
Consumers
Application
Team
Consumer / Employee
Applications
On/Off-premise
Resources
Internet
Employees
BYOD
Access Management
Fraud & Threat-aware application access across multiple channels
Strong Authentication, SSO, session management for secure
B2E, B2B and B2C use cases
Context-based access and stronger assurance for transactions
from partners and consumers
Applications
Data
Cloud
Mobile
Transparently enforce security access
policies for web and mobile applications
Enforce security access polices without
modifying the applications
© 2015 IBM Corporation
7
IBM Security Access Manager supports five main context
domains for risk-based access control
Endpoints:
There are various unique attributes (device fingerprint).
Screen depth/resolution, Fonts, OS, Browser, Browser plug-in, device model & UUID
Identity:
Groups, roles, credential attributes, organization
Environment:
Geographic location, network, local time . . . etc
Resource / Action:
The application being requested and what is being done.
Behavior:
Analytics of user historical and current resource usage.
User activity monitoring, specific business activity monitoring
© 2015 IBM Corporation
8
What are some use cases for strong / context-aware access?
 Improved end user experience:
– Eliminate usernames and passwords for mobile
devices users
– Situation awareness and graded trust
 Stronger mechanisms of validating an identity for
improved assurance
– Biometrics, touchID
– Multi-factor authentication
– Support FIO alliance
 Adoption of Mobile
– Secure mobile devices / transactions
– Use mobile device for authentication
– Out of band authentication (push notification)
 Step-up authentication for additional identity
assurance:
– Unknown device, high-risk or infected device
– High-value transactions
 Transaction validation
– Support 3D Secure
– Mandated by federal regulations
 Risk-elevation factors:
– IP reputation, Geo-political location
– Behavioral anomalies (e.g., time of day)
 Continuous authentication:
– Soft biometrics / behavioral biometrics
– User presence detection (e.g., motion)
© 2015 IBM Corporation
9
IBM architecture for risk-based access with strong authentication
Easy to deploy, easy to manage, and highly scalable virtual and physical appliances
SSO / FSSO / Context based Access
User on Mobile
or Desktop
PEP
Mobile
Client
Applications and Data
Policy Server (PAP)
Context
Access Policy Authoring
ISAM
ISAM
Proxy
Or
Data
Power
(PEP)
Runtime Services (PDP)
Risk Engine
Extensible Context
Authentication
Framework
Extensible Authentication & Verification Methods
Extensible Multi-modal Authentication
© 2015 IBM Corporation
10
Simplify fraud protection
Automatically protect users and organizations from fraud with strong authentication
Fraud and
Access Context
Fraud Context
and Risk Score
ISAM
Users
QRadar
Security
Intelligence
Protected
Applications
 Risk-based access controls built around malware and fraud risk score from Trusteer
– High risk transactions can be prompted to change behavior (e.g. open secure browser) or
perform step-up authentication
 ISAM adds Trusteer fraud protection to applications without requiring any code
changes on the protected applications themselves
© 2015 IBM Corporation
11
Remove barriers to mobile productivity
Enable more convenient and secure access to enterprise resources from mobile
MaaS360 App
Username
User
Authenticates
to MaaS360
Password
MaaS360-enabled
enterprise mobile apps
SaaS Applications
Single Sign-on
Sign In
ISAM
Enterprise Web
Applications
 Allows users to easily access enterprise resources with minimal authentication
friction
 Utilizes existing access management infrastructure to prevent the need for
application changes while enabling access from mobile devices
 Risk-based access controls can utilize context from MaaS360 in access decision
(e.g., compliance state, jail broken status, ownership status, etc.)
© 2015 IBM Corporation
12
Implementation pattern for providing advanced API security
DataPower is the API Gateway for IBM API Management to secure & integrate API traffic
 IBM API Management provides developer portal, API analytics, and development acceleration for
ISAM integration on DataPower Gateway appliances
 IBM DataPower Gateway provides API runtime policy enforcement point and integration to other
dynamic decision engines (e.g., ISAM)
 IBM Security Access Manager provides advanced mobile/API security capabilities for enhanced
protection of API resources.
DMZ
Internet
Trusted Zone
Define Policies
1
APIm
Consult Decision Engine
3
Invoke API
2
Mobile
Application
ISAM
ISAM Module
DataPower
“API Gateway”
4
Invoke Backend
Service
IBM
MobileFirst
© 2015 IBM Corporation
13
Agenda
 Introduction to the IBM Mobile Security Framework
 Scenarios: Adopting a risk-based security posture for mobile access management
 Demos: IBM Security Access Manager (ISAM) for mobile workloads
 Open discussion, Q & A
© 2015 IBM Corporation
14
Agenda
 Introduction to the IBM Mobile Security Framework
 Scenarios: Adopting a risk-based security posture for mobile access management
 Demos: IBM Security Access Manager (ISAM) for mobile workloads
 Open discussion, Q & A
© 2015 IBM Corporation
15
What is important to you when you think of mobile security?
 How do you deliver user access security for mobile applications in your organization?
 What are your major security concerns when launching new mobile applications?
 Do you have different solution requirements for internal users (employees, contractors) vs.
external users (consumers, business partners)?
 Do you use an Enterprise Mobility Management (EMM) or Mobile Device Management
(MDM) solution today? How well does it integrate with your IAM solutions?
 Are you using mobile apps from 3rd party vendors or SaaS providers? If so, are there any
unique security or user experience challenges that these introduce?
© 2015 IBM Corporation
16
Statement of Good Security Practices: IT system security involves protecting systems and information through prevention, detection and response to improper access from within and outside
your enterprise. Improper access can result in information being altered, destroyed, misappropriated or misused or can result in damage to or misuse of your systems, including for use in attacks
on others. No IT system or product should be considered completely secure and no single product, service or security measure can be completely effective in preventing improper use or access.
IBM systems, products and services are designed to be part of a lawful, comprehensive security approach, which will necessarily involve additional operational procedures, and may require other
systems, products or services to be most effective. IBM DOES NOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES ARE IMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE
IMMUNE FROM, THE MALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY.
THANK YOU
www.ibm.com/security
© Copyright IBM Corporation 2015. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any
kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor
shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use
of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and / or
capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product
or feature availability in any way. IBM, the IBM logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries
or both. Other company, product, or service names may be trademarks or service marks of others.