 


Th e DOD Cyber Strategy


: Strategic Goals


  


   


  


  


FIVE STRATEGIC GOALS


To mitigate risks and defend U.S. interests in the current and future security environment, the DOD Cyber Strategy outlines five strategic goals and specific objectives for its activities and missions. (SOURCE: PEO C3T)


DIVIDE AND CONQUER From weapon systems to communica- tions capabilities, the Army must lock down its systems even more securely than today. Te acquisition community has been responding directly to its customer, the Soldier, by addressing ARCYBER operational needs statements as they come in—even as we are establishing the resources and processes that will gov- ern the long-term acquisition of cyber defense and warfare capabilities.


To aid in improved weapon systems cybersecurity, capabilities for the Army’s newly constituted cyber mission forces and resilience for networks, the acquisi- tion and requirements communities are working together to create new cyber requirements. Tese include capability development documents (CDDs) and


initial capabilities documents (ICDs), in various stages of development, that focus on defensive cyberspace operations, cyber


situational awareness and offen-


sive cyberspace operations. Leveraging multiple cyber requirements documents, instead of focusing on a single document, is by design and meant to instill a new level of adaptability as needs change and new threats emerge.


Te mechanism that allows this multi- pronged approach, whereby several requirements documents work together holistically, is known as the Informa- tion Technology (IT) Box. Introduced by the DOD in 2014, the IT Box model allows approval for an overarching requirement—cyber, for example—then includes individual information system requirements documents for defensive


cyber operations, cyber situational aware- ness and offensive cyber operations that would only need approval at the service level instead of the joint level. Te intent of the IT Box approach is to provide agility and flexibility while ensuring better-integrated cyber solutions than we have seen in the past.


In addition to the overarching require- ments documents for cyber capabilities, the Office of the Secretary of Defense is imposing new cyber requirements at the individual system level, creating a cyber survivability key performance parameter to help programs increase cybersecurity in their baselines.


In pulling together the requirements documents, TRADOC and ASA(ALT) are also, for the first time, including


ASC.ARMY.MIL 23


ACQUISITION


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  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156