DIGITAL TRANSFORMATION


accordance with cybersecurity policies. DevSecOps is part of the application and workloads pillar of the DOD ZT framework. It is imperative that these interoperable capabilities work together to create a manageable enterprise, thus maxi- mizing the Army’s current investments in this space.


LOCK IT DOWN A key pillar of the zero trust initiative is protecting data. (Image by Getty Images)


Te Army is moving forward aggressively to implement zero trust concepts. Tis effort began with the Army establishing an authoritative source directing the use of these new principles and drafting guidance to organize a working group to provide direction and information exchange across Army ZT efforts.


Te DOD Zero Trust Reference Architec- ture version 2.0 defines seven “pillars” of zero trust. A pillar is a grouping of capabil- ities that organizes the range of activities necessary to achieve zero trust. Te seven pillars are user, device, network and envi- ronment, application and workload, data, visibility and analytics, and automation and orchestration.


Te Army is assessing existing capabilities for alignment with the DOD Zero Trust Reference Architecture. For example, the user pillar is focused on identifying the people operating within our network. An example of the work involved here is estab- lishing a database of all users and having


the capability to properly authenticate who they are when they log in to an IT system. Te Army has done much work in this area through its Army’s Identity, Creden- tial and Access Management capability, which includes a directory of users called the Army Master Identity Directory and its Enterprise Access Management Service ‒ Army authentication service used to verify user identities.


Likewise, the application and workload pillar focuses on ensuring enterprise appli- cations are tested internally and externally and can be made available to staff securely over the internet. An example of an Army effort is this pillar is the work being done with its Coding Resources and Trans- formation Ecosystems (CReATE) cloud environment. CReATE is a development, security and operations environment that uses tools and processes to enable secure software development.


Te key is implementing these changes in a secure and approved manner, in


CONCLUSION “Zero trust is a continuous journey,” Joseph said. “Right now, we are following the guidance put out by the Department of Defense CIO Zero Trust Portfolio Management Office. Based on that guid- ance, we have certain capabilities targeted to be online by [fiscal year 2027]. However, we know that it doesn’t stop there, and we will continue to modify and evolve as needed beyond [fiscal year 2027].”


For more informat ion, contact


usarmy.pentagon.hqda-cio.list.armyz- twg@army.mil.


RON LEE is a 20-year Army veteran of military broadcast journalism and public affairs. Following his time in the military, he earned an M.S. in public affairs management


and a B.A. specialist in


communications, both from the University of Maryland University College. He’s worked as a public affairs


for


the Program Executive Office for Soldier at Fort Belvoir, Virginia, and the District of Columbia National Guard


before


becoming an instructor of advanced public affairs and strategic communications at the Defense Information School at Fort Meade, Maryland, for two years. He recently worked


strategic communications for


U.S. Army Communications-Electronics Command Software Engineering Center, and now serves in a similar role with the Office of the U.S. Army Chief Information Officer.


https://asc.ar my.mil


27


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