Spreadsheet: 28ed92a3-7469-4c20-a1bc-61b7f99cb584
Sheet: MDM

RFTC Mobile Device Management Functional Requirements
Instructions:  Please review the responses and compare the response content against the RFTC Requirements Document.  If the response meets the requirement, then indicate its acceptance by coloring the cell green.  If it does not meet the requirement, or if the requirement has not been addressed in the response, then please indicate this by coloring the cell black.  If there is evidence that the suggests that the response exceeds the requirement, please indicate this in the comment section of the spreadsheet.
Requirements Reference | Descriptions | Meets/Exceeds? | Comments
2.2-1 MDM General | Enforce policy rules for overall enterprise (even if consisting of multiple sub-bureaus, etc.) - hierarchical policy rules
2.2-2 | Assign device search results to a Group
2.2-3 | Assign profile to one or many group(s)
2.2-4 | Display Required applications from the Mobile Application Store
2.2-5 | View and run reports on user and device information including usage and cost
2.2-6 | Run reports by user groups, including by location
2.2-7 | Support a Software Development Kit (SDK) or Application Programming Interface (API) Framework to integrate with existing applications
2.2-8 | Able to be monitored from industry standard monitoring and security tools
2.2-9 | Integrate certificates from the solution’s internal PKI system to mobile devices as well as third party public PKI providers
2.2-10 | Performs MDM functions through a secure connection or VPN
2.2.1.1 Device Enrollment | Set a target platform for profile provisioning
2.2.1.2 | Target device model to be used for profile provisioning
2.2.1.3 | Specify minimum OS version for profile provisioning
2.2.1.4 | Target device ownership (GFE, Personal etc.) to be used for profile provisioning
2.2.1.5 | Edit any field for a "live" or "active" profile
2.2.1.6 | Capability to self-enroll an agency or BYOD device
2.2.1.7 | Centrally manage multiple devices for a single user (e.g. smartphone, tablet, etc.)
2.2.1.8 | Different policies or grouping for multiple devices under one user (tablet policy, phone policy, etc.)
2.2.1.9 | Apply multiple policies to devices simultaneously - solution specifies how conflicts are handled
2.2.1.10 | Able to use external directory service repository for enrollment
2.2.1.11 | Require users have read policy and signed agreement when enrolling
2.2.1.12 | Set support email and phone information for registration messages during enrollment
2.2.1.13 | Set a URL to redirect user to upon successful enrollment
2.2.1.14 | Able to edit an enrollment activation notification message to the user
2.2.1.15 | Set a default Device Ownership type upon enrollment for different user and device groups
2.2.1.16 | Use internal user list for enrollment for different groups (mass enrollment)
2.2.1.17 | Set different support email and phone information for registration messages for different groups (multiple agency support)
2.2.1.18 | Edit an enrollment activation notification message to the user or group of users (duplicate of #14)
2.2.1.19 | Send a user or group an activation enrollment message
2.2.2.1 Device Profiles | Ability to create a profile template for creation of new profiles
2.2.2.2 | Ability to copy profiles
2.2.2.3 | Ability to edit a "live" or "active" profile (duplicate of 2.2.1.5)
2.2.2.4 | Ability to set Profile Removal Permission for device and management interface
2.2.2.5 | Ability to set Profile Start Date
2.2.2.6 | Ability to set Profile End Date
2.2.2.7 | Ability for an edited profile to automatically update devices that currently have the profile
2.2.2.8 | Ability to push a profile to any individual device
2.2.2.9 | Ability to automatically remove profiles from devices
2.2.2.10 | Ability to support multiple profiles being applied to a single device
2.2.2.11 | Ability to delete a profile from the MDM system
2.2.2.12 | Ability to set a description for a profile
2.2.2.13 | Ability to manage app installation, camera control, app usage
2.2.2.14 | Allow multiple Wi-Fi configurations for multiple profile's
2.2.2.15 | Ability to manage device Wi-Fi settings via a policy
2.2.2.16 | [NAME]
2.2.2.17 | Ability to support multiple VPN configurations
2.2.2.18 | Control VPN Connection settings via policy
2.2.2.19 | Ability to support a VPN connection Proxy for VPN configuration
2.2.2.20 | Ability to support multiple email/calendar/contact configurations (more than one account) per profile
2.2.2.21 | Allow multiple Web Clip / Web Shortcut configurations per profile
2.2.3.1 Device Feature Management | Multi-OS support
2.2.3.2 | Control device passcode enforcement (complexity, length, presence)
2.2.3.3 | Control installation of applications
2.2.3.4 | Camera (enable / disable)
2.2.3.5 | Control all radios / communications
2.2.3.6 | Control ability to enable or disable specific hardware component and uses
2.2.3.7 | GPS (enable / disable)
2.2.3.8 | Store enterprise data to removable media (disable)
2.2.3.9 (Optional) | Roaming (enable / disable)
2.2.3.10 (Optional) | Microphone (enable / disable)
2.2.3.11 (Optional) | Geofencing: enable/disable device features based on location
2.2.4.1.1 Data Collection | Collect and report on roaming status
2.2.4.1.2 | Collect and report on last policy update time
2.2.4.1.3 | Collect and report on last synchronization time
2.2.4.1.4 | Collect and report on jailbreak / root status
2.2.4.1.5 | Collect and report on available program memory
2.2.4.1.6 | Collect and report on available storage memory
2.2.4.2 COOP | Solution describes acceptable Continuity of Operations (COOP) and [NAME] (DR) plans
2.2.4.3 File Management | Capability to secure data, files, and applications (for example pdf files or word docs) on a mobile device; this is in addition to securing the management app and PIM data
2.2.4.4 Personal Information Management | Support a secure Personal Information Manager (PIM) capability with email, calendar, and address book
2.2.5 SCAP Support | Ability to automate security and configuration checks on the server / management side (not on devices)
2.2.6.1 Device Inven. Management | Device Manufacturer/Model
2.2.6.2 | Government Furnished (GFE) or personal (BYOD) device
2.2.6.3 | Carrier
2.2.6.4 | Wireless Phone Number
2.2.6.5 | MAC Addresses
2.2.6.6 | International Mobile Equipment Identity (IMEI)
2.2.6.7 | SIM module data
2.2.6.8 | Storage capacity
2.2.6.9 | OS and Version
2.2.6.10 | Device up time
2.2.6.11 | Encryption Capability
2.2.6.12 | User Name
2.2.6.13 | User [NAME] address
2.2.6.14 | User Phone number (separate from device)
2.2.6.15 | Agency information
2.2.6.16 | Supervisor contact information
[NAME]. Inven. Reports | Device Models
2.2.7.2 | Operation System and build level
2.2.7.3 | Last access times
2.2.7.4 | Application inventory
2.2.7.5 | Last Compliance Check
2.2.7.6 | Device Compliance Status
2.2.7.7 | Carrier
2.2.7.8 | Network Card IDs (MAC address)
2.2.7.9 | Agency Assignment
2.2.7.10 | BYOD or GFE
2.2.7.11 | Security Policy [NAME])
2.2.8.1 Sys. Perf. Reports | Concurrent Management Server Connections
2.2.8.2 | Peak Management Server usage (time of day)
2.2.8.3 | Total active user and device counts
2.2.8.4 | Management server(s) Bandwidth utilization trends
2.2.8.5 | End-to-End communications with devices testing results
2.2.8.6 | Device Authentication processing times (lag when devices start talking to infrastructure)
2.2.8.7 | Email/Calendar/Contact sync durations
2.2.8.8 | Connection failure rate to/from device for the MDM system
2.2.9.1 MDM Sec. / Compliance Reports | Non-compliant devices
2.2.9.2 | Device wipe actions
2.2.9.3 | Passcode reset actions
2.2.9.4 | User/Devices with failed authentication
2.2.9.5 | Aggregate data on failed authentications
2.2.9.6 | Devices with blacklisted applications
2.2.9.7 | [NAME] devices
2.2.9.8 | Device anti-virus versions (if existing)
2.2.9.9 | Mobile Management Agent presence & version
2.2.10 (Opt) QoS | Prioritize real-time or latency-sensitive application data where appropriate
2.2.11 (Opt) Classified | Access classified data up to the SECRET level via mobile devices
2.2.12 (Opt) PIV / CAC | Support the usage and management of PIV / CAC cards on mobile devices via the MDM
2.2.13 (Opt) Biometrics | Fingerprint or face recognition with their mobile devices
2.2.14 (Opt) Network Monitoring | Monitoring of the mobile device network quality and performance
Total Meeting Requirements