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

RFTC Security Section
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 entering a 'Y' which will color 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 entering a 'N' which will color 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 | Description | Meets/Exceeds? | Comments
Scope 2.1.1 | Scalable from 10,000 managed devices and higher
Multi_Tenancy 2.1.2 | Support multiple enterprises within a single solution
Solution Security 2.1.3-1 | Ability to enroll a device before applying any policy (null policy)
2.3.1-2 | Ability to create Whitelist / Blacklist including OS and device models
2.1.3-3 | Allow enrollment of untrusted devices outside the enterprise (supports BYOD)
2.1.3-4 | Apply existing user attribute repository for enrollment
2.1.3-5 | Ability with active and passive tools to detect, report, and alert on a compromised device and take action based upon compliance rules
2.1.3-6 | Lock the device or to erase ONLY the managed data on a device
2.1.3-7 | Password policy enforcement
2.1.3-8 | Mask passwords when they appear in the Management GUI
2.1.3-9 | Determine which administrative user made a configuration change in the MDM administrative environment
2.1.3-10 | Determine which device user made a configuration change in the MDM console (self-service)
2.1.3-11 | Installation and configuration of individual and group soft authentication certificates
2.1.3-12 | Encrypt and Sign, decrypt and verify messages that use PKI or S/MIME encryption, where email functionality is delivered by the solution
2.1.3-13 | Restrict downloading attachments, copying of data to/from removable media, or otherwise create separate spaces or virtual containers for agency data and applications from personal data
2.1.3-14 | View the current GPS location of a device or logical grouping of devices on a map
2.1.3.1 FISMA Requirements | Certifiable at a FISMA Moderate Impact level or higher.
2.1.3.2 FIPS Requirements | Protect control and management data in transit between the MDM and the device using FIPS 140 certified cryptographic modules
2.1.3.3.1 Containerization | FIPS 140 Validated or in-progress
2.1.3.3.2 | Secure container erasure
2.1.3.3.3 | Container Protection (described by platform)
2.1.3.4 IPv6 Support | IPv6 compliance or timeline
2.1.3.5 User Authentication | Support PIN or password for device and managed apps, PIV/CAC for management portal
2.1.3.6.1 User Compliance | Set up compliance rules to include custom compliance rules for profiles, devices, groups, and whitelist/blacklist
2.1.3.6.2 | Activate / deactivate a compliance rule
2.1.3.6.3 | Specify user and group rules for application compliance, such as required or prohibited applications on a device
2.1.3.6.4 | Provide enterprise level device compliance reports
2.1.3.7.1 Alerting | Set up custom alerts to users and management
2.1.3.7.2 | Send custom alerts to one or more user roles
2.1.3.7.3 | Ability to create custom alerts and alert levels
2.1.3.7.4 | Automated alerts for security issues such as compromised devices
2.1.3.7.5 | Create alerts based upon device status (battery, roaming, unresponsive, inactive)
2.1.3.7.6 | View alerts pending acknowledgement
2.1.3.7.7 | Acknowledge alerts and track which user acknowledged
2.1.3.7.8 | Search and run reports on alerts
2.1.3.8.1 Reporting | Run reports by device, profile, provisioning details, or compliance status
2.1.3.8.2 | Subscribe to a Report (automatically delivered)
2.1.3.8.3 | Schedule a Report
2.1.3.8.4 | Print a Report
2.1.3.8.5 | Save Report to a file
2.1.3.8.6 | Report on devices that haven't communicated with the MDM in a period of time
2.1.3.8.7 | Report all policy compliance status details of devices under MDM management
2.1.3.8.8 | View reports in HTML5 dashboards from tablets or mobile devices
2.1.3.8.1.1 | Audit report on administrator activity
2.1.3.8.1.2 | Audit report on user access times and enrollments
2.1.3.8.1.3 | Audit reports on participating Agencies
2.1.3.8.1.4 | Audit reports on devices
2.1.3.8.1.5 | Audit reports on console logins and functions
2.1.3.8.1.6 | Audit reports on policy changes and versions
2.1.4 Privacy | Safeguard any Personally Identifiable Information (PII), not contain advertising
2.1.5 Service Delivery Model | Is the service model acceptable in your agency: [NAME], on-premise, or hybrid; CONUS help desk
Total Meeting Requirements