DISA Mobile Threat Defense Key Functional Req Ver 1.0- 22 Oct 24.docx
DOCX document 21 KB Posted
- Attached to
- Mobility Enterprise Services (MES)
- Solicitation number
- 842571048
- Issued by
-
Defense Information Systems Agency
About this file
This document appears to be the Key Functional Requirements for the DISA Mobile Threat Defense (MTD) solution in support of the Mobility Enterprise Services (MES) contract opportunity. The key requirements include identifying malicious applications, networks, and compromised devices; issuing notifications to users and administrators; integrating with Mobile Device Management (MDM) systems and Security Information and Event Management (SIEM) tools; supporting multi-factor authentication for administration; meeting DoD security requirements; providing application vetting and analysis; and detecting inactive MTD applications, managed/unmanaged iOS profiles, and sideloaded apps.
The related federal contract opportunity is for the Mobility Enterprise Services (MES) capability to support DISA's DoD Enterprise Mobility Division. The MES objective is to provide support for the DoD Mobility Unclassified Capability (DMUC) and DoD Mobility Classified Capability (DMCC) service offerings and integrate new capabilities across these platforms.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| CUI - 842571048_MES Consolidation DF_Signed_Redacted.pdf | ||
| CUI - 842571048_MES Consolidation DF_Signed_Redacted.pdf | ||
| MES PWS Draft_842571048 (1).docx | DOCX document | |
| MES Sources_Sought_SAMgov_842571048_31 Oct 2024.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DISA Mobile Threat Defense (MTD) Key Functional Requirements Ver 1.0, Dated: 22 Oct 24
1. Identify applications as malicious if they are known to exploit OS vulnerabilities, attempt to escalate their system privileges, leak sensitive device or user data, record or monitor user actions, contain known malware, utilize existing elevated system privileges, or perform actions without the user’s permission.
2. Identify a network as malicious if traffic that is typically secured from an application to its server may be visible to an attacker on the network.
3. Identify a device as compromised if the operating system has been altered from a known-good state.
4. Issue tailored notification to the device user at the time of threat detection, including steps for self-remediation of the identified threat.
5. Issue a custom notification to the system administrator at the time of threat detection, including the affected device and threat information.
6. Provide a method of integration with MobileIron Core MDM for the purposes of communicating threat information, enrolling devices in the MEP solution, and retiring devices from the MEP solution.
7. Provide a method for forwarding threat information to enterprise security information and event management (SIEM) tools (e.g., Splunk).
8. Provide a method to enforce the use of multi-factor authentication for users authenticating to the administration console.
9. Meet all applicable DoD security requirements for the type of deployment.
10. Provide Mobile Application Vetting (MAV) and detailed App analysis reports to pre-screen and approve or deny applications submitted through the D.A.V.E. application portal.
11. Detect when an MTD application is inactive and have the capability to re-enable detection.
12. Detection of managed and unmanaged iOS Profiles.
13. Support for Multiple MDMs in a single instance.
14. Detect and alert on Side Loaded Apps on iOS and Android.
File details come from the government source that posted it. Updated .