RFI Template for Enterprise Mobile Device Management
Total Page:16
File Type:pdf, Size:1020Kb
RFI Template for Enterprise Mobile Device Management MDM SOLUTION – RFI TEMPLATE About This RFI Template A secure mobile device management solution is an integral part of any effective enterprise mobility program. Mobile devices are similar to other endpoints in the enterprise and require similar security as corporate issued desktops and laptops. Many businesses are also subject to regulatory requirements and compliance standards that drive the need for specific mobile security capabilities. Enterprise mobility is fast-changing with a crowded field of products and solutions from several vendors. Businesses have to choose carefully to pick the correct solution that will not only address their needs today but also those of the future. Not all MDM solutions are created equal. There are several products that only offer basic asset management capabilities for mobile devices. Some others support only a limited range of features on some platforms. Very few solutions offer a full complement of capabilities that address enterprise mobile security, availability, and manageability requirements that go beyond device management to address content security and “business-ready” apps. This document provides guidelines on key requirements that should be addressed by an MDM solution. The requirements for MDM solutions are grouped into the following categories: 1. Core MDM capabilities 2. Simplicity of MDM solution for administrators and end-users 3. End-to-end security and compliance 4. Enterprise-grade architecture 5. Best-in-class support, services and training © 2012 Zenprise, Inc. 2 MDM SOLUTION – RFI TEMPLATE 1 Core MDM Capabilities 1.1 Delivery Model: 1.1.1 Solution should provide deployment options that fit the business model and budget, with cloud and on-premises options, as well as a hybrid option with a mix of cloud solution and back-end integrations with LDAP, PKI, and application servers, as well as subscription options. 1.1.2 Are the identical set of features available both in the on-premise version as the cloud version 1.1.3 What are the SLAs for the cloud delivery model? 1.1.4 Does the cloud or hosted solution use shared database instances for customer data or dedicat- ed database instances? Have customers experienced data-corruption issues? 1.1.5 What is longest outage that customers have experienced with the cloud solution? What was it due to? 1.2 Integration with Systems and Services: Solution must offer out-of-the-box integration with enterprise infrastructure. 1.2.1 How does the solution integrate with Active Directory / LDAP? 1.2.2 How does integration with Microsoft® Exchange Server / ActiveSync work for securing access to corporate email/calendar? How are non-compliant devices blocked from accessing email/calendar? 1.2.3 Explain how the solution provides additional functionality over and above what is available with Microsoft Exchange™ ActiveSync (EAS) – Direct OS-MDM API integration instead of relying only on ActiveSync policies. 1.2.4 Can the solution integrate with PKI / certificate systems for access to common service and for two-factor authentication and single sign-on? 1.2.5 Can the solution integrate with security information and event management (SIEM) systems like ArcSight, Splunk, or Envision for advanced correlation, reporting, and incident forensic analysis? 1.3 Provisioning: 1.3.1 Explain the provisioning process for devices on different platforms – iOS™, Android™, Symbi- an™, and WindowsMobile™. Is the enrollment process similar or are there platform specific variations? 1.3.2 Explain how the solution provides a secure registration process in which users and devices © 2012 Zenprise, Inc. 3 MDM SOLUTION – RFI TEMPLATE cannot partially register (e.g., register with the Microsoft Exchange server but not with the MDM). 1.3.3 Explain how the solution performs a compliance check pre-enrollment, to ensure that jail- broken, rooted, or non-compliant devices can be enrolled into the system. 1.4 Presence Awareness: 1.4.1 Explain how the solution provides device status, tracking, and monitoring. Does it provide a full software inventory and a range of device statistics? 1.5 Platform Support: 1.5.1 Provide a matrix of platforms and operating systems your service supports. At a minimum the solutions should support all of the major mobile OSes – iOS, Android (including non-C2DM like Amazon Kindle Fire), Windows, Symbian, and Blackberry™. 1.5.2 Does the solution support advanced integration with Samsung SAFE approved devices to pro- vide advanced management and control for these device? 1.5.3 What is your turn around time to support new devices after they are launched? 1.5.4 Explain how the solution manages devices remotely per platform and operating system. What remote service and troubleshooting capabilities does it provide? Does it enable device service functions such as chat and remote control? 1.6 Inventory Management: 1.6.1 Explain how the solution captures and stores information about the user, device, user location, compliance, quantity, groups, device type, OS type, etc. 1.6.2 Explain how the solution manages and enforces the number of devices and types of devices per user. 1.6.3 Does the solution support the Apple® VPP program to enable automated provisioning of volume licenses purchased from the Apple enterprise store? 1.7 Security and Compliance Management: The MDM solution must have the capability to detect, block/allow, and report on devices that are not compliant with security requirements and policies. It must also enable IT to specify certain device compliance checks prior to enrollment. 1.7.1 How does the solution identify, report, and handle violations from compliance criteria? 1.7.2 Which of the following device compliance checks are available in the system? • Jail-breaking © 2012 Zenprise, Inc. 4 MDM SOLUTION – RFI TEMPLATE • Rooting • Encryption • Managed vs. unmanaged • Policy compliance • Revoked • Application blocking • Software version • Firmware version 1.7.3 How does selective wiping and full wiping work? Under what conditions can they be triggered? 1.7.4 What kind of information logging and auditing capability is available for compliance audits? 1.7.5 Do you support application deployment to managed devices? 1.7.6 Do you support selective wiping of Active Sync information? 1.7.7 How do you secure applications and over the air data exchanged with applications? 1.8 Handling of Corporate Liable versus Individually Liable Devices: 1.8.1 How does the solution handle the BYOD (bring your own device)? How are new devices sup- ported? Is the system capable of supporting Amazon Kindle Fire devices? 1.8.2 How does the solution identify corporate liable vs. individually liable devices? Does it enable users to self-identify device ownership, or does it keep that in the hands of IT or security pro- fessionals? 1.8.3 Does the solution provide a secure container for secure distribution of corporate documents that can be time-expired? 1.9 Reporting: 1.9.1 Provide a list of common reports that are available from the system. 1.9.2 Can the system provide reports by the following parameters? • By Device Count • By Device Type • By User Name and User Count • By Carriers © 2012 Zenprise, Inc. 5 MDM SOLUTION – RFI TEMPLATE • By OSes • By Inventory • By Status • By Location/Region 2 Simplicity for administrators and end-users IT administrators and security personnel are constantly under pressure to serve their internal customers efficiently. Every new task or activity adds incremental burden that causes costly additions of temporary personnel, resources, training needs or service-level challenges. Explain how the MDM solution addresses the following user experience criteria. 2.1 Deployment: MDM solutions should ease the IT administrator’s burden by making it simple to deploy policies and match them to user groups and devices. 2.1.1 Does the solution offer a console with a dashboard based view of the MDM deployment? Is the dashboard customizable by administrators? 2.1.2 Can an administrator initiate bulk actions on sets of devices directly from the dashboard view? 2.1.3 Does the console display system alerts like jail-broken or rooted devices, blocked devices, or inactive devices? 2.1.4 Can the administrator initiate enrollment notifications to unmanaged devices from the dash- board view? 2.1.5 Explain the information architecture that is used store users, groups, policies and configura- tions. Can users be associated with multiple groups (e.g., can a user be part of “West Coast”, “Management” and “Sales”, or is it a one-to-one mapping)? 2.1.6 How many steps are required to deploy a new policy? 2.1.7 How does the solution present the set of policy choices available by platform? How does it pre- vent selecting the wrong policy for a device type (e.g., Associating an Android policy to iOS)? 2.1.8 Can you change the policy once and have the change reflected everywhere the policy is de- ployed, or do you have to change it everywhere it’s deployed? As an example, can a passcode policy be changed once and applied across multiple groups or entities? 2.2 Active Directory/LDAP integration: Having up-to-date information in the MDM system is important for security. The system should allow the © 2012 Zenprise, Inc. 6 MDM SOLUTION – RFI TEMPLATE setting of policies and rules and the inheritance of policies across groups and users. 2.2.1 Does the solution automatically handle the addition or removal of groups and users based Ac- tive Directory/LDAP changes? 2.2.2 Are changes seamlessly propagated to all intended user groups