YOU NEED TO KNOW
Acquisition Regulation Supplement Case 2008-D028, Safeguarding Unclassified Infor- mation. This case would add a new subpart and associated contract clauses for the safeguarding, proper handling, and cyber intrusion reporting of unclassified DOD information that resides on or transits con- tractors’ unclassified information systems.
DOD published notice of this case in the Federal Register on March 3, 2010, and held an initial public hearing on it on April 22, 2010.
Categories of DOD information that would require protection include: critical program information (CPI); informa- tion subject to export control under International Traffic in Arms Regulations and Export Administration regulations; personally identifiable information; and other categories of CUI.
Among other things, contractors would be required to:
• Implement information security in any project, enterprise, or company-wide unclassified information technology system using specified minimum secu- rity controls.
• Report to DOD any relevant cyber intrusion events.
• Support the forensic analysis of those data for purposes of conducting assess- ments of damage to acquisition and other programs.
• Procure and use only DOD-approved identity authentication credentials to, for example, receive emails from Army PMs containing data files with CPI.
• Include the substance of this clause in certain subcontracts.
TRUSTED DEFENSE SYSTEMS Another key policy focus for mitigating risk of losing critical unclassified infor- mation is the effort to ensure trusted
62 Army AL&T Magazine
defense systems by managing the supply chain risk for those systems, particularly to protect mission-critical software and hardware components. Mission-critical functionality of DOD’s systems and net- works extensively leverages commercial, globally interconnected, globally sourced information and communications tech- nologies. Consequently, adversaries have more opportunities to corrupt technolo- gies, introduce malicious code into the supply chain, and otherwise gain access to the Department’s military systems and networks.
The policy framework to address this challenge is established by DTM 09-016, Supply Chain Risk Management (SCRM) to Improve the Integrity of Components Used in DoD Systems. During development of a system, the PM determines which soft- ware and hardware components within the system are critical and then determines, based on identified threat and vulnerabil- ity, how to protect it with the support of
COMPUTER DEFENSE ACTION
DODI 5205.13 establishes the policy framework for DOD’s main effort to work with DIB partners within a pilot program to mitigate the risk of losing sensitive unclassified program information to cyber attacks. Here, Jerod Young, an analyst in a Current Operations Cell, examines data during a computer defense action in Europe. (U.S. Army photo.)
experts from various disciplines, including counterintelligence, intelligence, security, systems engineering, and policy.
This policy establishes a process that involves extensive collaboration among the DOD components to manage these risks. Army program executive officers (PEOs) and PMs engage in this process as part of the development and updating of their program protection plans at each milestone review.
KEY LEGISLATION The congressional defense committees are playing a critical role in identifying and highlighting the need to improve cyber security. Two particular provisions in the NDAA for FY11 pertain to acquisition and address the issues outlined above. They are:
• Section 806, Requirements for Infor- mation Relating to Supply Chain Risk. Congress has given DOD new authority
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136
