Exhibit_2_Performance_Specification.pdf

UNCLASSIFIED//FOR OFFICIAL USE ONLY

i

UNCLASSIFIED//FOR OFFICIAL USE ONLY

SYSTEM PERFORMANCE SPECIFICATION

FOR

MAGTF COMMON HANDHELD (MCH)

UNITED STATES MARINE CORPS (USMC)

ACAT: AAP

14 November 2016

Prepared by: Product Manager Integration, Interoperability and Situational Awareness (I2SA) 2200 Lester Street Quantico, VA 22134

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only for Administrative or Operational Use as of 14 November 2016. Other requests for this document are referred to Marine Corps Systems Command.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.), or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App.

2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

ii

This Page Intentionally Left Blank iii

UNCLASSIFIED//FOR OFFICIAL USE ONLY

MAGTF COMMON HANDHELD (MCH)

ACAT: AAP

SYSTEM PERFORMANCE SPECIFICATION (PSPEC)

VERSION 1.0

NOVEMBER 2016

SUBMITTED BY

Major Kevin Shepherd Date Mr. Robin Makin Date MCH Team Lead Integration, Interoperability, and Situational Awareness Marine Corps Systems Command

MCH Lead Systems Engineer Integration, Interoperability, and Situational Awareness Marine Corps Systems Command

CONCURRENCE

Mr. Edmund Spinella Date Mr. Jeffrey Smith Date Assitant Product Manager, Engineering Assistant Program Manager, Engineering Integration, Interoperability, and Situational Awareness Marine Corps Systems Command

MAGTF Command, Control, Communications Marine Corps Systems Command

APPROVAL

Mr. Eric W. Miller Date Product Manager Integration, Interoperability, and Situational Awareness Acting Marine Corps Systems Command

SHEPHERD.KEVI

N.D.1149227667

Digitally signed by

SHEPHERD.KEVIN.D.1149227667

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USMC, cn=SHEPHERD.KEVIN.D.1149227667 Date: 2016.11.16 21:26:11 -05'00'

MAKIN.ROBIN

.J.1044686046

Digitally signed by

MAKIN.ROBIN.J.1044686046

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USMC, cn=MAKIN.ROBIN.J.1044686046 Date: 2016.11.16 15:53:47 -05'00' iv

This Page Intentionally Left Blank v

UNCLASSIFIED//FOR OFFICIAL USE ONLY

REVISION HISTORY

Revision Date Change Pages/ Change Authority Approval vi

UNCLASSIFIED//FOR OFFICIAL USE ONLY

Table of Contents 1 Scope

Identification .................................................................................................................. 11 1.1

System Description ........................................................................................................ 11 1.2

2 Applicable Documents

Government Documents................................................................................................. 12 2.1

2.1.1 Military Specifications, Standards, and Handbooks

2.1.2 Other Government Documents, Drawings and Publications

Non-Government Documents and Standards................................................................. 14 2.2

Order of Precedence and Criticality of Requirements ................................................... 15 2.3

3 Requirements

Mission Profile ............................................................................................................... 16 3.1

System Attributes ........................................................................................................... 17 3.2

3.2.1 Environmental

3.2.2 Security

3.2.3 Safety

3.2.4 Human Factors Engineering (HFE)

3.2.5 Reliability

3.2.6 Maintainability

3.2.7 Interoperability

3.2.8 Survivability

3.2.9 Support Equipment

3.2.10 Family of Systems

3.2.11 Wireless Access point

End User Device (EUD)................................................................................................. 48 3.3

3.3.1 EUD Operating System

3.3.2 EUD MDM Agent

3.3.3 EUD Security

3.3.4 Commercial EUD

Application Software...................................................................................................... 72 3.4

3.4.1 Application Graphical User Interface (GUI)

vii

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.4.2 Configuration and Utility

3.4.3 Message Exchanges

3.4.4 Command and Control

3.4.5 Map, Imagery, Video

3.4.6 Navigation

3.4.7 Common Tactical Picture (CTP) Track Management

3.4.8 CTP Display Tailoring

3.4.9 Fires

3.4.10 Application Programmer Interfaces (APIs)

Expeditionary Interface ................................................................................................ 293 3.5

3.5.1 Human System Integration

Peripheral ..................................................................................................................... 294 3.6

3.6.1 Mission Planner

4 Verification

General ......................................................................................................................... 296 4.1

4.1.1 Verification Methods

4.1.2 Classification of Verification Cases

4.1.3 Functional Qualification Test

4.1.4 Basis for Acceptance

System Attributes Verification..................................................................................... 298 4.2

4.2.1 Environmental Verification

4.2.2 Security Verification

4.2.3 Safety Verification

4.2.4 Human Factors Engineering (HFE) Verification

4.2.5 Reliability Verification

4.2.6 Maintainability Verification

4.2.7 Interoperability Verification

4.2.8 Survivability Verification

4.2.9 Support Equipment Verification

4.2.10 Family of Systems Verification

4.2.11 Wireless Access Point Verification

viii

UNCLASSIFIED//FOR OFFICIAL USE ONLY

End User Device (EUD) Verification .......................................................................... 337 4.3

4.3.1 EUD Operating System (OS) Verification

4.3.2 EUD MDM Agent Verification

4.3.3 EUD Security Verification

4.3.4 Commercial EUD Verification

Application Software Verification ............................................................................... 370 4.4

4.4.1 Application Graphical User Interface Verification

4.4.2 Configuration and Utility Verification

4.4.3 Message Exchanges Verification

4.4.4 Command and Control Verification

4.4.5 Map, Imagery, Video Verification

4.4.6 Navigation Verification

4.4.7 Common Tactical Picture (CTP) Track Management Verification

4.4.8 CTP Display Tailoring Verification

4.4.9 Fires Verification

4.4.10 Application Programmer Interfaces (APIs) Verification

Expeditionary Interface Verification............................................................................ 528 4.5

4.5.1 Human System Integration Verification

Peripheral Verification ................................................................................................. 529 4.6

4.6.1 Provisioning / Mission Planner Verification

5 Packaging

6 Notes

Intended Use................................................................................................................. 533 6.1

First Article .................................................................................................................. 533 6.2

Definitions.................................................................................................................... 534 6.3

Acronyms ..................................................................................................................... 551 6.4

7 APPENDIX A: Platform Interoperability............................................................................. 7-1

8 APPENDIX B: MCH Threshold Digital Messages.............................................................. 8-4

9 APPENDIX C: MCH Objective Digital Messages .............................................................. 9-1

10 APPENDIX D: MCH Software Configurable items and Characteristics........................... 10-1

11 APPENDIX E: Control Measures ...................................................................................... 11-1 ix

UNCLASSIFIED//FOR OFFICIAL USE ONLY

List of Tables

Table 1 MCH JCAs Supported Table 2 MCH USMC Missions Supported Table 3 MCH Verification Cases Table 4 MCH Definitions Table 5: Acronyms Table 6: Platform Interoperability ............................................................................................... 7-3 Table 7: MCH Threshold Digital Messages ................................................................................ 8-7 Table 8: MCH Objective Digital Messages ................................................................................. 9-4 Table 9: Controls / Indicators .................................................................................................... 10-1 Table 10: Preference / Profile Settings ...................................................................................... 10-6 Table 11: Danger Zones............................................................................................................. 10-6 Table 12: Critical System Events............................................................................................... 10-6 Table 13: Map File Types .......................................................................................................... 10-7 Table 14: Entity Types............................................................................................................... 10-7 Table 15: Platform Types........................................................................................................... 10-7 Table 16: Fire Control Measures ............................................................................................... 11-2 x

This Page Left Intentionally Blank

UNCLASSIFIED//FOR OFFICIAL USE ONLY

1 Scope

Identification1.1 This system performance specification establishes the requirements and the Government’s framework for verification testing of the Marine Air-Ground Task Force (MAGTF) Common Handheld (MCH) System, hereafter referred to as the MCH System.

System Description1.2 The MCH System is comprised of Government Off-the-Shelf (GOTS), Commercial Off-the- Shelf (COTS) and Non-Developmental Item (NDI) hardware and software. It is a modular, man-portable equipment suite that provides the warfighter with functionality common to the United States Marine Corps’ (USMC) Target Hand-off System (THS) Version 2, and the Joint Battle Command-Platform (JBC-P) Command and Control/Situational Awareness (C2/SA) Family of Systems (FoS). The MCH System will allow the warfighter to quickly acquire targets in day, night, and near all-weather visibility conditions; and control close air support (CAS) as well as artillery and naval surface fire support missions. The MCH System will also serve as a digital information processing and display system that provides integrated, on-the-move secure, timely, and relevant C2/SA information to tactical combat, combat support and combat service support commanders, leaders, and key C2 nodes using digital communications. Additionally, the MCH System will provide:

Leaders with a capability for selecting, managing, and assimilating relevant data and information Commanders with the ability to concentrate combat weapons system effects rather than combat forces and enable units to become both more survivable and lethal The ability to pass orders and graphics that will provide the joint warfighter the capability to visualize the commander’s intent and scheme of maneuver Enhanced SA of friendly, reported enemy, neutral, and civilian entities C2 at the dismounted level along with affording joint warfighters the capability to gain and retain the tactical and operational initiative under all Mission, Enemy, Terrain, Troops, Time, and Civilians (METT-TC) conditions despite an accelerated tempo.

UNCLASSIFIED//FOR OFFICIAL USE ONLY

2 Applicable Documents The documents listed in this section are referenced in sections 3, 4 and 5 of this specification.

While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited in sections 3, 4, and 5 of this specification, whether or not they are listed.

Government Documents2.1

2.1.1 Military Specifications, Standards, and Handbooks

The following military specifications, standards and handbooks of the exact revision listed below form a part of this document to the extent specified herein.

MCO P5090.2A w/Change 3: Environmental Compliance and Protection Manual MIL-DTL-22992H: Connectors, Plugs and Receptacles, Electrical, Waterproof, Quick Disconnect, Heavy Duty Type, General Specification for MIL-DTL-26482H w/Amendment 1: Connectors, Electrical, (Circular, Miniature, Quick Disconnect, Environment Resisting), Receptacles and Plugs, General Specification for MIL-DTL-38999M: Connectors, Electrical, Circular, Miniature, High Density, Quick Disconnect (Bayonet, Threaded or Breech Coupling), Environment Resistant with Crimp Removable Contacts or Hermetically Sealed with Fixed, Solderable Contacts, General Specification for MIL-HDBK-783: Chemical and Biological Contamination Avoidance and Decontamination MIL-STD-130N Change 1: Identification Marking of U.S. Military Property MIL-STD-188-220D Change 1:Digital Message Transfer Device Subsystems MIL-STD-461G: Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment MIL-STD-464C: Electromagnetic Environmental Effects Requirements for Systems MIL-STD-648D: Specialized Shipping Containers MIL-STD-810G Change 1: Environmental Engineering Considerations and Laboratory Tests MIL-STD-882E: System Safety MIL-STD-1472G: Human Engineering MIL-STD-1474E: Department of Defense Design Criteria Standard Noise Limits MIL-STD-2045-47001D Change 1: Connectionless Data Transfer Application Layer Standard MIL-STD-2073-1E w/Change 1: Standard Practice for Military Packaging MIL-STD-2500C: National Imagery Transmission Format Version 2.1 MIL-STD-2525D: Joint Military Symbology MIL-STD-6016E: Tactical Data Link 16 Message Standard

UNCLASSIFIED//FOR OFFICIAL USE ONLY

MIL-STD-6017: Variable Message Format MIL-STD-6017A: Variable Message Format MIL-STD-6017B: Variable Message Format MIL-STD-6017C: Variable Message Format

2.1.2 Other Government Documents, Drawings and Publications

The following Government documents, drawings and publications of the exact revision level shown form a part of this document to the extent specified herein.

29 CFR 1910: Occupational Safety and Health Standards CNSSAM TEMPEST/1-13: Red/Black Installation Guidance; 17 January 2014 CNSSI-1253: Security Categorization and Control Selection for National Security Systems Version 2; 15 March 2012 CNSSI No. 1300: Instruction for National Security Systems Public Key Infrastructure X.509 Certificate Policy CNSSP-7: Policy on the Use of Commercial Solutions to Protect National Security Systems; 9 December 2015 CNSSP-11: National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology Products; 10 June 2013 DODD S-5200.19 w/Change 1 and Transmittal 68-3: Control of Compromising Emanations DODI 8500.01: Cybersecurity; March 14, 2014 DODI 8510.01: Risk Management Framework (RMF) for DoD Information Technology (IT); March 12, 2014.

FED-STD-595C w/Change 1: Colors Used in Government Procurement FIPS 140-2: Security Requirements for Cryptographic Modules; May25, 2001 FIPS 199: Standards for Security Categorization of Federal Information and Information Systems Joint Publication 3-09.3 Close Air Support; Nov 2014 MCRP 3-16.6A Joint Application of Firepower (JFIRE); January 2016

NATO STANAG 4677

NAVSEA S9310-AQ-SAF-010: Technical Manual for Navy Lithium Battery Safety Program Responsibilities and Procedures, Second Revision, 15 Jul 2010 NIST SP 800-53 Revision 4: Security and Privacy Controls for Federal Information Systems and Organizations NIST SP 800-59: Guideline for Identifying an Information System as a National Security System NIST SP 800-60 Vol 1 Revision 1: Guide for Mapping Types of Information and Information Systems to Security Categories

UNCLASSIFIED//FOR OFFICIAL USE ONLY

NIST SP 800-88 Revision 1: Guidelines for Media Sanitization; December 2014 NIST SP 800-163: Vetting the Security of Mobile Applications NIST SP 800-164 (Draft): Guidelines on Hardware-Rooted Security in Mobile Devices (Draft); October 2012 NIST SP 800-124 Revision 1: Guidelines for Managing the Security of Mobile Devices in the Enterprise; June 2013 NIST SP 800-157: Guidelines for Derived Personal Identity Verification (PIV) Credentials; December 2014 JBC-P System Subsystem Specification, Aviation and Missile Research, Development and Engineering Center (AMRDEC) Software Engineering Directorate (SED), SED- JBCP-SSS-001D, 2 October, 2014 Cursor-on-Target Message Router User’s Guide (MP090284) Appendix A, Mitre Corporation, November 2009 U.S. Marine Corps NEPA Manual; 8 September 2011

Non-Government Documents and Standards2.2 The following documents of the exact revision level shown form a part of this document to the extent specified herein. Copies of these documents can be obtained by written request from Marine Corps Systems Command.

Air Force Application Program Development (AFAPD) Message Standard May 1999 Application Software V1.2, 25 April 2016 Certificate Authority V1.0, 16 May 2014 Chinese Encrypted Datum 2002 (GCJ-02) Data at Rest Capability Package Version 3; March 2016 DoD Annex for Protection Profile for Mobile Device Management V2.0, Version 1,Release 2; 20 July 2015 Earth Gravitational Model 1996 European Datum 1950 European Terrestrial Reference System 1989 Extended Package for Mobile Device Agent V2.0, 31 Dec 2014 Extended Package for VPN Gateways V2.0, 01 Dec 2015 Extended Package for Wireless Client V1.0, 11 Feb 2016 Extended Package for Wireless LAN Access Systems V1.0 28 May 2015 Extended Package for Software File Encryption, V1.1 06 Nov 2014 Geodetic Reference System 1980 IEEE Standard 802.11 IPSEC VPN Client V1.4, 23 Oct 2013 ISO/IEC 14443: Type B Proximity Contactless Identification Cards

UNCLASSIFIED//FOR OFFICIAL USE ONLY

ISO/IEC 18092: Information Technology – Telecommunications and Information Exchange Between Systems – Near Field Communication – Interface and Protocol

(NFCIP-1)

Mobile Device Management V2.0, 31 Dec 2014 National Electric Code; 2008 Edition National Fire Protection Association (NFPA) 70; 2014 Edition Protection Profile for Mobile Device Fundamentals V2.0; 10 June 2016 Registry of Toxic Effects of Chemical Substances (RETCS) South American Datum 1969 UL 60950: Information Technology Equipment - Safety World Geodetic System 1984

Order of Precedence and Criticality of Requirements2.3 In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3 Requirements Section 3 includes all requirements for the MCH System.

Mission Profile3.1 The MCH System will support the Joint Capability Areas (JCAs) indicated in Table 1 and USMC Missions indicated in Table 2. The MCH System will operate continuously with expeditionary battery charging support for 72 hours in hot, basic, and cold climates, during day and night, and in all weather conditions. The MCH System will support mission objectives through CONUS training operations and global OCONUS contingency land and littoral operations in and around desert, jungle, rain forest, mountainous, and arctic regions.

JCA 1 Force Support JCA 2 Battlespace Awareness JCA 3 Force Application JCA 4 Logistics JCA 5 Command Control JCA 6 Communication and Computers

Table 1 MCH JCAs Supported

Amphibious Air lifted Surface to Objective Maneuver

(STOM)

Amphibious Surface STOM Amphibious Company Raid Tactical Recovery of Aircraft and Personnel (TRAP) Opposed Non-combatant Evacuation Operation

(NEO)

Sustained Operations Ashore Military Operations other than Warfare (MOOTWA)

Table 2 MCH USMC Missions Supported

UNCLASSIFIED//FOR OFFICIAL USE ONLY

System Attributes3.2

3.2.1 Environmental

3.2.1.1 The MCH System shall be fully operable without degradation at a continuous, ambient temperature of -40°F in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.2 The MCH System shall be fully operable without degradation at a continuous, ambient temperature of 130°F in accordance with MIL-STD-810G Change 1. (T)

3.2.1.3 The MCH System should be fully operable without degradation at a continuous, ambient temperature of 140°F in accordance with MIL-STD-810G Change 1. (O)

3.2.1.4 The MCH System shall be capable of being stored without suffering degradation at temperatures ranging from ambient to -40 F in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.5 The MCH System shall be capable of being stored without suffering degradation at temperatures ranging from ambient to 158 F in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.6 The MCH System shall not suffer any degradation in performance following a submersion in salt water at a depth of 1.0 meter in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.7 The MCH System, within its transit case, shall not suffer any degradation of performance following a 30 minute submersion in salt water at a depth of 1.0 meter in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.8 The MCH System shall operate without degradation after exposure to rain for 2 hours in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.9 The MCH System shall not suffer degradation after exposure to 6mm of frozen precipitation accumulation in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.10 The MCH System shall operate without degradation after exposure to blowing sand and dust in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.11 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with CE101. (T=O)

3.2.1.12 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with CE102. (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.1.13 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with CS101. (T=O)

3.2.1.14 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with CS114. (T=O)

3.2.1.15 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with CS115. (T=O)

3.2.1.16 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with CS116. (T=O)

3.2.1.17 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with CS118. (T=O)

3.2.1.18 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with RE101. (T=O)

3.2.1.19 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with RE102. (T=O)

3.2.1.20 In all authorized use cases, the MCH System shall meet the requirements in MIL-STD- 461G in accordance with RS103. (T=O)

3.2.1.21 The MCH system in its transit configuration shall not suffer degradation of performance due to the vibrations experienced during transportation in accordance with MIL-STD- 810G Change 1. (T=O)

3.2.1.22 The MCH system shall be operable without performance degradation in standard atmosphere conditions at an altitude of 25,000 ft. in accordance with MIL-STD-810G Change 1. (T) Note: Standard Atmosphere conditions are defined in MIL-STD-3013.

3.2.1.23 The MCH system should be operable without performance degradation in standard atmosphere conditions at an altitude of 42,000 ft. in accordance with MIL-STD-810G Change 1. (O) Note: Standard Atmosphere conditions are defined in MIL-STD-3013.

3.2.1.24 The MCH System shall not suffer any degradation in performance (as a result of atmospheric pressure related effects) after being subjected to a military free fall operation conducted from 25,000 ft. Mean Sea Level (MSL) in accordance with MIL- STD-810G Change 1. (T)

3.2.1.25 The MCH System should not suffer any degradation in performance (as a result of atmospheric pressure related effects) after being subjected to a military free fall operation conducted from 42,000 ft. MSL in accordance with MIL-STD-810G Change

1. (O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.1.26 The MCH System shall not suffer any degradation in performance following sudden changes in ambient air temperature of up to 35.6 F/min (T).

3.2.1.27 The MCH System should not suffer any degradation in performance following sudden changes in ambient air temperature of up to 50 F/min in accordance with MIL-STD- 810G Change 1. (O)

3.2.1.28 The MCH System shall operate without leakage during and after exposure to a salt fog environment in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.29 The MCH System shall operate without degradation during and after exposure to a salt fog environment in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.30 The MCH System shall not be degraded in performance after experiencing shock commonly induced during normal transportation in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.31 The MCH System shall not be degraded in performance after experiencing shock commonly induced during normal maintenance in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.32 The MCH System shall not be degraded in performance after experiencing shock commonly induced during normal field operations in accordance with MIL-STD-810G Change 1. (T=O)

3.2.1.33 The MCH System shall not suffer any degradation in performance when exposed to solar radiation of up to 1120W/m2 in accordance with MIL-STD-810G Change 1.

(T=O)

3.2.1.34 The MCH System shall not suffer any degradation in performance between 0% and 95% humidity in accordance with MIL-STD-810G Change 1. (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2 Security

3.2.2.1 The MCH system shall be certifiable to process SECRET data in accordance with references including: DoD 8510.01 "Risk Management Framework for DoD Information Technology", DoDI 8500.01 "Cybersecurity" , DoDI 5000.02 "Operation of the Defense Acquisition System", CNSSI-1253 "Security Categorization and Control Selection for National Security Systems", CNSSP-7 "Policy On The Use of Commercial Solutions to Protect National Security Systems", CNSSP-11 "National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology Products" and National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 Rev.4 "Security and Privacy Controls for Federal Information Systems and Organizations", NIST SP 800-59 “Guidelines for Identifying an Information System as a National Security System”, NIST SP 800-60, “Guide for Mapping Types of Information and Information Systems to Security Categories”; and Federal Information Processing Standards [FIPS] 199, “Standards for Security Categorization of Federal Information and Information Systems." (T=O)

3.2.2.2 The MCH system shall be designed to comply with either the NSA Commercial Solutions for Classified (CSfC) Mobile Access or the Campus WLAN Capability Package, including any identified deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O)

3.2.2.3 The MCH system shall be designed to comply with the NSA Commercial Solutions for Classified (CSfC) Data-At-Rest Capability Package, including any identified deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O)

3.2.2.4 The MCH system shall comply with NIAP Protection Profile (PP) guidance including the Mobile Device Fundamentals PP for the EUD, the Mobile Device Management and Agent PPs for the Mobile Device Management components, the Certification Authority (CA) PP for Certificate Authorities, the Extended Package for VPN Gateways and IPsec VPN Client PP for IPsec VPN client, Extended Packages for Wireless LANT Client and Wireless LAN Access Systems, Extended Package for Software File Encryption, and Application Software PP. (T=O)

3.2.2.5 The MCH system shall exchange SECRET data over wireless media in accordance with the NSA CSfC Mobile Access or Campus Wireless LAN Capability Package composed solution guidance, including any identified deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.6 The MCH system shall exchange SECRET data over the wired USB tether in accordance with the NSA CSfC Mobile Access or Campus Wireless LAN Capability Package composed solution guidance, including any identified deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O) Note: for wired communication, "securely" is achieved by physical security vice digital security.

3.2.2.7 The MCH system shall have provisions to detect if unauthorized changes are made to EUD security settings to meet security control SA-10 Developer configuration management from NIST SP 800-53 revision 4. (T=O) Note: Unauthorized changes are those made without explicit permission or approval.

3.2.2.8 The MCH system shall have provisions to detect if unauthorized changes are made to EUD security related software to meet security control SA-10 Developer configuration management from NIST SP 800-53 revision 4. (T=O)

3.2.2.9 The MCH system shall have provisions to detect if unauthorized changes are made to EUD security settings to meet security control SI-7 "Software, Firmware, and Information Integrity" from NIST SP 800-53 revision 4. (T=O)

3.2.2.10 The MCH system shall have provisions to detect if changes are made to EUD security related software to meet security control SI-7 "Software, Firmware, and Information Integrity" from NIST SP 800-53 revision 4. (T=O)

3.2.2.11 The MCH system shall have provisions to log changes made to EUD security settings.

(T=O)

3.2.2.12 The MCH system shall have provisions to log changes made to EUD security related software. (T=O)

3.2.2.13 The MCH system shall have provisions to log if unauthorized attempts are made to change EUD security settings. (T=O) Note: Unauthorized means without explicit permission.

3.2.2.14 The MCH system shall have provisions to log unauthorized attempts made to change EUD security related software. (T=O) Note: Unauthorized means without explicit permission.

3.2.2.15 The MCH System shall have provisions to protect against unauthorized changes made to the EUD security settings (T=O). Note: Unauthorized means without explicit permission.

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.16 The MCH System shall have provisions to protect against unauthorized changes made to the EUD security related software (T=O). Note: Unauthorized means without explicit permission.

3.2.2.17 The MCH user shall be granted access to the EUD only after successfully authenticating to the device in accordance with guidance provided by the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

3.2.2.18 The MCH user shall be granted access to the EUD plain text data only after successfully authenticating to the device in accordance with composed solution guidance provided by the NSA CSfC DAR Capability Package including any identified tactical deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O)

3.2.2.19 The MCH user shall be granted access to the EUD only after successfully authenticating to the device in accordance with composed solution guidance provided by the NSA CSfC Mobile Access or Campus Wireless LAN Capability Package including any identified tactical deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O)

3.2.2.20 The MCH user shall be granted access to the MCH applications only after successfully authenticating to these applications in accordance with composed solution guidance provided by the NSA CSfC Mobile Access or Campus Wireless LAN Capability Package including any identified tactical deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O)

3.2.2.21 The MCH system shall provide network device authentication in accordance with the NSA CSfC Mobile Access or Campus Wireless LAN Capability Package including any identified tactical deviations to the solution that have been submitted and approved through the CSfC registration office. (T=O)

3.2.2.22 The MCH system shall securely transmit data via a wireless 802.11, Wi-Fi connection in accordance with EUD configuration guidance presented in the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

3.2.2.23 The MCH system shall securely receive data via a wireless 802.11, Wi-Fi connection in accordance with EUD configuration guidance presented in the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

3.2.2.24 The MCH system shall securely transmit data via a wireless Bluetooth connection in accordance with EUD configuration guidance presented in the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.25 The MCH system shall securely receive data via a wireless Bluetooth connection in accordance with EUD configuration guidance presented in the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

3.2.2.26 The MCH system shall securely transmit SECRET data via a wireless connection in accordance with guidance presented in the CSfC Mobile Access or Campus Wireless LAN Capability Package. (T=O)

3.2.2.27 The MCH system shall securely receive SECRET data via a wireless connection in accordance with guidance presented in the CSfC Mobile Access or Campus Wireless LAN Capability Package. (T=O)

3.2.2.28 All modifications to the MCH EUD boot process shall be detected in accordance with guidance provided by the NIAP Mobile Device Fundamentals, Mobile Device Management, and Mobile Device Agent Protection Profiles (T=O)

3.2.2.29 All modifications to the MCH EUD boot process shall be logged in accordance with guidance provided by the NIAP Mobile Device Fundamentals, Mobile Device Management, and Mobile Device Agent Protection Profiles (T=O)

3.2.2.30 The MCH system shall allow the configuration of application privileges on the EUD by authorized administrators in accordance with the Mobile Access or Campus Wireless

LAN CP. (T=O)

3.2.2.31 Updates to the MCH antivirus software shall not require internet connectivity. (T=O)

3.2.2.32 Updates to the MCH host intrusion prevention software shall not require internet connectivity. (T=O)

3.2.2.33 The MCH user shall be prevented from tampering with the reporting of events from the device in accordance with guidance provided by the NIAP Mobile Device Fundamentals, Mobile Device Management and MDM Agent Protection Profiles.

(T=O)

3.2.2.34 The MCH user shall be prevented from disabling the reporting of events from the device in accordance with guidance provided by the NIAP Mobile Device Fundamentals, Mobile Device Management and MDM Agent Protection Profiles.

(T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.35 When connected to the tactical networks, the MCH System shall use time synchronized with the tactical network. (T=O) Note: There are three basic types of synchronization methods for wireless networks. The first is relative timing and is the simplest. It relies on the ordering of messages and events. The basic idea is to be able to determine if event 1 occurred before event 2. Comparing the local clocks to determine the order is all that is needed. Clock synchronization is not important. The next method is relative timing in which the network clocks are independent of each other and the nodes keep track of drift and offset. Usually a node keeps information about its drift and offset in correspondence to neighboring nodes. The nodes have the ability to synchronize their local time with another nodes local time at any instant. Most synchronization protocols use this method. The last method is global synchronization where there is a constant global timescale throughout the network.

3.2.2.36 When not connected to the tactical network and if connected to a SAASM GPS, the MCH EUD shall use Coordinated Universal Time (UTC) from the SAASM GPS time code receiver. (T=O) Note: See CJSCI 6130.01E for UTC time standard directive.

3.2.2.37 The MDM server shall securely validate remote attestation by the EUD in accordance with guidance provided by the NIAP Mobile Device Fundamentals, Mobile Device Management and MDM Agent Protection Profiles. (T=O)

3.2.2.38 The MDM system shall enforce the security critical policies specified in the NIAP Mobile Device Fundamentals Protection Profile on each MCH EUD. (T=O)

3.2.2.39 The MCH system shall provide application updates via wired connections in accordance with guidance provided by the NIAP Mobile Device Management, NIAP Mobile Device Fundamentals Protection Profile, and the MDM Agent Protection Profiles. (T)

3.2.2.40 The MCH system should provide application updates via Over the Air connections in accordance with guidance provided by the NIAP Mobile Device Fundamentals Protection Profile, Mobile Device Management, and MDM Agent Protection Profiles.

(O)

3.2.2.41 The MCH MDM shall validate the software version level of each connected EUD's operating systems via wired connections in accordance with guidance provided by the NIAP Mobile Device Fundamentals and Mobile Device Management and MDM Agent Protection Profiles. (T)

3.2.2.42 The MCH MDM shall validate the software version level of each connected EUD's MDM client via wired connections in accordance with guidance provided by the NIAP Mobile Device Fundamentals and Mobile Device Management and MDM Agent Protection Profiles. (T)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.43 The MCH MDM shall validate the software version level of each connected EUD’s MCH applications via wired connections in accordance with guidance provided by the NIAP Mobile Device Fundamentals and Mobile Device Management and MDM Agent Protection Profiles. (T)

3.2.2.44 The MCH system should validate the software version level of each connected EUD's operating system via Over the Air connections in accordance with guidance provided by the NIAP Mobile Device Fundamentals and Mobile Device Management and MDM Agent Protection Profiles. (O)

3.2.2.45 The MCH system should validate the software version level of each connected EUD's MDM client via Over the Air connections in accordance with guidance provided by the NIAP Mobile Device Fundamentals and Mobile Device Management and MDM Agent Protection Profiles. (O)

3.2.2.46 The MCH system should validate the software version level of each connected EUD's MCH applications via Over the Air connections in accordance with guidance provided by the NIAP Mobile Device Fundamentals and Mobile Device Management and MDM Agent Protection Profiles. (O)

3.2.2.47 The MCH EUD wipe functionality shall include cryptographically erasing all Data Encryption Keys in non-volatile memory in accordance with guidance provided by the NIAP Mobile Device Fundamentals PP. (T=O)

3.2.2.48 The MCH system wipe function shall overwrite all protected data in accordance with guidance provided by the NIAP Mobile Device Fundamentals PP. (T=O)

3.2.2.49 The MCH system shall wipe protected data upon command in accordance with the NIAP Mobile Device Fundamentals PP. (T=O)

3.2.2.50 The MCH system shall wipe sensitive data upon command in accordance with the NIAP Mobile Device Fundamentals PP. (T=O)

3.2.2.51 The MDM client shall wipe MCH applications upon command in accordance with the NIAP Mobile Device Fundamentals PP. (T=O)

3.2.2.52 The MCH system shall be able to perform EUD wipe upon removal of the EUD MDM Client. (T=O)

3.2.2.53 The MCH system shall be able to perform EUD wipe upon removal of any of the EUD's security policies. (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.54 The MCH system shall cryptographically erase cryptographic keys on specified network connected MCH EUDs upon command by an administrator in accordance with guidance provided by the NIAP Mobile Device Fundamentals PP. (T=O)

3.2.2.55 The MCH system shall cryptographically erase cryptographic keys on specified network connected MCH EUDs upon command by an administrator in accordance with guidance provided by NIST SP 800-88 Rev 1. (T=O)

3.2.2.56 The MCH system remote wipe operation shall be accessible to authorized administrators from the Mobile Device Manager in accordance with the NIAP Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.57 The MCH system shall allow the operator to initiate the wipe operation on the EUD.

(T=O)

3.2.2.58 The MCH administrator shall be able to designate the number of consecutive unsuccessful login attempts allowable. (T=O)

3.2.2.59 The MDM server shall validate assertions made by the MCH EUD RTV in accordance with the NIAP Mobile Device Management and Agent Protection Profiles and NIST SP 800-164. (T=O)

3.2.2.60 The MDM server shall incorporate software that shall enable administrators to transition selected EUDs to the locked state in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.61 The MDM server shall incorporate software that shall enable administrators to perform a full wipe of protected software on selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.62 The MDM server shall incorporate software that shall enable administrators to un-enroll selected EUDs from MDM management in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.63 The MDM server shall incorporate software that shall enable administrators to install policies on selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles.

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.64 The MDM server shall incorporate software that shall enable administrators to query network connectivity status of selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.65 The MDM server shall incorporate software that shall enable administrators to query firmware versions of selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.66 The MDM server shall incorporate software that shall enable administrators to query hardware versions of selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.67 The MDM server shall incorporate software that shall enable administrators to query application versions of selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.68 The MDM server shall incorporate software that shall enable administrators to import and remove X.509v3 certificates from the Trust Anchor Database of a selected EUD in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.69 The MDM server shall incorporate software that shall enable administrators to install/remove applications of selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.70 The MDM server shall incorporate software that shall enable administrators to import and destroy keys in secure key storage on a selected EUD in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.71 The MDM server shall incorporate software that shall enable administrators to read audit logs of selected EUDs in accordance with guidance provided by the NIAP Mobile Device Fundamentals, and Mobile Device Management and Agent Protection Profiles.

(T=O)

3.2.2.72 The MCH system shall provide a method to securely upgrade the EUD OS without requiring the Android EUD to be "rooted". (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.73 The MCH system shall provide a method to securely update the MCH EUD firmware without requiring the Android EUD to be "rooted". (T=O)

3.2.2.74 The MCH system shall provide a method to securely provision USB drivers necessary for required functionality, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.75 The MCH system shall provide a method to securely upgrade the MCH EUD Wi-Fi drivers necessary for required functionality and accreditation, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.76 The MCH system shall provide a method to securely upgrade the MCH EUD Bluetooth drivers necessary for required functionality and accreditation, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.77 The MCH system shall provide a method to securely upgrade the MCH EUD mobile network access drivers necessary for required functionality and accreditation, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.78 The MCH system shall provide a method to securely update the EUD OS without requiring the Android EUD to be "rooted". (T=O)

3.2.2.79 The MCH system shall provide a method to securely update the EUD firmware without requiring the Android EUD to be "rooted". (T=O)

3.2.2.80 The MCH system shall provide a method to securely update USB drivers necessary for required functionality, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.81 The MCH system shall provide a method to securely update the Wi-Fi drivers necessary for required functionality and accreditation, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.82 The MCH system shall provide a method to securely update the Bluetooth drivers necessary for required functionality and accreditation, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.83 The MCH system shall provide a method to securely update the 4G drivers necessary for required functionality and accreditation, without requiring the Android EUD to be "rooted". (T=O)

3.2.2.84 The MCH system shall provide a method to securely update the EUD OS without requiring internet access. (T=O)

3.2.2.85 The MCH system shall provide a method to securely update the EUD firmware without requiring internet access. (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.86 The MCH system shall provide a method to securely update USB drivers necessary for required functionality, without requiring internet access. (T=O)

3.2.2.87 The MCH system shall provide a method to securely update the Wi-Fi drivers necessary for required functionality and accreditation, without requiring internet access. (T=O)

3.2.2.88 The MCH system shall provide a method to securely update the Bluetooth drivers necessary for required functionality and accreditation, without requiring internet access.

(T=O)

3.2.2.89 The MCH system shall provide a method to securely update the 4G drivers necessary for required functionality and accreditation, without requiring internet access. (T=O)

3.2.2.90 The MCH system shall provide a means of preventing unauthorized OS rollback with previously released updates in accordance with guidance provided by the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

3.2.2.91 The MCH system shall provide a means of preventing unauthorized firmware rollback with previously released updates in accordance with guidance provided by the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

3.2.2.92 The MCH system shall provide a means of preventing unauthorized software rollback with previously released updates in accordance with guidance provided by the NIAP Mobile Device Fundamentals Protection Profile. (T=O)

3.2.2.93 Removable media shall be capable of being cryptographically associated to a particular MCH EUD such that information can only be decrypted when the removable media is attached to the EUD that encrypted it; thereby mitigating the risk of offline attacks on the media in accordance with NIST SP 800-124 rev 1. (T=O)

3.2.2.94 The MDM server shall provide a mechanism for time periodic transfer of connected EUD security related log files to a logging server in accordance with the NIAP Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.95 The MDM server shall provide a mechanism for event driven transfer of connected EUD security related log files to a logging server in accordance with the NIAP Mobile Device Management and Agent Protection Profiles. (T=O)

3.2.2.96 Cryptographic modules employed in the all COTS MCH system components shall be FIPS 140-2 Validated. (T=O)

3.2.2.97 The MCH Mobile Device Management server software shall support using an external directory server to perform the authentication decision for performing the remote enrollment of an MCH EUD. (T=O)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

3.2.2.98 The MCH certificate authorities shall be compliant with NIAP Certification Authority Protection Profile guidance. (T)

3.2.2.99 The MCH certificate authorities shall be compliant with NIAP Certification Authority Protection Profile requirement selections as specified in the CSfC Mobile Access Capability or Campus Wireless LAN Package. (T)

3.2.2.100 The MCH PKI infrastructure shall be compliant with CNSSP 25 guidance as refined in

CNSSI 1300. (T)

3.2.2.101 The MCH system components shall be configured according to Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs), in compliance with CNSSI 1253.

3.2.2.102 The MCH Application Software should meet general application security requirements as defined in NIST SP 800-163, Vetting the…