SMP Security & Identity Management An Introduction

Transcription

1 SMP Security & Identity Management An Introduction SMP Enterprise Grade Mobility Webinar Series Brought to you by the SAP Mobile Rapid Innovation Group (RIG)

2 SAP Mobile Platform: Enterprise Grade Mobility On SCN pages and a series of webinars, we drill down into Enterprise Readiness aspects of the SAP Mobile Platform (SMP). On the SCN Pages, you find links to White Papers, How-To Guides, Blogs and other resources. Webinars complement these published resources. The Webinar schedule is also published on SCN SAP AG. All rights reserved. Public 2

3 Security & Identity Management - Introduction SMP Enterprise Grade Mobility Webinar Series Dirk Olderdissen, Regional Mobility Presales, EMEA July, 2013

4 Agenda 1. SMP Security Overview 2. Transport Security 3. SMP Application Identification 4. Server Security Configuration 5. DMZ Security 6. Client Security 2013 SAP AG. All rights reserved. Public 4

5 SMP Security Overview

6 Platform security elements SMP 1 Transport Security X SAP Afaria 2 Application Security X X (partial) 3 Platform Security Authentication Backend Security 4 DMZ Security X 5 Device Security X X Backend Backend 3 SAP Mobile Platform Application Layer Communication Layer D M Z 4 SMPTraffic 1 SMP Application Application Layer Communication Layer SAP AG. All rights reserved. Public 6

7 SMP Data transport encryption The SMP client traffic can be encrypted. Most SMP protocols are actually already encrypted out of the box. When encryption is configured, the encryption is established before data is sent to the mobile device. The encryption type and details depend on the respective protocols that are being used. SMP Application SMP Server 2013 SAP AG. All rights reserved. Public 7

8 SMP app ID check SMP applications* need to present a valid app ID The app ID is created during the app enrolment process The app presents this ID on every connection with the SMP server The App ID is checked on the SMP server for validity The ID allows the SMP Server to uniquely identify each App on any particular device (for security + management + data handling) SMP Application ID ID SMP Server * HTTP Rest API application connection ID is optional 2013 SAP AG. All rights reserved. Public 8

9 Authentication The app needs to authenticate against SMP and against the backend The app needs to present credentials for authentication The required credentials are configurable The authentication is a two tier authentication o o First tier for SMP Second tier for the Data Source SMP Server U SMP U1 U2 EIS Application 2013 SAP AG. All rights reserved. Public 9

10 SMP communication process overview U1 U2 ID ID U1 SMP DB Auth U2 EIS Auth Steps taken before any data is sent to the mobile application 1. Transport Encryption is established when the client connects with SMP 2. Application registration (App ID) is verified 3. SMP server authentication takes place (first tier) 4. Data source (EIS) authentication takes place (second tier) This process is different for SAP Agentry applications as of SMP 2.3 Application Registration SMP Credentials ID U1 U2 Data Tier Credentials 2013 SAP AG. All rights reserved. Public 10

11 Protocols by platform version SUP SUP 2.2 SMP 2.3 SMP 3.0* SMP Messaging X X X X SMP Replication X X X X HTTP Rest API X X X SAP Agentry X X SAP Afaria Backend SAP Mobile Platform SMP Application Backend Application Layer HTTP (Rest API) Application Layer Communication Layer SAP Agentry SAP Afaria SMP Replication SMP Messaging Agentry (ANGEL**) *SMP3.0 road map, subject to change, see disclaimer, **ANGEL Agentry Next Generation Encryption Layer Communication Layer 2013 SAP AG. All rights reserved. Public 11 Afaria Agentry Client SAP Afaria

12 Transport Security

13 SMP Messaging communication SMP Messaging is always compressed and encrypted Protocol HTTP encapsulated (HTTPS is optional) Compressed & Encrypted Binary protocol Encryption 1024 bit asynchronous encryption 1024 bit RSA Public Key exchange 128 bit AES synchronous encryption (payload) Data traffic (payload) encryption from SMP-Client to the SMP-Server. Synchronous keys are automatically renewed automatically during Synchronization Session SAP AG. All rights reserved. Public 13

14 SMP Replication traffic encryption Replication traffic is encrypted with AES by default (SMP ) RSA for key exchange, 128bit AES transport encryption (configurable in SCC) The RSA Public Key is transported to the SMP client via SMP Messaging Traffic is HTTP with a binary payload, HTTPS encapsulation optional Devices need to be registered (via SMP Messaging) before data replication can take place SMP installs with default RSA keys you MUST change them! SAP AG. All rights reserved. Public 14

15 HTTP REST API traffic encryption The HTTP REST API is using regular HTTPS (SSL) for traffic encryption. REST API is a server side only API, no client side SMP specific modules HTTPS security level (SSL version), depends on the SSL Endpoint and the client implementation. The SSL for REST API traffic is often terminated on a customers reverse proxy or the SMP Relay Server. SAP Mobile Platform Application Layer Communication Layer D M Z HTTP(s) Application using REST API 2013 SAP AG. All rights reserved. Public 15

16 SAP Agentry SAP Agentry traffic can be encrypted with SSL The Agentry server is either stand-alone or part of SMP (v2.3 and higher), depending on the SMP version. The Agentry traffic protocol is called ANGEL, and is custom TCP binary traffic. The Agentry Server is not (as of SMP 2.3) integrated into the SMP Security concept. All discussed concepts in this presentation do NOT apply to SAP Syclo Agentry if not explicitly stated otherwise. SAP Mobile Platform Agentry Server D M Z Agentry (ANGEL) SAP Syclo Client METADATA 2013 SAP AG. All rights reserved. Public 16

17 SMP Application Identification

18 Application identification concept In order for SMP to function properly and to supply a high level of security, every app needs to be uniquely identified. A valid app identifier is used for App security only apps with a valid app connection ID are legitimate. Combined with the user credentials (U) this is an ownership (ID) & knowledge (U) security concept Data Synchronization and consistency required to sync the correct data differentials App management allows a clear management and reporting of all apps, versions, devices and users U Knowledge SMP Application Ownership ID 2013 SAP AG. All rights reserved. Public 18

19 SMP App Registration The SMP server needs to know the App connection ID getting to know this ID is called the registration process The registration process (part of enrolment) is protected, as only legitimate apps are supposed to register with the SMP server. This registration protection can be configured with SMP 1 U SMP Application ID + U SMP U ID DB 1. Credentials (configured authentication provider, automatic registration) Activation Code Activation Code 2. One time activation code (activation code is entered on app) 2 SMP Application ID + Activation Code ID DB SMP * HTTP Rest API application connection ID is optional 2013 SAP AG. All rights reserved. Public 19

20 SMP registration process details During the registration, the SMP server combines three values into a fixed registration triple* Application Name SMP application name that the developer has defined during design time. App Name App connection ID The unique ID for this particular application registration (usually hardware specific) App user name A name needed for administrative reference. SMP Application App Name App ID App User SMP App ID App User DB If this triple changes, the registration is considered invalid and the app needs to re-register. * HTTP Rest API application connection ID is optional 2013 SAP AG. All rights reserved. Public 20

21 Server Security Configuration

22 SMP - Authentication/Authorization SMP utilizes the Common Security Infrastructure (CSI) Authentication making sure the connecting user is who he claims to be Authorization check where the user belongs to and if he is entitled or not Role Mapping Puts the user into a SMP definable Role for easier administration Audit logging of authentication/authorization decisions made SMP (off by default) SMP Security Configuration Authentication Authorization Role Mapping Auditing SAP AG. All rights reserved. Public 22

23 SMP authentication The SMP authentication is a two step (tier) process: 1. SMP Server authentication - configurable, using SMP authentication providers App Registration Security Configuration SMP CDB Registration Data 2. Data Source authentication - depends on data source 1 Auth provider: LDAP Corp LDAP Data Source Definition 2 JDBC MS SQL 2013 SAP AG. All rights reserved. Public 23

24 SMP Authentication Providers SMP provides different authentication providers* that can be used in the Security Configurations (as of SMP2.3) NoSecurity LDAP NTProxy SAP SSO Token Certificate Authorization Certificate Validation User Role Authorizer HTTP Authentication Custom App Registration Security Configuration LDAP HTTP Authentication SMP CDB Registration Data Corp LDAP SAP Netweaver Authentication providers can also be combined* E.g. Use LDAP for authentication and HTTPAuth to generate a SSO2 token Data Source Definition * ** SAP AG. All rights reserved. Public 24 EIS

25 SMP Security Configurations SMP Security configurations are defined globally and can then be assigned to SMP domains (tenants) Applications (application templates) Packages (data structure definitions) Security Configuration SSO2 Token LDAP SMP Domain Prod-South SMP Domain Prod-North Security Configuration Corporate AD SMP Domain Test Security Configuration Developer HTTP Authentication LDAP UserRole Application Sales v1 Application Inventory Application Test-Dev * SAP AG. All rights reserved. Public 25

26 Value By providing these security configuration features, the SAP Mobile Platform allows: Implementation of complex security requirements (e.g. SSO with SAP tokens, Network Edge Authentication, ). Custom authenticators if required. Multi-Tenant support for large corporations. Global security configurations can be done by security experts and then used and assigned by SMP administrators. Multiple apps can share a security configuration without the need of re-wirering for each app SAP AG. All rights reserved. Public 26

27 DMZ Security

28 SMP Protocol Reference SMP is utilizing some very specialized protocols. In order to find the best suited networking setup, the used protocols and their individual nature needs to be kept in mind. Protocol Comment Structure HTTPS Relay Server support Messaging aka imo, MOCCA, MBS, ODP traffic HTTP, plaintext header with binary body, Yes, HTTPS encapsulation optional Replication aka - Mobilink, RBS HTTP, binary payload, Yes, HTTPS encapsulation optional HTTP REST HTTP standard HTTP plain Yes, HTTPS optional Yes Yes ANGEL Syclo Agentry traffic TCP binary, SSL encrypted No No No Yes Yes Out-of-the-box Reverse Proxy filters No No 2013 SAP AG. All rights reserved. Public 28

29 Firewall Firewall SMP Relay Server RelayServer (RS) is an optional DMZ security component 1. Additional network security component in front of SMP Prevents a direct connection from the internet to the SMP server 2. Allows only SMP / Afaria Traffic, all other traffic is dropped / blocked (basic protocol checks) 3. Requires only one outbound port in the inner DMZ (messaging & replication & Rest API) 4. Allows to reduce the open inbound ports from the internet, e.g. reduction to 443 for SMP traffic. 5. Provides built in load balancing for SMP & Afaria clusters (built in round robin) Internet DMZ LAN Mobile Device 1 Proxy SMP Server SMP Client 4 2 Relay Server on IIS / Apache 3 5 SMP Server 2013 SAP AG. All rights reserved. Public 30

30 Relay Server FAQ 1. Is the Relay Server required? Use of the Relay Server is considered best practice for security and architecture improvements. Technically, the RS is not required, but adds some security and architectural benefits that a reverse proxy usually does not provide. 2. Can I use a reverse proxy instead of the Relay Server? Technically this is possible, but not recommended. Due to the nature of many SMP protocols, reverse proxies are o o o very hard to configure if they are to provide a security benefit SAP support can not help as this is a customer specific infrastructure Unless you know what you do, potentially less secure as the RS 3. Do I need to license the Relay Server? No, the Relay Server is part of the SMP and does not need to be licensed separately. 4. Are there any exceptions? Yes, using the RS is a customer individual decision. e.g. when using Network Edge Authentication, RS may be considered redundant SAP AG. All rights reserved. Public 31

31 Firewall Firewall SMP Network Setup Examples - Regular Major denominators 1. Most common architecture with RS in DMZ Comments Best known setup by tech support, consulting and ecosystem Best covered by product and supporting documentation Internet DMZ LAN EIS Mobile Device SMP Client Relay Server Relay Server Service SMP Server SMP Server 2013 SAP AG. All rights reserved. Public 32

32 Firewall Firewall SMP Network Setup Examples - SMP landscape only with Reverse Proxy (no RS) Major denominators 1. Reverse Proxy as HTTPS endpoint 2. Traffic routing rules needed 3. Custom protocol filters or TCP pass-through required Comments Reverse Proxy can t filter SMP protocols out of the box custom filters required No outbound port model Network Edge authentication recommended Internet DMZ LAN Mobile Device SMP Client HTTPS 1 Proxy I Reverse Proxy 3 Replication Messaging 2 SMP Server SMP Server REST API 2013 SAP AG. All rights reserved. Public 33

33 Firewall Firewall SMP Network Setup Examples - Reverse Proxy and RS Major denominators 1. Reverse Proxy as HTTPS endpoint 2. RelayServer for additional security and ease of routing Comments Reverse Proxy for corporate security policy compliance Maintaining communication benefits of RS (outbound port, single port) No traffic routing rules needed on Reverse Proxy Internet DMZ I LAN EIS Mobile Device SMP Client HTTPS Reverse Proxy 1 HTTP SUP Server SMP Server IIS / Apache 2 Development RS plugin SMP SDK Eclipse 2013 SAP AG. All rights reserved. Public 34

34 Client Security

35 Database Encryption SMP mobile database can be encrypted with 256 bit AES. SMP Object API provides methods to generate a secure-random AES (256bit) key and encrypt the local DB with it. The app developer has all the tools to implement good data security on the mobile device Create key Encrypt DB Store key securely (Data Vault) SMP Application SMP Object API Configuration Data Vault Communication Engine Operating System OS Cert Store SAP AG. All rights reserved. Public 36

36 Data Vault - Concept The Data Vault provides encrypted storage of occasionally used, small pieces of data. SMP native applications Object API that provides secure data storage on the mobile device 256bit AES encrypted Vault API is device agnostic Usage Application queries user for password Password is used (salted & hashed) to unlock Data Vault Application can access secrets e.g. DB encryption key Backend access credentials Operating System SMP Application SMP Object API Configuration Communication Engine Data Vault OS Cert Store Taken from the Data Vault documenation: SAP AG. All rights reserved. Public 37

37 Hybrid Web Container - Container security benefits The HWC provides built in cross platform security - Local Data Security - Data at rest encryption. - Encrypted offline storage available - Browser Kit is used (not the device browser) prevents exposing data via browser cache, history or offline storage. - Communication Security - SMP Server communication is encrypted. - Built in app-device ID association - Backend Security - SMP platform authentication & authorization concepts apply (e.g. support for SSO). - SMP data source management for user data source access management etc. - User and application management Browser Kit Hybrid App Data HTML5 Container Interp. MSG Engine 2013 SAP AG. All rights reserved. Public 38

38 Rest API client security The SMP Rest API is a server side API only. That means the application developer has to handle client side security all by himself with his available developer tooling, as of SMP 2.3. The SAP Mobile Platform road map has plans to provide great tooling to increase developer productivity. E.g. Mobile Application Framework (MAF), Application Builder, etc. Product road maps can be found here: Custom App SAP Mobile Platform Application Layer Communication Layer HTTP(s) Credential handling App ID registration + handl. HTTPS traffic encryption Data at rest protection 2013 SAP AG. All rights reserved. Public 39

39 Wrapup

40 Wrapup This presentation is the first part of a planned series of 4 SMP security webcasts. Lookout for the other three parts, currently targeted for October/November Webinar recordings and announcements can be found here SMP security content starting point on SCN SMP documentation security starting point SAP AG. All rights reserved. Public 41

41 Thank you Contact information: Dirk Olderdissen Solution Advisor, Regional Mobility Presales, EMEA

42 2013 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see for additional trademark information and notices SAP AG. All rights reserved. Public 43

43 2013 SAP AG. Alle Rechte vorbehalten. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige der von der SAP AG und ihren Distributoren vermarkteten Softwareprodukte enthalten proprietäre Softwarekomponenten anderer Softwareanbieter. Produkte können länderspezifische Unterschiede aufweisen. Die vorliegenden Unterlagen werden von der SAP AG und ihren Konzernunternehmen ( SAP-Konzern ) bereitgestellt und dienen ausschließlich zu Informationszwecken. Der SAP-Konzern übernimmt keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Der SAP-Konzern steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren. SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und verschiedenen anderen Ländern weltweit. Weitere Hinweise und Informationen zum Markenrecht finden Sie unter SAP AG. All rights reserved. Public 44