{"id":16834,"date":"2015-09-25T13:40:08","date_gmt":"2015-09-25T13:40:08","guid":{"rendered":"https:\/\/one.sightlinemg.com\/c4isrnet\/uncategorized\/2015\/09\/25\/how-to-protect-and-strengthen-c4isr-systems\/"},"modified":"2026-08-08T17:58:42","modified_gmt":"2026-08-08T17:58:42","slug":"how-to-protect-and-strengthen-c4isr-systems","status":"publish","type":"post","link":"https:\/\/one.sightlinemg.com\/c4isrnet\/opinion\/the-compass\/2015\/09\/25\/how-to-protect-and-strengthen-c4isr-systems\/","title":{"rendered":"How to protect and strengthen C4ISR systems"},"content":{"rendered":"\n

Cyber threats remain a top concern of Department of Defense officials involved in procuring and maintaining C4ISR systems, according to a recent Market Connections survey of 250 decision-makers across the Pentagon. On its own, this finding is not terribly surprising. C4ISR capabilities, no matter how sophisticated, offer little war-fighting value if they are not secure. However, it has been our experience that the same approaches that foster the most effective, integrated C4ISR also create the most secure C4ISR. That is, seamless interoperability and robust security go hand in hand. Here’s how our military can best achieve both.<\/p>\n\n\n\n

For some time now, military officials have been calling for a shift from proprietary, closed, vendor-owned C4ISR systems to an enterprise architecture that is standards-based, open and government-owned. Under this approach, the government will own the architecture, the system and the data, thus reducing vendor lock-in and helping eliminate inefficiencies. This standards-based approach will also allow for a plug-and-play environment where vendors can bring their most innovative solutions to government for easy insertion into military networks.<\/p>\n\n\n\n

As another important step, Pentagon officials have also advocated the adoption of agile, incremental delivery of modular systems with integrated capabilities. Under this approach, military organizations will shift away from the big-bang acquisition approach in which large, monolithic systems are delivered all at once by a single vendor team, often after years of development. Instead, they will acquire smaller, modular systems that are built with common interface specifications and delivered incrementally by the entire industry base. This enables program officials to insert new innovations into the integrated C4ISR solution as soon as they are invented.<\/p>\n\n\n\n

What’s noteworthy about this approach is that it would help to create a significantly more secure C4ISR environment. Today, the complex interfaces required to integrate independent, proprietary C4ISR systems can introduce vulnerabilities and create security holes that increase the attack surface for malicious actors. Consequently, by designing systems to interoperate through interfaces with common (and secure) standards, they will not be linked by insecure \u2014 and often makeshift \u2014 interfaces created when independent systems are integrated after fielding.<\/p>\n\n\n\n

In addition, agile development enables systems developers to make cybersecurity an organic and continuing feature of each integrated system. That is, security is tested and, if necessary, improved with each modular phase. The early and continuous engagement of security issues in the design process, along with control over security standards and interfaces, ensure that security, like interoperability, is designed in rather than bolted on after a system is built. In this way, C4ISR solutions are infused with a unified and multilayered defense.<\/p>\n\n\n\n

These approaches are key components of an overarching methodology for achieving “integrated C4ISR.” In integrated C4ISR, all of the individual pieces are designed from the start \u2014 and then maintained throughout the life cycle \u2014 as part of an enterprise system. Integrated C4ISR is distinguished by these major features:<\/p>\n\n\n\n