DoD Enterprise Initiatives

1
DoD Enterprise Initiatives
Col Marcus Miller SAF/XCTX Maj Joe
Terrones SAF/XCTX 16 Apr 2009
2
Purpose

• Provide highlights of on-going DoD enterprise IT
  initiatives with potential impact to AF

3
BLUF

• DoD CIO leadership starting to focus on
  enterprise issues
• Initiatives encompass critical issues impacting
  warfighter, but dwell on access, sharing and
  consolidation for sake of cost effectiveness
• An emerging architecture being employed to help
  shape DoD-wide initiatives
• DoD-wide Tiger Team leading the architecture work
  (under AF leadership but with critical expertise
  from the entire department)
• Forums and initiatives offer opportunity to
  introduce promising AF solutions
• Jumpstarts the transformational path to reduce
  Service stovepipes

3
4
The DoD Enterprise Team
Led by DoD Dep CIO Members Service CIOs, DISA,
NSA, JS, OSD Staff Principals, IC Focus
Enterprise Services
Security and Identity Management Members
Services, DISA, JS, NII, NSA, JFCOM, TRANSCOM,
DMDC, IC
4
5
DoD Enterprise Initiatives

• Global Information Grid (GIG) 2.0
• Common Security Framework and End to End Assured
  Information Sharing
• Joint Naming Standard
• Enterprise Portal
• Active Directory (AD) Consolidation
• Enterprise Global Address List (GAL)
• Enterprise Email Consolidation
• Thin Client
• Collaboration
• Content Discovery
• Content Dissemination
• Task Management
• Geospatial Visualization
• To be discussed in greater detail

5
6
GIG 2.0
6
7
Security Framework Identity Management

• Problem Lack of common enterprise wide approach
  drives individual network enclaves and software
  applications to implement stove-piped
  authentication and authorization mechanisms that
  ultimately hinder information/service access and
  sharing

• Approach Develop an architectural framework
  that identifies and defines services, standards,
  common interfaces, components, and practices at
  the information sharing layer
• Impact
• Common lexicon
• Roles responsibilities
• Analyze gaps
• Understand solutions
• Shape implementations

8
Enterprise Portal

• Rationale
• Common Joint gateway to DoD content and services
• Brute force approach to info sharing
• Minimize redundant Service/Agency/COCOM portals
• Approach Leverage AKO to create Defense
  Knowledge OnLine (DKO)
• Concerns
• AF migration dependent upon business case not
  yet evident
• DKO functionality less than Global Combat Support
  System Air Force (GCSS-AF) precluding full
  replacement
• Transition to desired portal architecture
  (loosely coupled) unfunded
• AF users limited to those with need for access to
  Joint content
• Status
• Development of future architecture on-going
• Infrastructure build-out not currently supported
• Enterprise SharePoint considered as
  interim/migration path
• Concept of Operations and Strategy being
  re-examined

8
9
Defense Knowledge Online
9
10
Active Directory (AD) Architecture

• Problem
• Hundreds of disparate Microsoft Active Directory
  (AD) forests, domains, Operational Units (OUs)
• Difficult to provide enterprise NetOps
  visibility, C2 or configuration mgt
• Enterprise-wide information/service sharing and
  access hindered
• Approach
• Define target architecture that drives
  consolidation where appropriate
• Establish Enterprise Resource Forests for access
  to enterprise services
• Longer term plan for the consolidation of AD
  forests and domains
• Concerns
• Balancing efficiency and operational risk
• User authentication and inter-forest trust
  mechanisms
• Way Ahead/Status
• Architecture and implementation plans under
  review

10
11
Active Directory Consolidation
Active Directory Architecture
12
Enterprise Global Address List

• Problem Existing GAL is not fully populated
  across DoD
• Objective Establish a DoD wide GAL with a
  standard set of contact attributes
• Approach Leverage Joint Enterprise Directory
  Service (JEDS) as the hub with feeds and pulls
  from Service/COCOM directories
• Concerns
• Implementation timeframes
• Dependencies with AD consolidation in some
  Services
• Trustworthiness of attributes
• Way Ahead/Status
• Coordinating list of contact attributes
• Examining JEDS architecture
• Drafting policy memo

DoD-wide directory
12
13
Enterprise Email

• Opportunity Substantial cost savings possible
  with enterprise consolidation of existing
  Microsoft Exchange Servers with centrally
  administered, managed and support service
• Approach
• Collapse Microsoft Exchange Servers into DISA
  DECCs
• Focus initially on CONUS/persistently connected
  users
• Concerns
• Alignment with AFNET transformation
• User authentication
• Access from tactical edge
• Smart, user-friendly migration
• Competitive price point
• Balancing consolidation with
  performance
  and business case
• Way Ahead/Status
• Technical and migration planning on-going

Enterprise Email
13
14
Implementation Concept
DISA PM, Enterprise Email has overall
responsibility for the enterprise service
Enterprise E-Mail Service OPR DISA
Collapse Servers OPR DISA
Phase 3
Phase 1
Phase 2
DISA
100K Users
1M Users
DISA
5M Users
DISA Users first capacity 25K users

• Exchange servers in DoD Enterprise Resource AD
  Forest

• 5M users
• Achieve capabilities as outlined in 2012 E-Mail
  CONOPS GIG 2.0 CONOPS
• Support for Tactical LANs

TRANSCOM, Army, Capacity 100K users
Army/Others Capacity 1M users
2010-11
2009
14
(notional)
15
Enterprise E-Mail Address

• Most e-mail traffic in DoD is addressed using the
  Display name
• Lastname, Firstname MI GenQual Rank/Title
  PersType Citizenship DoDComp SubComp
• Bracketed fields omitted if no data present
• e.g. Smith, John E Jr Col MIL (USA) USAF ACC
• E-Mail for Life has exceptions (name change, MIL
  to RET, etc.)
• Unique user name _at_mail.mil (everyone gets this)
• e.g. firstname.middleinitial.lastname_at_mail.mi
  l
• Domain name aliasing based on service is being
  considered
• All fields pulled from data in JEDS
• Dual-role/Dual-CAC individuals will have dual
  accounts

16
Recap

• Global Information Grid (GIG) 2.0
• Common Security Framework and End to End Assured
  Information Sharing
• Joint Naming Standard
• Enterprise Portal
• Active Directory (AD) Consolidation
• Enterprise Global Address List (GAL)
• Enterprise Email Consolidation
• Thin Client
• Collaboration
• Content Discovery
• Content Dissemination
• Task Management
• Geospatial Visualization
• To be discussed in greater detail

16