search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
IN SYNC, SECURE AND AWARE


prioritizing cyber gaps and distributing requirements across program executive offices (PEOs) for execution.


Working with the ASA(ALT) Cyber Task Force and the requirements community are three PEOs with key roles in sup- porting these future technologies: PEO Command, Control


and Communica- BUILDING BRIDGES


Defense Secretary Ashton B. Carter addresses the U.S. Cyber Command workforce at Fort Meade, MD, March 13. The cyber frontier is challenging the Army acquisition and requirements communities as they work to equip and train cyber forces for this complex threat. (DOD photo by PO2 Sean Hurt)


Recently, the director of national intel- ligence named the cyber threat as the number


one strategic threat to the


United States, placing it above terror- ism for the first time since 9/11. April saw the publication of the DOD Cyber Strategy, which provides five prioritized strategic goals and objectives for DOD’s cyber activities and mission to achieve over the next five years.


In this urgent but fiscally constrained environment, it is critical to properly frame the Army’s cyber requirements and capabilities, as well as to ensure that they are flexible enough to support the inher- ent challenges of this domain.


TEAMING UP FOR THE CYBER REALM Creating requirements focused specifi- cally on cyber reinforces the need for information security and resilience throughout the program life cycle. To do this, the Army is using the Com- mon Operating Environment (COE) as


22


a vehicle for increased security in newer systems, while also establishing security mechanisms


for legacy systems. Tis


strategy necessitates a holistic approach to acquisition and requirements that can adapt to address changing, emerging and unknown threats.


To prepare well for these threats, while also protecting and defending DOD’s information network and data, the Army materiel development and cyber operational communities are build- ing cyber requirements to meet today’s needs. Tis team includes the U.S. Army Cyber Command (ARCYBER), the U.S. Army Training and Doctrine Command (TRADOC) Cyber Center of Excellence, the acquisition community and a variety of partners from industry and academia. From the acquisition side, the Office of the Assistant Secretary of the Army for Acquisition, Logistics and Technology (ASA(ALT)) System of Systems Engineer- ing and Integration Directorate’s Cyber Acquisition Task Force is responsible for


President Barack Obama has compared the lack of boundaries found in cyberspace to a game of basketball, where—unlike in football or baseball— there is no clear line between offense and defense. Instead, the roles switch constantly.


tions – Tactical (C3T) leads in defense of the tactical network; PEO Enterprise Information Systems (EIS) leads in defense of the enterprise network; and PEO Intelligence, Electronic Warfare and Sensors (IEW&S) leads in offensive cyber efforts. Tis collaboration—along with those formed with other organiza- tions that support cyberspace operations, such as the intelligence community, international alliances and joint and coalition forces—is key to employing a more defendable network architecture in the joint information environment.


Army AL&T Magazine


July-September 2015


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