50 likes | 173 Vues
This overview discusses critical initiatives from the Department of Defense (DoD), focusing on the implementation of Public Key Infrastructure (PKI) to secure non-public NIPRNet web servers and enforce Smart Card Logon (SCL) protocols by July 2006. It outlines the directives of the Joint Task Force (JTF) for Global Network Operations, which mandates that all non-PK enabled systems must transition to PKI. Additionally, it addresses the upcoming FTP replacement measures, including blocking FTP ports and transitioning to Secure FTP solutions that meet FIPS 140-2 compliance.
E N D
DoD Network InitiativesCEISC13 Apr 2006 Mr. Walter Coley Ms. Kathy Cotton AFWA/SCM Distribution Authorized to U.S. Government Agencies and their Contractors only
Overview • Public Key Infrastructure (PKI) • FTP Replacement • Discussion
Public Key InfrastructureDoD Mandates • Joint Task Force (JTF) – Global Network Operations (GNO) Communications Tasking Order (CTO) 06-02 • By 1 July 2006 • PK Enable all non-public NIPRNet web servers • By 31 July 2006 • Implement Smart Card Logon (SCL) to NIPRNet • Identify all systems not PK enabled • DoD contractors off-site must acquire certificates from an approved DoD External Certificate Authority (ECA) • New password and best practice guidance for “those systems and user populations unable to achieve CAC/PKI logon”
FTP Replacement • FTP Ports (20, 21) will be blocked by DISA on 12/15/06 • Applies to all FTP traffic between DoD and non-DoD enclaves • Several options being considered • Establishing servers in the DoD DMZ • Migrate customers/data providers to Secure FTP • Must be FIPS 140-2 compliant, support scripting, and API • Commercial and Open Source alternatives being evaluated • Obtain waivers for non-DoD customers • Solution is being worked as a high priority