Mission Partner Environment(U.S. contribution to FMN)

Multi-National Maritime Information Services Interoperability (M2I2) Board 15-2

7 September 2015

UNCLASSIFIED

UNCLASSIFIED

Joint Staff JS J6 DDC5I IIDDeputy Director Cyber and C4 Integration Interoperability and Integration Division

UNCLASSIFIED

What does the Commander need?

Communicate Commander’s Intent

Build trust

Operate in the information environment

Create unity of effort

Possess speed of command

…not just share information

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

MPE Range of Military Operations

UNCLASSNETWORKS

US BICES-X

Classified Releasable FEDERATION OF MISSION NETWORKS

MN BICES

HA/DR MCO

MAX OMB

What is the Commander’s intent? What is the mission? Who are the partners? What information needs to be shared? What classification / releasability level(s) do you need to operate in?

LOW to HIGH3

CENTRIXS

Evolving to a Mission Partner Environment

4

Policy & Governance

National Connections

Training

Doctrine & TTP

Standards

Mission Threads

Web-browsing

Email with Attachment

VoIP

GAL Sharing

VTCoIP

Chat

CX-I

CIAV

CX-GCTF

Web-browsing

GAL Sharing

National Connections

Doctrine &

TTP

Standards

Mission ThreadsTraining

Policy & Governance

Email with

Attachment

VoIPVTCoIP

Chat

MPE- Theater Agnostic

VTCoIP Doctrine & TTP VoIP National

Connections

GAL Sharing Mission Threads Web-browsing

Chat CX-”X” Email with Attachment CIAV-like

Policy & Governance Standards Training

some assembly required

Pre-AMN

[ISAF] AMN - Theater Specific

MPE: Provides an overarching capability framework for CCMDs based on CONOPS, Doctrine, TTP, Policy, Governance, Common Standards, Training, Interoperability

UNCLASSIFIEDUNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

Validated Requirements [USA]

MPE Pedigree

Strengthening Security Relationships: Our relationships with mission partners are a critical component of our global engagement and support our collective security

Central to these efforts is strengthening global network of allies and partners. Combine capabilities with mission partners: form, evolve, dissolve, and re-form in

different arrangements in time and space Scalable: ranging from an individual unit enrolling the expertise of a

nongovernmental partner to multi-nation coalition operations.

Terms of Reference

ICD/CONOPS

JROCM 081-12

90-DayStudy

JROCM026-13

MPE Enduring(Tier 1) CDP

Joining Instructions

CJCSI 5128.01

DoDI 8110.01

Episodic MPE CDP

Both US MPE and NATO FMN efforts originated from the same requirement(s) document generated by COMIJC, endorsed by COMISAF and forwarded up the respective US and NATO chains of

command to CJCS and SACEUR for endorsement. Both sets of leadership endorsed the requirement.

MPE Definition: An operating environment enabling C2 for operational support planning and execution on a network infrastructure at a single security level with a common

language. (DoDI 8110.01)

UNCLASSIFIED

UNCLASSIFIED

MPE Enduring and Episodic Definitions

6 UNCLASSIFIED

“US and Mission Partners collaborate in Mission Partner Environment (MPE) Enduring environments day to day with the capability to transition to conducting operations within a MPE Episodic for any operation”

Application of MPE Tenets and Network Relationships and Characteristics differ

(known steady state relationships vs. unknown situation shaped coalition membership)

• MPE Enduring: Strategic Level (information sharing & planning)– Asynchronous and non-real time information sharing

– Persistent – time not a factor

– Specified Mission Partners (bilateral or multi-lateral “Communities of Interest)

– Combatant Command (CCMD) HQ capabilities for Mission Partner engagement/planning

– Technologically dependent

– Integrated with and enabled by Joint Information Environment (JIE)

• MPE Episodic: Operational to Tactical Level (Conduct Operations)– Synchronous and near-real-time, or real-time, conduct of operational mission tasks

– Episodic – time to establish always a factor

– Mission Focused (exercise or contingency operation)

– Unknown mission partners, emergent mission; unknown duration

– JTF and component capabilities for peer to peer Mission Partner operations

– US may not be lead; but must leverage JIE to contribute DOTMLPF, P & TTP to coalition

7

EnduringMPE“C”

Persistent CCDR level US-Centric Bi-lateral /Multi-lateral Specified Mission

Partners

Temporal CJTF level Commander centric

Unknown Coalition of the Willing

Joint Information Environment (JIE) – Enduring & Episodic MPE

LEGEND

National Classified Network (e.g. SIPRNet)National Unclassified Network (e.g. NIPRNet)

National Contribution (3rd Stack); National DOTMLPF-P, IA, Security

Enduring MPE ConnectionEpisodic MPE Federated Network; Commander accepts risk, sets rules

EpisodicMPE

CJTF

CFACCCFLCC

CFMCCCFSOCC

MP B

MP D

MP CMP Y

MP X

e.g. Existing bi-lateral and multi-lateral network relationships: MN BICES and other named network relationships, etc.

JIEConnectAccessShare

EnduringMPE“A”

MPG

MP Z

MP P

MP A

MP Q

Cross Security Level Exchange “Guard”

Rel to Mission or ExerciseCCMD

EnduringMPE“B”

MPG

CCMD

CCMD

SIPRNet and NIPRNet

MPG = Mission Partner Gateway

CCMD

Discussion: Do CENTRIXS-Maritime relationships and IT infrastructure investments reflect an MPE Enduring or MPE Episodic / NATO FMN use case? Or perhaps elements of both?

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

US BICES-XFTI

PACOM CENTCOM

EUCOM

TNE

TNETNE

SIPRNET TIER 1

Tier 1 SIPR connection currently

provides only CENTCOM users access to the

US BICES-X FTI

Mission Partner L

JIE

ConnectAccessShare

Mission Partner M

Mission Partner N

Mission Partner O

EnduringMPE

EnduringMPE“B”

MN BICES

Today’s MPE Enduring Environments

8

Mission Partners collaborate via a JIE Tier I environment but must be able to rapidly shift to operating within an Episodic Mission Partner Environment (MPE) framework as situation(s) dictate

Interim

Plus other existing bi-lateral and multi-lateral network relationships some of

which may not be directly connected to current DoD Networks or future JIE

MPG

MPG

EnduringMPE“A”

SIPRNet and NIPRNet

CCMD

CCMD

Collaborate and Share Information

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

Near Term - Episodic Capability

• Joining, Membership and Exit Instructions (JMEI)– Specific to mission or exercise, include all documents pertaining to event

• Policy⁻ Foundation of Trust-- Collective agreement by originating partners

• Management⁻ Pre-mission “coalition of willing” identification of, and training and equipping to agnostic standards

• “Third Stack”⁻ Provided by each Mission Network contributor

• Training & Education– Leadership direction, Culture change, and Practice

• Governance– Mission Commander-specific as shaped by partner(s)

• CIAV (mission specific activities per Cdr’s Guidance)⁻ Compare mission partner operational processes⁻ Deliberate “Do No Harm” coordinated change of DOTMLPF and TTP

9

MPE: Provides a consistent overarching capability framework for CCMDs based on CONOPS, Doctrine, TTP, Policy, Governance, Common Standards, Training, and Interoperability

EpisodicMPE

CJTF

CFACCCFLCC

CFMCCCFSOCC

MP B

MP D

MP CMP Y

MP X

MP Z

MP P

MP A

MP Q

Self provided National SecretSelf provided National UnclassifiedSelf provided Cross Security Level Information Exchange Guard

Conduct coalition operations, tasks, and activities in a “REL to mission” primary C2 network environment

[Up to] SECRET REL Mission

Specific C2 relationships for exercises and/or operations is NOT depicted

Specific C2 relationships for exercises and/or operations is NOT depicted

UNCLASSIFIED

UNCLASSIFIED

MPE and the Maritime Community

10 UNCLASSIFIED

• No major changes for the maritime community – MPE tenets have long been standard practice • Ability to reconfigure IT Infrastructure to connect to different mission networks while

deployed• Any changes dependent on role and function of embarked staffs, assigned forces and/or land-

based maritime HQ• CENTRIXS-Maritime not different from MPE, it is an MPE use case…..

• Culture already accepts concept of CENTRIXS – “X” infrastructure / hardware “repurposed” to fit the mission(s) at hand

• Biggest change – move fight (operational activities) off National-Only networks (e.g., US SIPRNet) when applicable• Employ releasable versions of existing C4ISR tools within “Rel to mission” mission network(s)• Data and information exist at any desired classification level and releasability caveat

• MPE and NATO FMN use case implementation and employment are scenario, partner and warfighting domain agnostic

“U.S. forces must learn to function routinely on CENTRIXS networks in the coalition environment and by exception on U.S. only networks. U.S. reliance on SIPR chat, SIPR email……limited coalition integration.” Excerpt BOLD ALLIGATOR 2012, Final Report

Back Up

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

Mission Partner Environment (MPE) JKO Courses

12

J3OP-US1277; Introduction to MPE J3OP-US1278; Planning an MPE Both MPE courses are available for US DoD, Multinational and interagency partners on JKO Direct via following link: https://jkodirect.jten.mil/Atlas2/faces/page/login/Login.seam?cid=21417

Note: US MPE documents, US MPE JMEI Joining Instructions, Operation DIRTY WIND video, links to JKO MPE courses are posted on Tidepedia in the FMN section: http://tide.act.nato.int/tidepedia/index.php?title=Main_Page

UNCLASSIFIED

UNCLASSIFIED

Mission Partner Environment (MPE)

Operational Context: As a standard practice, US Forces conduct many Warfighting operations via SIPRNET. In Afghanistan, this constrained the ability of US commanders to speak with immediacy to all operational commanders (mission partners).

• The need to mitigate risk and provide the commanders with strategic, operational and tactical flexibility spurred the development of the Afghanistan Mission Network (AMN) for coalition information sharing & get the “fight” off the SIPRNET

Lessons Learned & Guiding Principles:

• Operational imperative – unity of effort, enable communications with all mission partners to execute the Commander’s intent in a single security environment

• MPE is not a single network – it is a federation of networks & national systems

• There is no intent establish a new program of record; focus is on re-purposing existing materiel and non-materiel enablers and capabilities

• Alignment with NATO’s Federated Mission Networking (FMN)

“We’re one year away from forgetting everything we learned in Afghanistan.” Iron Major, USMC - Communications Officer

13

UNCLASSIFIED

UNCLASSIFIEDUNCLASSIFIED

• Lesson Learned: USA use of SIPRNet as primary C2 network during mission partner operations generates strategic, operational and tactical limitations:– Forces on different networks with inadequate cross-domain solutions resulted in poor

ops, planning and intelligence information exchange between NATO, U.S. and other partner forces in ISAF

– Non-materiel DOTMLPF, TTP and Policy solutions as or MORE important than materiel solutions

• Need for strategic to tactical human-to-human information exchange in a common language on same security and releasability level in real time – share by default; classify by exception

• Consistent DoD ability to employ in-place information sharing, TTP, and operational C4ISR to support both persistent and episodic (mission specific) operations with mission partners

• MPE leverages a “federation of sovereign C2 networks” created by the contribution of two or more nation “mission networks” to establish a mission specific enterprise in which all mission partners may operate as peers within a single classification and releasability policy

MPE Operational Context

14

Solution: Move coalition fight off of national networks [SIPRNet]

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

MPE Operational Metrics

MPE “What”• MPE is a framework, a concept of operations. A use case. MPE implementation is

represented by two or more mission partners agreeing to achieve unity of effort by joining trusted mission networks together to form a federation of networks composed of collective partner provided policy, transport, systems, applications, security, services and operational processes

MPE “So What”• Clearly communicate commander’s intent for desired operational effects with all mission

partners• Moves the fight off SIPR; allowing US and non-US formations, information, and data to

operate in the same battlespace

• Greater flexibility in mission and task organizing to fight more effectively

• US and partners fight with the equipment and TTPs they ALREADY own and train with

• Addresses CCMD persistent info sharing requirements and JTF episodic events

• Elevates mission partners to peers and recognizes their sovereignty

• Defines the level of trust & addresses cyber vulnerabilities upfrontMission Partner Advance Planning, Training, and Practice versus Crisis Reaction

UNCLASSIFIED

UNCLASSIFIED

The US MPE JMEI Joining Instructions were signed by LTG Mark Bowman, US Joint Staff J6 on 21 August 2014

• Distribution is to any and all partners• Content derived from ISAF AMN JMEI and draft NATO FMN Implementation

Plan (NFIP) Volume 2 and informed by lessons from COMBINED ENDEAVOR (CE) 2013 and planning for CE2014

• Governance and implementation within US DoD to be accomplished via:

• DoD 8110.1 Instruction (Mission Partner Environment (MPE) Information Sharing Capability Implementation for the DoD) signed 25 Nov 2014 by DoD CIO

• CJCSI* 5128.1 Mission Partner Environment Executive Steering Committee (MPE ESC) Governance and Management signed 1 October 2014

• Policy. It is US DoD policy that: MPE will serve as the framework for information sharing and conduct of coalition operational activities between DoD Components and Mission Partners

*CJCSI = Chairman of Joint Chiefs of Staff Instruction

MPE Implementation and Policy Within US DoD

UNCLASSIFIED

UNCLASSIFIED

NATO / ISAF UNCLASSIFIED

NATO / ISAF UNCLASSIFIED

18

UNCLASSIFIED

UNCLASSIFIED

Roles, Responsibilities and Relationship options within ANY coalition

• Eight options for mission partner participation within a coalition event. Only one involves “joining” by contributing and federating a mission network with a “core” mission network provided by a lead HQ or any other mission partner HQ

1) Contribute own network, resourced and governed by mission partner operating with a "Releasable to Coalition Event Name" caveat. – Required: Receipt and full compliance with coalition event lead HQ JMEI documents

2) Request purchase, lease or loan extension of coalition event lead HQ network to own forces/C2 nodes. – Compliance with network provider criteria is required, assumes network provider has already fully

complied with coalition event lead HQ JMEI document criteria.

– No direct compliance with lead coalition event HQ JMEI template documents required.

3) Request purchase, lease or loan extension of a network provided by another coalition event mission partner to own forces/C2 nodes. – Compliance with network provider criteria is required, assumes network provider has already fully

complied with coalition event lead HQ JMEI document criteria.

– No direct compliance with lead coalition event HQ JMEI template documents required.

“Federation of sovereign mission networks” key tenet of

MPE / FMN Concepts

UNCLASSIFIED

UNCLASSIFIED

• Note: Mission partners may utilize a coalition event federation of networks established to support a specific coalition event without selecting options 1-3:

– No direct or indirect compliance with lead coalition event HQ JMEI template documents required for any option below.

– Data and information may flow to and from option 4-6 mission partner representatives in a variety of different ways.

4) Embed a small or large force within another mission partner's force.

5) Send augmentees to coalition event HQ or lower echelon HQ or mission partner HQ as augmentees.

6) Send personnel to coalition event as observers.

7) Advocate and support coalition mission in world forums via a variety of communications media.

8) Some combination of options 4-7.

"Releasable to Event" caveat means information is releasable to all coalition event mission partners, not just those who contribute networks to a specific coalition federation of networks!! 19

Roles, Responsibilities and Relationship options within ANY coalition

20

UNCLASSIFIED

UNCLASSIFIED

MPE JMEI Task Execution Overview

• Eligibility: Who is eligible to contribute a mission network? Anyone, provided the ALL other [pre-]existing or original network contributing mission partners agree

– A mission partner wishing to contribute a network to a coalition federation of networks MUST be a formal member of a specific coalition event*

– Obvious, but……. Coalition event membership is a political decision with the only requirement being a statement of support for the coalition X event task/objective in a world forum.

– Coalition event membership carries no automatic requirement to contribute either personnel or equipment.

Coalition member ≠ Network Contributor

*Event = Exercise, experiment, test, training event, operational mission

Generic “Third Stack” at any US locationSIPRNet Secret

Rel USA OnlyThird Stack CENTRIXS-”X”

InfrastructureDifferent Crypto but may be same switch to connect to transport. MPE Tier 1 AND MPE Tier 2

Software location for Operating Systems, services

Data Storage.Separate location from Operating System!

Today only six collaboration services with a few exceptions

NIPRNet UNCLASSIFIED [Access] Rel USA Only

Wide variety of applications, services, portals, etc., to include six

collaboration services BUT very few “Warfighting tools”

Wide variety of applications, services, portals, etc., to include six

collaboration services and most “Warfighting tools”

JWICS, etc.

Work Stations: Virtual (VDI), Laptop, Desk Top.May be repurposed to any environment at low cost and effort.

Possible transport solution for long or short haul communication links as well as within an organization facility, base or platform

Repurpose workstations distribution per mission needs

Crypto CryptoCrypto

Crypto

CryptoCrypto

Crypto

CryptoCrypto

Crypto could be in one “box” or multiple boxes

To a user, six different “networks”, to a “6”

provider “one network”

May be replaced with releasable database per mission needs

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

MPE Use Case Concept: Two Levels

• Enduring = Strategic Levelo CCMD Phase 0 operations (can be utilized

during all operational phases)

o Persistent – time not a factor

o Specified mission partners

o CCMD HQ capability for mission partner planning/engagement/operations

• Episodic = Operational/Tactical Levelo CCMD-CJTF HQ Phases I-V operations

o Temporary – time always a factor/mission focused (exercise/contingency)

o Known and/or unknown mission partners

o CJTF HQ capability for mission partner operations

MPE Definition: An operating environment enabling C2 for operational support planning and execution on a network infrastructure at a single security level with a common language. (DoDI 8110.01)

UNCLASSIFIED

23

Persistent CCDR level US Centric Bi / Multi-lateral Specified M

ission Partners

Temporal CJTF level Com

mander centric Unknow

n Coalition of the Willing

Capabilities in Support of MPE Today

Existing bi / multi - lateral network relationshipsCMFC CMFP CENTRIXS-J CENTRIXS-K etc.

Interim Enduring MPE US BICES-X

EPISODIC ENDURING

CENTCOMPartner

Network

Bold Quest Mission Network

Austere Challenge Mission Environment

Afghan Mission Network

UNCLASSIFIED

UNCLASSIFIED

Federal Unclassified Partner users

Non DoD .gov/.org/ .com/.

net Partner users

Federal classified Partner users

MissionPartner

Transport

MP Unclass Network(s)

MP Classified Network(s)

MP Security

MP Desktop Infrastructure

Services

MP Clients

MP Information Environment(s)

Joint Information Environment [JIE]

Internet Access Point

NIPRnet

SIPRnet

JRSS

JRSS

Virtual Desktop Infrastructure

services

Virtual Enclaves

Multi-Enclave Client

Dedicated Client

Partner(s) voluntarily requesting classified mission network support

provided infrastructure and services by another willing partner

MPE Use Case Formula: US & Mission Partner Contributions

Mission Partner Environment [MPE]

Enduring COIsUS Led

Episodic Federation of Networks

US Led

US Contribution to MPE

MPGW-U(Unclassified)

MPGW-S(Secret)

MPGW-X(Bi / Multi – Lat)

Core Services- email w/attachments- Chat- Web browsing- VTCoIP- VOiP- Active Directory

Other Services- Access control- File share- Office automation- Print- Org messaging- Geo SA “COP”- Language translation

US BICES-X Cross Domain Enterprise Services

DISA Cross Domain Enterprise Services

Mission Specific Cross Domain Enterprise

Services

Operating With Mission Partners: Diplomacy, Policy, JMEI, Governing, Security, Doctrine, TTP

Enduring COIsPartner Led

Episodic Federation of Networks

Partner Led

MP Contribution(s) to MPE

Core Services- email w/attachments- Chat- Web browsing- VTCoIP- VOiP- Active Directory

Other Services- Access control- File share- Office automation- Print- Org messaging- Geo SA “COP”- Language translation

MP Cross Domain Services

MPE is a federation of mission networks where mission partners

“contribute” and use their own IT infrastructure, services, doctrine, and TTPs

based upon agreed to standards and protocols.

MPE ≥ US contribution + MP1 contribution + MP2 contribution + … + MPn contribution

Mission Thread Based Apps and

Services

Mission Thread Based Apps and

Services

UNCLASSIFIED

UNCLASSIFIED

JIE Capabilities Enable MPE Use Case

MN BICES CENTRIXS-Maritime

UNCLASSIFIED

UNCLASSIFIED

MPE and FMN• US MPE and NATO FMN born of the same requirement document from COMIJC

• MPE and FMN concepts and implementation plan documents developed in parallel with close coordination and collaboration

– Both leverage best practices & lessons from ISAF AMN federation, other missions & exercises

– Primary tenet of both: Apply current capabilities, equipment, skills, talent, and TTPs to a mission network

• #1 challenge: Coordinating national/organizational implementation policies in a “do no harm” manner to achieve “unity of effort” within a mission network in pursuit of coalition mission objectives (Goal of CE14 FPC, documented in CE14MN JMEI)

• MPE JMEI Joining Instructions and NFIP Volume 2 Instructions contain the same protocol standards, IA & Security criteria to create a trusted, protected and secure federation of mission networks and standards for connecting six partner “human to human collaboration” core services with each other

– US MPE and NFIP basic protocols, standards and trust criteria cross referenced and match those referenced and used in ISAF AMN, CE13, CE14, AC15, and BOLD QUEST 15.2 JMEI documents.

– ATO* for mission network contributions listed above demonstrated ability to meet foundational MPE JMEI Joining Instruction and NFIP Instruction protocols, standards and trust criteria

*ATO = Authority To Operate

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

MPE and FMN Parallel Efforts

“US MPE AND NATO FMN efforts are in parallel and are deliberately aligned

NATO FMN Implementation Plan (NFIP) Volume 1 NAC Approved 29 January 2015

US MPE JMEI Joining Instructions signed by, US Joint Staff Director J6 on 21 August 2104

Jolted Tactics

Mis

sion

Par

tner

En

viro

nmen

t

NATO IT Infrastructure Joint Information Environment

Mobile Computing

Strategy

Conn

ecte

d Fo

rces

Initi

ative

Fede

rate

d M

issi

on

Net

wor

king

Stra

tegi

cTa

ctica

lO

pera

tiona

l

CIAV

Ente

rpris

e &

Mis

sion

Ser

vice

s

US - NATO Strategic C2 Relationships & Partnerships

Nation / Mission Partner Funded

NAT

O C

omm

on F

unde

d

Similar Tools and Processes Support BothGlobal Integrated Operations and NATO Level of Ambition

Mobile CommunicationsEn

terp

rise

& M

issi

on S

ervi

ces

Glo

bal I

nteg

rate

d O

pera

tions

Mis

sion

Thr

eads

O

pera

tiona

l Pro

cess

es

XML Exchanges

XML Exchanges

Represents Any Nation or Organization

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

US MPE – NATO FMN Relationship

**All flags representative only – notional laydown

CJTF

CFACCCFLCC

CFMCCCFSOCC

• US MPE (Episodic) and NATO FMN use cases conceptually alike• MPE (US led mission) – FMN (NATO led mission)• Federation of “REL TO Mission” mission networks model also valid for a mission led by some other

entity• Episodic in nature (temporary, built for mission)• Nations agree to trust and security criteria to “connect” mission networks• Trusted and protected connections made through Joining, Membership, and Exiting Instructions

(JMEI)• Nations provide their own equipment and TTP “federate” capabilities and TTPs• Partners replicate releasable, operational capabilities and TTPs within respective mission networks

CJTF

CFACCCFLCC

CFMCCCFSOCC

NS WAN

MN BICES

NationsUS MPE Instance NATO FMN Instance

[Up to] SECRET REL Mission [Up to] SECRET REL Mission

Mission XMission Y

UNCLASSIFIED

UNCLASSIFIED

Key = Managed Deliberate Coordinated Change Among Willing PartnersUNCLASSIFIED

NATO Federated Mission Networking (FMN) and US Mission Partner Environment (MPE) Discussion Points

--Overall message: NATO FMN efforts and US MPE efforts are cut from the same cloth and look to achieve similar objectives with similar materiel and non-materiel tool sets

--Two key challenges within any partner entity:• Culture change and implementation of organizational versions of MPE or

FMN concept to facilitate use of organizational DOTMLPF and Policy in a trusted peer to peer coalition mission network environment

• Respective Program Office accreditation and governmental* approval for release of organizational capabilities and technologies for use in a mission partner environment with a specific set of mission partners

• Leverage reciprocity or streamline process to obtain or to reuse accreditations and release* of organizational capabilities and technologies for subsequent mission network environments with the same or different sets of mission partners

*e.g. US ITAR = International Trade and Arms Regulation

UNCLASSIFIED

UNCLASSIFIEDCannot “Surge” or “Pre-determine” Trust

• Unity of Effort and Speed of Command within a coalition force requires movement of coalition C5ISR operations and activities off of national or NATO specific security domains

• Federated Mission Networking and Mission Partner Environment frameworks offer option of an additional network environment specific to a mission/exercise/training event

– Use is complementary to, not in place of, existing national, NATO, or other multi-national network domains

– Each coalition is different-- leverage common agnostic protocols, standards to establish trusted and protected connections and compatibility criteria for six collaboration services as a consistent foundation for each different coalition mission network

• No new* equipment, no new skill sets, no new software, no new services, no new people required to implement FMN and MPE Framework—just a desire to participate and adjust to mission priorities

– Partners bring own DOTMLPF capabilities -- whatever they are

– COMBINED ENDEAVOR 2013 and 2014 achieved FMN and MPE objectives with current DOTMLPF and Policies

– All are treated the same—as peers-- capacity and size or organizational role does not matter to security, infrastructure and information assurance accreditation teams.

– *May require additional sets of current equipment/licenses if re-purposing of existing equipment/licenses is not available

• Most difficult challenge to coalition mission planning is coordination and adjustment of national and NATO policy implementations to establish mission/exercise specific policies

– Lessons from ISAF, CE2013, CE2014, IMMEDIATE RESPONSE 14 , CLEVER FERRET 14, any other coalition event planning process

– Culture and policy adjustments---perform coalition mission tasks on mission network, national business on national network, business with NGOs and others on Unclassified networks

• Practice and more practice is only tried and true method of increasing trust among mission partners and reducing time to implement trusted network-enabled information sharing arrangements.

– Trust can be gained by practice and familiarity with partner DOTMLPF and Policies—practice must include training audience J (A/G/N) 6’s!

NATO Federated Mission Networking (FMN) and US Mission Partner Environment (MPE) Discussion Points

UNCLASSIFIED

UNCLASSIFIED

Draft Operation ATLANTIC RESOLVE (OAR) Mission Network Relationships

• Joining Membership and Exiting Instructions (JMEI)⁻ Specific to OAR

• OAR Policy⁻ Foundation of Trust - Collective agreement by originating OAR partners

• “Third Stack”⁻ “REL OAR” DOTMLPF provided by each Mission Network contributor⁻ Network, capabilities, TTP employed therein to conduct OAR Ops

• Training & Education⁻ Leadership direction, Culture change, and Practice

• Governance⁻ Mission CDR specific as shaped by partner(s)

• CIAV (OAR specific activities per CDR’s Guidance)⁻ Compare OAR partner operational processes⁻ Deliberate “Do No Harm” coordinated change of DOTMLPF and TTP

32

Specific C2 relationships for OAR related exercises and/or operations is NOT depicted

SECRET REL OAR

CJTF

CFACCCFLCC

CFMCCCFSOCC

MP B

MP D

MP CMP Y

MP X

MP Z

MP P

MP A

MP Q

Self provided National SecretSelf provided National UnclassifiedSelf provided Cross Security Level Information Exchange Guard

MN BICES

Create OAR CoI?

Joining Membership and Exit Instruction (JMEI) Role in

Mission Partner Environment (MPE)and

Federated Mission Networking (FMN)

Train and Equip and Implementation Processes

Joint Staff JS J6 DDC5I IIDDeputy Director Cyber and C4 Integration Interoperability and Integration Division

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

Why JMEI?

34 UNCLASSIFIED

Non-Materiel (DOT_MLPF) and Policy contributions by NATO and Nations to the ISAF coalition are the most important contributing factors to ISAF mission success

The term “JMEI” came about as HQ ISAF and HQ ISAF Joint Command (IJC) needed to be able to provide nations [partners] wishing to contribute a national extension to ISAF AMN a consistent and repeatable package of holistic guidance and procedures

• COMISAF could not “mandate” systems interoperability for the various national C4ISR systems already in use, so the focus was on generating UNITY OF EFFORT by mandating human to human collaboration leveraging the most basic standards and technical protocols

• In addition to being able to protect and secure a network to ISAF mission policies the only other mandated criteria was to be able to communicate with other partners via six “core services”

• Web browsing, Chat (NATO Standard XMPP technical format mandated), Voice Over IP Telephone (VOIP), Video Tele-Conferencing over IP (VTCoIP), E-mail (with attachments), and Global Address List sharing

• The result was an evolution of mission technical and procedural documents from “a collection of workarounds” to a description of how to “federate” national mission network contributions into a trusted and protected federation of partner DOTMLPF capabilities and policies called “Afghan Mission Network”

• Operational and Functional ISAF documents also evolved to reflect operations as a unified coalition force vice a partnership of multiple independent forces

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

JMEI Defined

35 UNCLASSIFIED

Joining Membership and Exit Instructions

• Not a new idea but a new term generated by ISAF coalition forces

• Old terms: TTPs, SOPS, other named products resulting from exercise planning process or Crisis Action Planning (CAP) process

• In short, JMEI are a set of documents specific to a mission/exercise that range from technical implementation guidance to establishment of secure and trusted peer to peer communications to Mission[Exercise] CONOPS to OPORDERs and FRAGOs to political guidance to agreements between partners to Commander's Intent

• Operation [or Exercise] Orders, all OPORDER Annexes and any other document pertinent to a specific mission or exercise are a part of the collective set of documents referred to as “JMEI”

UNCLASSIFIED

UNCLASSIFIED

Repeatable JMEI for MPE / FMN

36 UNCLASSIFIED

Exchange and Access made “Practical, Efficient, and Effective” When all Participants are Conducting Operations or Training at the “same Security Classification and Releasability Level”

NATO and a significant number of nations came to same conclusion that operating as a part of a coalition was most effective and efficient when coalition partners were equal peers within a “mission network”

• NATO consideration included coalition partnerships with non-NATO member nations

In order to leverage the “best practices” of ISAF AMN to inform establishment of a future “mission network” while retaining the flexibility to adapt and adjust to any mission or mission partner set, basic technical elements of JMEI were separated from mission specific and temporal policy driven elements

Two categories of JMEI were born

• JMEI Joining Instructions – A set of mission agnostic documents that describe a nations’ view of the basic standards and compliancy criteria necessary to establish a trusted and secure network relationship as well as compatibility of six core collaboration services between network contributing mission partners (Repeatable and consistent across MPE and FMN documentation)

• Event specific JMEI – A set of documents are generated by mission/exercise lead HQ staff and mission partner reps to address all aspects of a specific coalition mission or exercise to include partner agreements regarding compatible implementation of national security, identify and access management and cyber defense policies within a federation of “mission networks”

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

MPE JMEI Joining Instructions Definition

37 UNCLASSIFIED

“MPE JMEI Joining Instructions contain the common “Lego Blocks” to enable more rapid establishment of trusted network relationships between any unique set of willing mission partners”

MPE JMEI Joining Instructions – A set of mission and partner agnostic documents that describe basic standards and compliancy criteria to establish a trusted and secure network relationship / connectivity between US and “coalition of the willing” partners as well as compatibility of six core collaboration services between network contributing mission partners

US objective: A consistent and repeatable set of MPE JMEI Joining Guidance across Combatant Commands (CCMD) and Services to describe minimum criteria for technical connections, IA, security, and six core collaboration services• Benefit: Services and mission partner ability to train and equip to a standard that is useful

regardless of which US CCMD or contributing mission partner is the lead or what mission is being executed

• Choice to train and equip forces to JMEI Joining Guidance is a sovereign decision—change(s) in MPE JMEI Joining Guidance managed and coordinated, not governed, among a “coalition of the willing”

• US DoD governs US train and equip processes• Content of US MPE JMEI Joining Instructions evolve in a consistent and complementary manner

with NATO Federated Mission Networking Implementation Plan Volume II Instructions• Partner MoDs govern respective train and equip processes• HQ NATO / Existing NATO processes govern train and equip processes to support NATO

Command Structure HQs

UNCLASSIFIED

UNCLASSIFIED

UNCLASSIFIED

Event Specific JMEI Definition

38 UNCLASSIFIED

Event Specific JMEI – A set of documents specific to a mission/exercise• Content ranges from technical implementation guidance to Mission/Exercise CONOPS to

OPORDERs/FRAGOs to political guidance to agreements between partners to Commander’s Intent• Starting point: Leverage and reference basic standards and compliancy criteria set in MPE JMEI

Joining Instructions [stated US goal is US MPE consistency with NATO FMN Volume II Instructions]

•Generated by mission/exercise lead HQ staff and mission partner reps to address all aspects of a specific coalition mission or exercise with mission partners under a JTF Commander lead, lead Nation, or exercise sponsor

• Event specific JMEI are the products of Crisis Action Planning or a the planning process associated with any exercise, test, experiment planning process

Benefit: Shape and drive collective DOTMLPF and Policy contributions to achieve mission objectives via generation of event specific policies, operational procedures, and technical configuration and security agreements tailored to address unique criteria and circumstances applicable to each mission and partner set• Commanders retain flexibility to shape and employ coalition force HQ and DOTMLPF of supporting

forces as they see fit to conduct operations in order to meet assigned objectives • Mission partners respond to acknowledged leadership role of whomever is mission or exercise

Commander without giving up sovereign rights and responsibilities

Risk to nation by joining XX Mission Network Federation is less than NOT joining in terms of resources, force protection, mission accomplishment

39

UNCLASSIFIED

UNCLASSIFIED

“Mission X” JMEI Development & Validation Flow Chart

Coalition Nations that provide

Combat Power, Logistics, BOG*, etc.

“Mission X”NetU.S. HQ &

Components“Mission X”

Partners

Systems, Applications,

Services, Operational

Processes

CIAV***

“Mission X” specific tasks and objectives

FMN CommunityStandardization

Exercise / OPLAN Validation

“Mission X” JMEI

J3s

“Mission X” TASKORD, OPORD, EXORD, CONOPS,

SOP, CDR Guidance and Intent, etc.

Feedback * Boots on the Ground**Joining, Membership & Exit Instructions***Coalition Interoperability, Assurance & Validation

Mission Partner Advance Planning versus Crisis Reaction

Systems, Applications,

Services, Mission Threads

US FMN 90 Day Study Figure 7

JMEI** MPE Joining Instructions

“Execution”

“Mission X” Exercise Planning or Crisis Action Planning Process

Secret REL to “Mission X”

US MPE JMEI Joining Instructions signed by JS J6 21 August 2014

US

MPE

Epi

sodi

c/N

ATO

FM

N U

se c

ase

The US MPE JMEI Joining Instructions were signed by LTG Mark Bowman, US Joint Staff J6 on 21 August 2104 • Distribution is to any and all partners• Governance and implementation within US DoD to be accomplished via DoD 8110.1

Instruction (Mission Partner Environment (MPE) Information Sharing Capability Implementation for the DoD) signed 25 Nov 2014 by DoD CIO and CJCSI* 5128.1 Mission Partner Environment Executive Steering Committee (MPE ESC) Governance and Management signed 1 October 2014

• Policy. It is DoD policy that: MPE will serve as the framework for operational information sharing between DoD Components and Mission Partners

Governance:• Internal national [US] business pertaining to training and equipping forces per MPE JMEI

Joining Instruction standards• Governance also reflects relationships and influence within a mission or an exercise

Management: • US MPE JMEI Joining Instructions are living documents with updates derived from feedback

received from implementation in coalition events• Change is via agreement, not consensus, among "coalition of the willing" to ensure coherent,

cooperative and deliberate change management process for minimum criteria for technical connections, IA, security, and six core services with as many partners as possible given sovereign decisions and political desires

• All changes deliberately made in close coordination with “coalition of the willing” contributors (Management vice Governance)

• Unilateral changes are/would be counter-productive*CJCSI = Chairman of Joint Chiefs of Staff Instruction

MPE Implementation / JMEI Change Management

UNCLASSIFIED

UNCLASSIFIED

41

CE14MN JMEIs

• Joining the CE Mission Network (15) • Policies for CEMN: PKI, Accreditation, IA, etc.

• Configuring the CE Mission Network (48)• Technical Guidance to provide trusted and protected environment needed to meet CE14

goals• Exiting the CE Mission Network (1)

• Guidance for protecting archived information post CE14• Procedures to gracefully exit CEMN federation

• CE Mission Network Membership (8)• NETOPS CONOPS, Cyber Security, Incident Reporting, IM/KM, Vulnerability Management,

etc.• Event Specific Instructions (38)

• Daily Battle Rhythm, ORBAT, Reporting Procedures, Trouble ticket, numbering convention, SCR VHF, HF UHF, SHF Allocation, Network diagrams, Tactical Data-link verification, Friendly Force Tracking systems verification, SATCOM Systems Information, etc.

• Admin (5)• Library of Terms, CE14 JMEI Structure, US MPE JMEI Joining Instructions

APAN link to CE14 Event JMEI documents: https://wss.apan.org/s/CE/CE14/JMEI/Forms/JMEI%20Grouped%20View.aspx

UNCLASSIFIED

UNCLASSIFIED

CE13 JMEI Trends and Statistics

Participants not following, not reading or an outside restriction (technical or policy) with the JMEI are the primary reasons for accreditation issues

*e.g. missing procedures, delayed equipment, weather-related problems, etc.

64%

36%

30%

17%

24%

11%

8%

8%

Compiled by CE13 C7 Assessment staffUNCLASSIFIED

UNCLASSIFIED

CE14 Assessment Trends and Statistics

Total JMEI Deficiencies

Mandatory ComplianceDeficiencies

Optional ComplianceDeficiencies

317 290 27

Optional Compliance Issues

8%

Mandatory Compliance Issues92%

Not Fol-lowed85%

Restricted 10%

Unclear5%

Not Followed 271 Restricted 31Unclear 15

JMEI Issues

Restricted = Conflicts with national policy or otherwise unable to comply

UNCLASSIFIED

UNCLASSIFIED

Compiled by CE14 C7 Assessment staff

Appendix 2 - Infrastructure Annex A- NIP Design & Router Configuration B- Internet Protocol (IP) Plan & Routing C- Multicast D- Border Gateway Protocol Routing E- Border Protection Systems F- Network Time Synchronization Services/Network Time Protocol (NTP) G- Data Transport Services (DTS) H- IP Security / Virtual Private Network (VPN) I- Domain Name Server (DNS) Summary

Master BQ MN 15.2 JMEIs

Appendix 3 - Core Services Annex A- Email Routing (Email) B- Voice over Internet Protocol (VoIP) C- Chat D- Global Address List (GAL) Synchronization E- Web Services (Secure FTP) / Shared File Directory

Appendix 1 - PolicyAnnexA- Statement of Security Compliance (ESSC) and Compliance QuestionnaireB- Interconnection Security Agreement (ISA)C- NCMP Authority to Connect Process D- HMP Authority to Connect Process E- Network Connection Approval Team (NCAT)F- Cyber and Physical Security PolicyG- Authentication, Authorization, AccountingH- Removable MediaI- Wireless PolicyJ- Incident Handling & ReportingK- Vulnerability Management L- Malicious Code Management

Appendix 5 - NetOps Annex A- MN Network Operations TTPB- Contingency Plan C - BQ 15-2 Helpdesk Incident Management SOP

Appendix 6 -Operations (BQ Mission Initiatives) AnnexA- NIE/BQ Execution Battle RhythmB- Command and Control (C2) Services (Systems)C- Force Tracking Systems (FTS) D- IAMDE- DaCASF- JFS JMTG- LVCH- Tactical Infrastructure Enterprise

Services (TIES) JCTDI- CISR (NOR/JDAT)J- Cyber (MND) K – NIE/BQ Joint Exercise Directive (JED)

JoiningMembership

Joining

Membership

Exiting

JoiningMembership

03 Sep 2015

JoiningMembership

JoiningMembership

Appendix 8 - Process Description Annex A- Planning and Joining the BQMN B- JMEI Development Process C- Risk Reduction Plan D- JMEI Change Process E- Acronym and Glossary of Terms F- Assessment/Instrumentation Plan

Appendix 7 - ExitAnnexA- Data Handling and Protection GuidanceB- Mission Network Exit Procedures

Appendix 4 - CommsAnnex A- Radio Circuit Plan B- Communications and Information Sys Security C- Tactical Data Links (TDL) (LINK 16/SADL/VMF)

JoiningMembership

Exit

BQ MN 15.2

JMEIs