Intelligence Community Chief Information Office IC CIO

1
Intelligence Community System for Information
Sharing (ICSIS) to the Secure E-Business
Summit 7 May 2001
2
ICSIS Responsive to the DCIs Vision A
Unified IC optimized to provide a decisive
information advantage.. Led by the IC Chief
Information Officer (CIO) and the IC CIOs
Executive Council Engineered by the
Intelligence Collaborative Operations Network
(ICON) Office 7 May 2001
3
What ICON Does

• provides analysis and system engineering to
  define the communications and information system
  architectures and their implementation for the
  future intelligence environment.

ICON Charter, 13 October 1999
4
IC System for Information Sharing

• ICSIS Background
• ICSIS Overview
• Coming Attractions

5
ICSIS Background
4-10-00 DDCI/CM chaired Meeting 4-28-00
ICCIO Direction to Program 6-6-00 ICCIO EC
Approved Work Plan
After 4-28-00

• Focus on
• Architecture
• IC CIO EC Priorities
• Congressionally Directed Actions
• IC Roadmap

6
The Driving Requirement To develop an IC
information technology architecture that provides
users secure access to information across the
Community comparable to that currently provided
within individual agencies
7
Key Requirements

• Ability to collaborate securely and synchronously
  from the desktop
• IC
• Customers, Partners, Supporters
• Ability to share applications and information
  securely

8
Early Alternatives
Option 3
Option 2
Option 0
Option 1
9
ICSIS Overview
Organization Internal Space
Organization Internal Space
Agency CA
Organization Internal Space
Organization Shared Space
IA Sensors
Collaboration
SCI Community Space
Data Conversion
Collaboration
TSABI Approved Controlled Interface
Collateral Space
PKI
Collateral Applications
10
Key Features of ICSIS

• Modeled on virtual and physical centralization of
  services of common concern
• Implements Worldwide Web and Internet construct
• Implements IC public key infrastructure and
  reinforces need-to-know
• Standardizes product markup
• Provides one-stop-shop for services
  communications
• People share knowledge and assets securely and
  freely

11
Inside the Organization Internal Space

• Information and applications normally not
  shared with external organizations

• Access based on IA parameters
• and need to know
• Collaboration is in-house
• Inter- organization communications
• tightly controlled
• Information organizationally
• sensitive
• Trust is not an accepted risk
• Resource protection and control
• is by the owner

12
Inside the Organization Shared Space

• Information and applications shared with
  trusted business partners

• Access based on IA parameters
• and need to know
• Collaboration is in-house
• Inter-organization communications
• tightly controlled
• Information is less organizationally
• sensitive
• Trust may be an accepted risk
• Resource protection and control
• is by the owner

13
Inside the Community Space

• Information and applications are routinely
  shared among the IC and its customers

• Access based on IA parameters
• and need to know
• Collaboration is IC-wide
• Inter-organization communications
• is routine
• Information is not organizationally
• sensitive
• Trust is an accepted risk
• Resource protection and control
• is exercised by the CSP on behalf
• of the owner

14
Inside the Collateral Community Space

• Intelligence and applications, plus other data
  holdings deemed appropriate by the collateral
  space owners

Shared Intelligence Data
Community Shared Data
Both DoD and non-DoD
PKI
Collateral Space
Shared Intelligence Applications
15
ICDC Approved Action Plan (1 of 2 )

• By IC CIO Executive Council
• Identify and provide to actionees all policy and
  structural changes required to implement the
  recommended option (February 2001)
• Create policy to require development of
  web-based, PKI-enabled applications for inclusion
  within the IC Space (March 2001)
• Establish Conops and refine supporting technical
  architecture for recommended option (June 2001)
• Estimate program costs of the recommended option
  (June 2001)
• Create access management framework, integrating
  FSD, PKI, network policies, uniform document
  standards (June 2001)
• By IC Security Directors Working Group
• Develop uniform interpretation of DCID 6/4, 1/19,
  1/21 and 6/3 standards for protecting and
  accessing IC Space (June 2001)
• Develop uniform practices for foreign national
  access to information, facilities, and systems
  (June 2001)

16
ICDC Approved Action Plan (2 of 2)

• By ADCIs for AP and Collection
• Develop a business model and governance rules for
  guiding cross-agency collection and analysis
  collaboration and data use (March 2001)
• Establish a process for vetting potential
  collaborative workflows and objectives which
  obtains early stakeholders sponsorship (March
  2001)
• Develop and promulgate initial production
  standards for use within the IC Space, to include
  standard formats and data labeling (June 2001)
• By CMS
• Review and sponsor required program/budget
  changes (July 2001)
• By ICDC/ICPC
• Review and adopt, as appropriate, required
  business, policy, and structural changes
  developed by other actionees (April/June 2001)

17
Where Do We Want To Be?

• Secure, synchronous collaboration
• Data access from anywhere at any time
• Fully interoperable data stores
• Streamlined flow from collector to producer to
  customer aided by intelligent applications
• Secure push and pull between spaces
• Analytic tools and digital production support

18
Things Too Hard To Do In Phase One?

• Synchronous audio/video collaboration at the
  desktop
• An all inclusive two-way interface between SCI
  and Collateral Spaces
• Ability to dynamically modify security controls
  managed by intelligent programs
• Search and access applications based on
  artificial intelligence and intelligent agents

19
What is Phase One?

• Infrastructure that issues and maintains
  certificates for all ICSIS users
• Full Service directories that include and can be
  used by all ICSIS users
• S/MIME IC Email systems for exchange of
  information up through B level
• Controlled TSABI approved interface(s) to
  collateral space

20
What is Phase One?

• An agreed set of databases and applications
  hosted in either Community or Organization Shared
  space
• Collaboration tool kit
• Web-enabled applications and databases
• Meta data and markup standards defined and
  implementation started
• With agreed level of content and security
  markings
• A CSP infrastructure to support Phase One
• A communications infrastructure with bandwidth
  adequate to support Phase One capabilities

21
What is Phase One?

• System engineering and integrations support
  organization for defining interfaces and
  maintaining standards
• A governance mechanism for overseeing day-to-day
  operations as well as future enhancements

22
Coming Attractions

• Phase One Trades, Mid-May thru Mid-June 2001
• ICDC, July 2001