Tactical cross-domain solutions: Current status and the need for change

The rapid migration of system high information sharing to the tactical edge has made it imperative that the DoD reexamine tactical Cross Domain Solutions/Enterprise Services (CDS/ES). Prior to Operation Iraqi Freedom (OIF), information sharing requirements at the tactical edge were relatively few in number and nominal in terms of data throughput, data types, and users. Cross Domain Solutions (CDS) deployed back then were specialized, hardened, and resistant to hacking in the event of enemy overrun. Since OIF, both the volume of battle field system high tactical networks as well as the operational requirements to support each of these networks (i.e., increased data throughput, data types and variety of users) have significantly increased [On Point]. When combined with additional constraints inherent to the battle space such as low latency, Size, Weight and Power (SWaP), the current approach to addressing information sharing requirements in a tactical network breaks down. Taking the traditional, point-to-point approach by making a CDS smaller and more robust in the tactical environment may be adequate in the near term. However, this approach will not support the requirements levied upon next generation warfighting systems. In the future, interdependent tactical networks will be required to exhibit a dynamic (self organizing) nature, supporting adaptability and quick response to data ingress and egress. Nodes on these future networks will also need to operate with severely limited bandwidth and other operational and/or environment constraints. Therefore it is necessary to examine current and future information sharing requirements at the tactical edge from both the CDS/ES developer as well as user perspective. This position paper will discuss both perspectives in order to allow a better understanding of the current CD problem space, as well as gain insight into building the next generation CDS/ES.