NATO UNCLASSIFIED Releasable to ISAF CENTRIXS-ISAF: Phase 1 Overview Jesse Scott NC3A CAT 7: Core...

NATO UNCLASSIFIED Releasable to ISAF

CENTRIXS-ISAF:Phase 1 Overview

Jesse ScottNC3A CAT 7: Core Enterprise Services

Agenda

1. Transformation of Afghanistan Coalition Networks 2. CENTRIXS-ISAF Interconnection Overview 3. A Common Mission Network 4. Operational Use 5. Mission Applications & Interoperability 6. The Way Ahead (Phase 2, HoA, Additional Nations)

NATO UNCLASSIFIED Releasable to ISAF 2

Coalition Network Transformation

CENTRIXS-GCTF Cross-Domain Gateway (2006) Procured by US and NATO Allowing bi-directional e-mail and tracks through guards

UK Overtask Extension (2007) Extension of NATO CIS to the UK bases in the south Procured and deployed by the UK Managed by NATO and UK

CENTRIXS-ISAF Interconnection (2009) Procured by US and NATO (interconnection only) Direct connection of the two networks with no guards Connection managed by US and NATO


Overview of the ISAF Networks


FOC+ ISAF

NATO ISAF

NATO

NATOFOC+

KAF

KABUL

FOC+ primary connection

IOC connection

FOC+ SATCOMAnchor connection

FOC+ secondary connection

IOC infrastructurelocation

FOC+ infrastructurelocation

SATCOM anchorlocation

Gateway connection

FOC+

UK Overtask

UK Overtask infrastructure

CENTRIXS-ISAF

CENTRIXS-ISAFinfrastructure

4

Pre-CENTRIXS-ISAF IERs


SIPR

GCTF ISAF MS

OPERATIONAL

IN PROGRESS

REQUIRED

EM

AIL

FILE

(R)

VoIP

FMV

EMAILCHAT

CO

P

COP

CHAT

EMAIL

FILE (R)

FILE (G)

FMV

IER

IER

IER

CID

NE

NATO NS

CH

AT

EM

AIL

WE

B

CO

P

OVERTASKUK

VO

IP

NIT

B

Creation of new CENTRIXS-ISAF network

National expansion of ISAF Secret network (e.g. Overtask Model) was not feasible for U.S. (funding and support structures)

Implementation Approach Establish a new baseline (STIG = SIPRnet standards) and

upgrade the CENTRIXS network in order to stand up CENTRIXS-ISAF within Afghanistan.

Remove ~5% non-ISAF TCN users to a separate network Move CDG between CENTRIX-ISAF and CENTRIXS-

GCTF Establish two interconnection points (Kabul and KAF)

between CENTRIXS-ISAF and ISAF SecretNATO UNCLASSIFIED Releasable to ISAF 6

ISAF Current networks and Information Exchange Requirement

7

US SIPR

CENTRIXSGCTF

NATOISAF

OPERATIONAL

IN PROGRESS

REQUIRED

EM

AIL

FILE

(R)

FMV

CO

P

CH

AT

EM

AIL

FILE

FM

VIER

IER

IER

CID

NE

CENTRIXSISAF

NATO NS

EMAILCHATFILEFMV

OVERTASKUK

VO

IP

EM

AIL

WE

B

CO

P

VoIP

COP

COP

41 TCN Coalition Zone

NIT

B

CH

AT

VOIP

CHAT

EMAIL


Post-Phase 1 CXI Connectivity


ISAF Coalition Information Domain

ISAF SECRET(41 TCN)

CENTRIXS-ISAF(41 TCN)

CENTRIXS-GCTF

N ATO SECRET

(existing) CrossDomainGateways(eMail, Chat, VoIP)

eMail, one-way http one-way http

Service Provision Authority:NATO CIS Services Agency

Service Provision Authority:U.S. ARCENT

Common Mission Network

Command C2 Network

Strategic (JFC-B, ISAF HQ) NS / IS

Operational (IJC, RC, APOD) NS / ISCX-I, National

(CJOC)

Tactical (TF) CX-I, UK Overtask, National networks

The funding of NATO CIS into the operational level is more then traditionally expected from NATO (Balkans, Bi-SC AIS)


Common Mission Network

There is NO Common Mission Network for Afghanistan NATO still has two (classified) networks (NS + IS) National networks still used on tactical level

Germany Canada The Netherlands

However: ISAF Secret (+Overtask + CXI) is the largest network

throughout Afghanistan (with potentially more sites then the NATO static network)


Application Sources

NATO Applications Free of charge and available to all nations JOC Watch, JChat

NATO Application with COTS elements NATO application free of charge but component needs

investment from nation JOIIS (MapInfo), iGeoSIT, BOM/COPLM (Maria)

COTS Applications Requires significant investment from nation for

procurement, maintenance and development (!) JADOCS, WEBTAS, CIDNE

National Applications Release and support issues (FMS, ITAR etc.)


Application Interoperability

As part of the CXI Phase 2 discussions NATO and the US have agreed to:

NOT select a common set of applications but work on application/data operability

NATO (selected) applications will be used at HQ ISAF, IJC HQ and RC level.

National trusted/funded applications can be used at Tactical level

Individual connections between applications should be prevented as they are hard to manage. Interoperability servers should be used instead


Interoperability Points

Interoperability points will be setup to exchange information. NATO will use COPLM/BOM server (MIPDEM compliant) US will use the PAS Servers (Publish and Subscribe) UK will use ....

One of the key applications that we need as “Common Mission Application” is XMPP based Chat in support of C2. All nations have to agree on the protocol extensions so that

we remain interoperable (e.g. security labels for x-domain chat, geo-whiteboarding extensions for map based collaboration).


Proposed CXI Architecturewith C2 Interoperability Bus

14

US Integration SolutionsBased on PASS / DDS Server

C2 Interoperability Bus (CUR 355)JC3IEDM / NIIA Canonical Form

JOCWatchB

BOM

NIRIS

COPJOIIS

Intel FS

EVE CIED JISR 1

JADOCSGEO ü

ICC

IFTS

CORSOM

JADOCS

C2PC

ISRIS

FBCB2CPOF

CIDNE

GCCS

Others


Way Ahead

Expansion of the Common Mission Network More NATO/ISAF nations to extend the mission secret

network Achieve Data / Application Interoperability

CENTRIXS-ISAF Phase 2 Define & implement interoperability points

Increase the use of web based access Provide ISAF C2 Interoperability Bus and ISAF COP (CUR 355 and 264)

15NATO UNCLASSIFIED Releasable to ISAF

NATO UNCLASSIFIED Releasable to ISAF CENTRIXS-ISAF: Phase 1 Overview Jesse Scott NC3A CAT 7: Core...

Documents

Transcript of NATO UNCLASSIFIED Releasable to ISAF CENTRIXS-ISAF: Phase 1 Overview Jesse Scott NC3A CAT 7: Core...