DISA Operations Testing

Perspective

Mr. Ron Stimeare

Defense Information Systems Agency

Operations Technical Director

29 Nov 2012

v1.2

DISA Test and Evaluation Efforts

DISA has extensive test and evaluation programs under way

DISA Acquisition organizations

• Perform developmental testing

Joint Interoperability Test Command (JITC)

• Conducts testing and operational evaluations for suitability, effectiveness, security, and interoperability; certifies IT capabilities for joint interoperability

DISA Field Security Office (FSO)

• Conducts security compliance testing

3 v1.2

►DISA is designated as a Combat Support Agency (Title X, US Code)

►Plans, engineers, acquires, tests, fields and supports global net-centric

information and communications solutions (DODD 5105.19)

AGENCIES COALITIONS

CENTCOM

DISA Central

ISAF

Contracting

AFGHANISTAN

IRAQ

PACOM

KOREA

DISA Pacific

USFK

OKI JAPAN HAW

GUAM

Contracting

ALASKA

DECC

NORTHCOM

DISA NORTHCOM

SOUTHCOM

DISA SOUTHCOM

AFRICOM

DISA AFRICOM

EUCOM

DISA Europe

DECC NATO

SOCOM

DISA SOCOM

JSOC

TRANSCOM

DISA TRANSCOM

SUPPORT

WHITE HOUSE

CJCS

DISA Joint Staff

SECDEF

DoD CIO

SUPPORT SUPPORT

STRATCOM

DISA STRATCOM

CYBERCOM

DSE CYBERCOM

Defense Spectrum

Organization

Joint Interoperability

Test Command

SUPPORT

Defense IT Contracting

Organization

COMMAND

COMMAND

WHCA

Contracting

DISA

DISA Operations Environment

ARMY

NAVY

AIR FORCE

MARINES

SUPPORT

Elements of Operational Integration Testing

Validate integration of process, people, and technologies

ITSM Processes

Cyber Ops Technical Toolsets

Cyber Ops Organizations

Governance Board

Reviews

Needs of the Operational Community

Understanding Operational Context of Testing is Essential

Broadened view of “Interoperability”

• Encompass both technical and operational integration, to include C2 and SA for decision-makers

Integrate Cyber, Intel, and non-Cyber Ops

• Cyber Ops info, Intel ,and Ops info from Land/Air/Sea/Space domains integrated in decision-maker SA

• Example: Cyber module in GCCS

Shared test data for more rapid and efficient fieldings

• Leverage reciprocity by testing units once and sharing test data to avoid expense/delay of redundant tests

Test ‘services’ not ‘boxes’

• Ask the operational “so what” when testing: how is end-to-end assured delivery impacted? How is the user affected? How is the service operator affected?

Help operators see what is about to happen

• Test for proactive detection of actionable events before users are impacted

Prioritize with risk management

• Not everything can be tested; use risk management to prioritize testing resources

Cross Community Boundaries

• Test for integration not just across technical boundaries, but across community and authority boundaries

Test results in the language of operators

• Provide concise risk-level assessments and mitigation options

A Combat Support Agency A Combat Support Agency

7

Combat Support Agency