1 COPC/CSAB JAG-CCM Status Updates and Recommendations Prepared for: CSAB Spring Meeting April 15, 2009 By: CCM Team version

2 Outline CCM Team Membership Status Updates and Recommendations –Encryption requirements for Controlled Unclassified Information (CUI) –Development of the Next Generation COPC Enterprise Network –Requirements gathering across the COPC partners Summary

3 CCM Team MemberOrganization Charles AbelAir Force/AFWA/A6 Kenneth BarnettOFCM Luis Cano*NOAA/NWS/NCEP/NCO Patrick GregoryNOAA-NESDIS-OCIO Craig HegemannNOAA/NWS/OCIO/TOC Seyed HosseiniNOAA/NESDIS/OSDPD/IPD Ben KygerNOAA/NWS/NCEP/NCO Sherryl PanekNavy/FNMOC Casey SwansonNavy/CNMOC/N6 VacantNavy/NAVO *JAG-CCM Chair

4 Encryption Requirements for Controlled Unclassified Information (CUI) COPC Action Item : JAG CCM will provide analysis of recent changes to DoD IA requirements regarding the category “unclassified but sensitive” and determine if this new guidance requires encryption for meteorological data. AFWA TD will capture the new guidance and provide to JAG CCM. [NUOPC related] Priority: (H) Advocate: JAG/CCM – [Luis Cano (Chair)] Suspense: Spring 2009 CSAB meeting or (April 1, 2009). Status as of 19 March 2009: Open.

5 Encryption Requirements for Controlled Unclassified Information (CUI) Status: –CUI analysis completed Information designated as CUI requires encryption for electronic transmission Encryption shall be implemented in accordance with FIPS 140-2, Security Level 1 Five years to implement CUI framework - due May 2013 Encryption requirements captured within “Requirements Gathering Across COPC Partners” action item See next slide for COPC partners’ CUI encryption status Recommendation: –close Action Item

6 Encryption Requirements for Controlled Unclassified Information (continued) Data SourceData DestinationProtocol*Meets CUI encryption requirement? AFWAFNMOCFTPN AFWANWSTGIP SocketsN FNMOCNWSTGHTTPSY FNMOCAFWAFTPN FNMOCNAVOFTPN NAVOFNMOCFTPN NAVONWSTGFTPN NAVONWSTGSFTPY NESDISAFWAFTPN NESDISFNMOCFTPN NESDISNAVOFTPN NWSTGAFWAFTPN NWSTGAFWAIP SocketsN NWSTGFNMOCFTPN Assumption: COPC shared data designated as CUI (*Currently, no data is designated as CUI)

7 Development of the Next Generation COPC Enterprise Network COPC Action Item : JAG CCM shall coordinate the development of the next generation COPC shared network infrastructure with DoD and NOAA IT leadership. The JAG CCM shall leverage projects currently underway that are planning a NOAANet-DoD enterprise network capability. [NUOPC related] Priority: (M) Advocate: JAG/CCM – [Craig Hegemann] Suspense: Spring 2009 CSAB meeting or (April 1, 2009).

8 Development of the Next Generation COPC Enterprise Network Due Date MilestonesAssigned toStatusComments 4/13/09NWS TOC meet with DISA to connect with appropriate level of DISA leadership NWS TOC DirectorComplete NWS TOC and DISA establish strategic alliance to work NOAANet-DoD enterprise network program 5/01/09NWS TOC coordinate draft high-level milestones and schedule NWS TOC DirectorOpen High level milestones and schedule provides insight to the development and deployment of NOAANet-DoD enterprise network capabilities Milestones and schedule to be presented at the COPC meeting scheduled for May 13-14, 2009

9 Development of the Next Generation COPC Enterprise Network Status: –actively working action item Recommendation: –keep action item open

10 Requirements Gathering Across COPC Partners COPC Action Item : JAG CCM will provide an ongoing process to capture and coordinate telecommunication requirements across COPC partners. These requirements would include the size of the data, when the data needs to be transmitted, when the data needs to be received, which COPC partner will send the data, which COPC partner will receive the data, the schedule of when new data will or needs to be enabled, encryption requirements, other data restrictions, and related COPC business functions. As a follow-on action item, this process would be used to validate technical designs and resource estimates for new network infrastructure initiatives. This process would provide COPC continuing value by supporting network capacity management for existing infrastructure and help justify funding requests for future network upgrades. [NUOPC related] Priority: (M) Advocate: JAG/CCM – [Luis Cano (Chair)] Suspense: Spring 2009 CSAB meeting or (April 1, 2009).

11 Requirements Gathering Across COPC Partners Due Date MilestonesAssigned to StatusComments 2/26/09CCM meet with COPC Senior IT Leadership CCM, OFCM and COPC Senior IT Leadership Complete CCM communicated issue of lack of progress in providing needed network infrastructure for COPC missions CCM assigned action to initiate shared network requirements data-call to COPC CIOs 3/19/09OFCM send shared network requirements data- call to COPC CIOs CCM and OFCM Complete CCM coordinated design of requirements template with DISA Template design captures annual requirements for 5-years into future 4/24/09COPC CIOs send completed shared network requirements template to OFCM CIOsOn-track 4/2/09: Navy and Air force actively working data-call. 4/13/09: Acknowledgment from NESDIS of working on data call 4/13/09: NWS TOC to leverage climate data requirements and coordinate with NESDIS OCIO 5/29/09CCM analyze requirements and report-out to CSAB, COPC CIOs and DISA CCM and OFCM Open COPC CIOs and DISA use requirements to provide COPC shared network infrastructure AnnualUpdate COPC shared network requirements using annual data-call process CCM, OFCM and COPC CIOs Open Annually update 5-year projection of COPC shared network requirements and share with COPC CIOs and DISA

12 Requirements Gathering Across COPC Partners Status: –actively working action item Recommendation: –keep action item open

13 Summary COPC Action ItemStatusRecommendation Encryption Requirements for Controlled Unclassified Information CompleteClose action item Development of the Next Generation COPC Enterprise Network On trackKeep action item open Requirements Gathering Across COPC Partners On trackKeep action item open