Pages

23 February 2023

JADC2 or How to Eat an Elephant: Six Principles for Success

William McHenry

The internet is the most complex network humanity has ever created. Joint All Domain Command and Control (JADC2), if fulfilled in the entirety of its purpose, has the potential to be humanity's second most complex network. The internet was built using a decentralized approach, allowing anyone meeting common standards to join, communicate, and share data. The internet would not be what it is today if early proponents and contributors had insisted that it be created top-down with proprietary components and differing standards.

Over the last several years, the Department of Defense (DoD) has invested billions of dollars to build a system of bespoke command and control networks that will eventually link sensors to shooters and provide a common operating picture for decision making. Initial efforts have not been well integrated across the Services. DoD and the separate Armed Services seem to have again taken an approach that will preclude the rapid adoption and expansion of JADC2.

While U.S. doctrine holds that the individual Armed Services fight as a Joint Military Force with elements of Soldiers, Sailors, Airmen, Guardians and Marines fighting side by side, the Army (Overmatch), Navy (Convergence) and Air Force (Advanced Battle Management System (ABMS) have chosen to build separate, incompatible, and bespoke networks. While it is unrealistic and inefficient to dictate a common network architecture across the Services with their varying needs and mission sets, there are a set of expectations/standards that if followed, will allow JADC2 to come together in a decentralized manner to meet future mission sets. The expectations are:

A robust, resilient network architecture

For JADC2 to meet future mission requirements, it must be a robust, resilient network. Future adversaries will focus on disrupting our command and control networks in the first stages of any conflict. A single architecture and traditional communications infrastructure is susceptible to attack, potentially rendering communications and data flow difficult if not impossible. In order to frustrate adversarial efforts, DoD must integrate commercial technologies and networks into JADC2. Doing so will realize a network that can sustain communications. If one pathway succumbs to attack, a robust, resilient network would allow switching networks to reroute traffic and data. Commercial satellite launches are outpacing government launches and commercial cyber companies are outspending the government in research and development (R&D) by an order of magnitude. Considering the rise of adversarial threats to satellites and the constant probing of government networks, partnering with the commercial technology sector will provide the government access to the best of current technology while vastly increasing the satellite resources available to replace battlefield losses.

Common data standards

The Military Services fight as a Joint Force under a single Commander. Disparate units must be able to communicate, share data, and analyze data across the Force to ensure maximum effectiveness. To capture, analyze and operationalize data flowing from a plethora of sensors, DoD must establish and enforce common data standards and transmission protocols in order to preclude the individual services from adopting incompatible standards for their Command and Control (C2) networks. To date, the U.S. has invested billions of dollars in the various Services’ JADC2 efforts without setting in place standards that will ensure the individual networks will be able to share data and communicate rapidly. Past iterations of Service-specific C2 systems could not communicate, share data, or process data developed on other Services’ proprietary networks. While the path is well trod, following in previous footprints will again lead to friendly elements on the battlefield not being able to communicate and thus unable to integrate effectively.

Zero Trust Authentication/Authorization

In November of 2022, the DoD Chief Information Officer released the Department’s Zero Trust Strategy containing a road map for future implementation of Zero Trust across the Joint Force. While very different from a full implementation, it is a start. Zero Trust is a critical component of maximizing JADC2’s hardware and software security while minimizing the effectiveness of network breaches. Authentication of data at the packet level is key as purposeful data corruption attacks will increasingly be utilized by adversaries as a means to mitigate the benefits of leveraging Artificial Intelligence (AI) to build a common operating picture and to make rapid decisions.

Post-Quantum Encryption

Post-quantum encryption for authentication, authorization and information protection must be a part of JADC2. The ability to attack current methods of encryption using quantum properties and computers is a coming reality. Currently, potential adversaries are collecting and storing our communications and data. Once online, quantum computers will be used to break the encryption on vulnerable data and communications systems as well as attack any non-Quantum protected encryption. The commercial market has existing solutions to aid in government efforts to protect current and future communications systems and data from the inevitable quantum attack.

Computing/AI at the Edge

AI and computing at the edge of the battlefield will efficiently route data and alert commanders at all levels of war to relevant data and threats. Modern sensors capture vast amounts of data. The ability to transmit all of the data collected by numerous sensors to a central cloud for data analytics/processing is inefficient and time consuming. Using AI to sort and categorize data prior to transmission will prevent overloading networks and speed processing. Assuming multiple levels of friendly command structures and strike capability, future sensors incorporating AI can collect data relevant to multiple levels of command. Information at the tactical level such as small troop movements or a smaller class Unmanned Aerial System (UAS) might be relevant to a small operating unit in the area of operations but will be less relevant to a distant Joint Task Force Commander. Processing the data at the edge, sifting for relevant data and routing the data based on its relevancy and current queries, will build an appropriate level of the common operating picture at each level of command and prevent network bottlenecks.

Backward Compatibility with Legacy Systems

Investments in connecting legacy systems will pay off in readiness while future capabilities come online. JADC2 is not a lightning pivot to all new technologies, with cutting edge sensors linked to micro satellites in low earth orbit, connected to clouds in the ether, with future advanced weapons standing by to strike emerging targets. JADC2 must be backward compatible. Existing systems and networks must be linked and modernized with newer technologies as they come online. The Defense Advanced Research Projects Agency (DARPA) has a number of current projects focused on the problem of connecting legacy systems. Joining current networks and adding future capabilities in a decentralized manner will realize JADC2’s promise.

While OSD and the Chief Digital and Artificial Intelligence office are working to identify critical needs and mitigate vulnerabilities in building out JADC2, the Services remain laser focused on their Service specific priorities. As a result of separate mission sets, the Services naturally have different perspectives on JADC2. Like blindfolded people feeling an Elephant, each of the Services believe that JADC2 is something different than the other Services. The Air and Space Forces think it's a snake that will link aircraft and satellites to airborne command and control. The Navy thinks it's a tree trunk connecting undersea and surface vessels to aircraft. While the Army and Marine Corps think it's a wall that requires new sensors and networks linked to shooters. With their different perspectives and mission sets, the Services will continue to build their networks with Service-specific components meeting Service-specific requirements. As long as each of their separate designs incorporate the six highlighted common standards/principles, JADC2, like the disparate networks that comprise the internet, will come together in a decentralized manner. It will connect sensors, command and control, and shooters across the Joint Force thus increasing lethality and sustainability; step by step, bite by bite.

No comments:

Post a Comment