110 likes | 208 Views
The IA Strategy Document Baked-in versus Brushed-on Integrating IA into Major Programs. Art King IBM Business Consulting Services Acquisition Team, DIAP 703.604.1480 ext. 104 arthur.king@osd.mil. 8 th Annual IA Workshop 3 February 2004 Atlanta, Georgia. Purpose.
E N D
The IA Strategy DocumentBaked-in versus Brushed-onIntegrating IA into Major Programs Art King IBM Business Consulting Services Acquisition Team, DIAP 703.604.1480 ext. 104 arthur.king@osd.mil 8th Annual IA Workshop 3 February 2004 Atlanta, Georgia
Purpose • Review the OSD guidance and template for an IA Strategy • Discuss the effectiveness of the guidance in facilitating meaningful IA Strategies • Identify opportunities for improvement
IA Strategy Guidance • Guidance to be published in the new Defense Acquisition Guidebook, currently in DAPWG review • Product of an NII/AT&L working group • IA strategy section describes • When an IA strategy is required • Recommended content • Recommended template • Submission and review requirements
Determining IA Strategy Requirement Source: DRAFT Defense Acquisition Guidebook
IA Strategy Elements • Program Category and Life Cycle Status: • Acquisition Category (ACAT) • Acquisition Life cycle phase • Next milestone decision • “Mission Critical” or “Mission Essential” • Mission Assurance Category (MAC) and Confidentiality Level: • As determined by information owner • Required for Baseline IA Controls
IA Strategy Elements • System Description: • High-level overview • Graphic (block diagram) of major elements/subsystems • High level description of IA architecture that will secure the system • Threat Assessment: • Describe method/source • Required for Baseline IA Controls • Risk Assessment: • Describe planned regimen of assessments • Add classified annex, if required
IA Strategy Elements • Information Assurance Requirements: • Describe sources of IA requirements (ORD, CDD, etc) • Describe method for ensuring requirements are addressed early in the acquisition process • Describe how requirements costs are included in budget • Acquisition Strategy: • Summary of how IA is addressed in the program’s overall acquisition strategy • Describe how the RFP: • Includes IA requirements in performance or technical specification • Requires personnel trained in IA • Address COTS IA or IA-Enabled products and approach towards NSTISSP 11 compliance
IA Strategy Elements • DITSCAP: • Identify DAA, CA, User Rep • Provide rough DITSCAP timeline • Will C&A be through DCID 6/3 (SCI material)? • IA Testing: • Describe how IA testing is integrated in TEMP • IA Shortfalls: • Identify any known significant shortfalls • Proposed approach to correct or mitigate • Add classified annex, if required
IA Strategy Elements • Policy/DirectivesDITSCAP: • Identify primary IA policy guidance employed by the program • Relevant Associated Program Documents: • Identify specific version of applicable CRD/ORD/ICD/CDD/CPD • Identify specific version of applicable C4ISP • IA Point of Contact: • Preferably, the IA Manager for program
For your consideration • Is the Strategy content requested sufficient? • Recommendations to improve?
DIAP Acquisition TeamPoints of Contact Mr. Eustace King ASD(NII)/DIAP-Technologies and Capabilities (703) 602-9969 eustace.king@osd.mil Mr. Art King (IBM) (703) 604-1480 ext. 104 arthur.king@osd.mil Mr. Dominic Cussatt (IBM) (703) 604-1480 ext. 119 Dominic.cussatt.ctr@osd.mil