https://orcid.org/0000-0002-9097-2246
Earlier this year I received an invitation to participate in the Geospatial World Forum 2026 at the RAI Amsterdam that is one of the more substantive gatherings in the Geospatial and Defence intelligence space. The week ran from April 27 through May 1, and I found myself sitting across from some of the sharpest practitioners working at the intersection of spatial intelligence, defence systems, and emerging technology. The conversations were candid, the perspectives diverse, and the stakes given the current geopolitical climate very real.
I was part of three panel discussions across the week. This is the first of a short series of posts where I'm putting down what we discussed mostly for my own records, partly because these conversations deserve to exist somewhere beyond a conference hall.
Panel Discussion 5: Network-Centric Warfare and Data Centricity
The session title sounds clinical and crisp. What it actually described was one of the most consequential shifts in modern military doctrine the move away from platform-centric thinking toward a model where the network itself is the force multiplier.
The core premise is straightforward: a sensor that sees something is only useful if that observation reaches a decision-maker before the window closes. In legacy architectures, that gap between observation and action has historically been where wars are lost. Network-centric warfare is the systematic attempt to collapse that gap.
Linking Sensors, Platforms, and Decision-Makers
What struck me most in our discussion was how mature the concept is, and how immature the execution still remains in many theatres. The vision is elegant: sensors whether satellite, UAV, ground-based radar, or human intelligence feeds pipe data into a unified digital ecosystem where platforms (vehicles, aircraft, naval assets) and decision-makers share a common operational picture in near-real-time.
The core premise is straightforward: a sensor that sees something is only useful if that observation reaches a decision-maker before the window closes. In legacy architectures, that gap between observation and action has historically been where wars are lost. Network-centric warfare is the systematic attempt to collapse that gap.
Linking Sensors, Platforms, and Decision-Makers
What struck me most in our discussion was how mature the concept is, and how immature the execution still remains in many theatres. The vision is elegant: sensors whether satellite, UAV, ground-based radar, or human intelligence feeds pipe data into a unified digital ecosystem where platforms (vehicles, aircraft, naval assets) and decision-makers share a common operational picture in near-real-time.
The friction points are less glamorous. We talked about data standardisation across allied forces, legacy systems that weren't designed to interoperate, and the latency that creeps in at every translation layer. One of the panellists made a point I keep returning to: the weakest link in most network-centric architectures isn't the sensor it's the middleware.
Rapid Data Sharing for Coordinated Response
The session highlight framing mentioned "coordinated and adaptive combat responses" and this is where the discussion got genuinely interesting. Adaptive is the operative word. A static command-and-control model assumes that orders flow downward and the environment cooperates. Modern conflict doesn't offer that.
What network-centricity enables, at its best, is a force that can recompose itself in response to ground truth rather than responding to a plan that was made twelve hours ago. That requires not just fast data pipelines, but trust in those pipelines. Operators need to act on data they haven't personally verified. That's a significant psychological and institutional shift, and it came up more than once.
We also touched on the adversarial dimension what happens when an opponent understands your data architecture well enough to inject noise, delay, or disinformation into it. The network that enables adaptive response can also be the attack surface. This bleeds directly into the cyber-geospatial panel I was part of later in the week, which I'll cover in the next post.
Situational Awareness, Force Agility, and Mission Effectiveness
These three phrases tend to travel together in defence literature, sometimes as buzzwords. In practice, they describe a genuine capability gradient.
Situational awareness at the tactical level means a soldier knows what's beyond the next ridgeline. At the operational level, it means a commander understands how a theatre is evolving across multiple simultaneous engagements. Network-centric architecture is what connects those two levels and everything between.
Force agility the ability to reposition, reassign, or re-task elements quickly is a direct function of how good that common picture is. If your forces are operating on shared, current data, you can exploit opportunities and respond to threats faster than an opponent who isn't.
Mission effectiveness is the output of the two above, but it also depends on something the technology can't fully provide: trained humans who can interpret ambiguous data and make decisions under pressure. We spent some time on this. The risk of over-automating the common operational picture is that you optimise for the scenario you modelled, not the one you're actually in.
WHAT I DISCUSSED
On ZTA in networked battlefield architecture: One of the points I raised was why Zero Trust Architecture isn't optional in a network-centric environment it's foundational. When you're linking sensors, platforms, and decision-makers across a distributed ecosystem, the old perimeter-defence model collapses entirely. Every node, every data feed, every inter-platform handshake has to be treated as potentially compromised. Assume breach, verify continuously, grant least-privilege access. In a coalition context especially, where you're operating with allied systems you don't fully control, ZTA is the only architecture that makes operational sense.
On zero-day exposure in sensor-platform pipelines:I brought up zero-day vulnerabilities specifically in the context of the network's attack surface. The more you integrate sensors feeding platforms feeding command layers the more entry points you create. A zero-day in a firmware layer of a battlefield edge device isn't just an IT problem; it's a potential blind spot or worse, a spoofed data feed entering your common operational picture. The network that gives you agility is the same network that, if unpatched and unmonitored, gives an adversary a quiet way in.
On homomorphic encryption for coalition data sharing: A practical problem in joint operations is that allied nations need to share processed intelligence without exposing raw sensor data to each other's systems. I discussed homomorphic encryption as a maturing solution here the ability to run computation on encrypted data means a partner nation's AI layer can query your dataset without you ever decrypting it on their side. We're not at frictionless deployment yet, but the direction is clear.
On Differentially Private Federated Learning for shared battlefield AI: Federated learning lets distributed nodes forward units, vehicles, command posts contribute to a shared intelligence model without centralising raw operational data. Add differential privacy on top of that, and you're injecting calibrated noise into each node's contribution such that no individual data point can be reverse-engineered. I raised this as the architecture that makes collaborative battlefield AI viable without creating a single honeypot of sensitive operational data.
On zero-day exposure in sensor-platform pipelines:I brought up zero-day vulnerabilities specifically in the context of the network's attack surface. The more you integrate sensors feeding platforms feeding command layers the more entry points you create. A zero-day in a firmware layer of a battlefield edge device isn't just an IT problem; it's a potential blind spot or worse, a spoofed data feed entering your common operational picture. The network that gives you agility is the same network that, if unpatched and unmonitored, gives an adversary a quiet way in.
On homomorphic encryption for coalition data sharing: A practical problem in joint operations is that allied nations need to share processed intelligence without exposing raw sensor data to each other's systems. I discussed homomorphic encryption as a maturing solution here the ability to run computation on encrypted data means a partner nation's AI layer can query your dataset without you ever decrypting it on their side. We're not at frictionless deployment yet, but the direction is clear.
On Differentially Private Federated Learning for shared battlefield AI: Federated learning lets distributed nodes forward units, vehicles, command posts contribute to a shared intelligence model without centralising raw operational data. Add differential privacy on top of that, and you're injecting calibrated noise into each node's contribution such that no individual data point can be reverse-engineered. I raised this as the architecture that makes collaborative battlefield AI viable without creating a single honeypot of sensitive operational data.
On sovereign AI models: This came up when we discussed why coalition forces can't simply share an AI layer the way they might share a radio frequency. Every nation feeding data into a shared model is implicitly exporting its operational patterns, its sensor signatures, its tactical doctrine. Sovereign AI models trained and hosted within national infrastructure, on national data isn't protectionism, it's operational security. Interoperability has to happen at the interface layer, not by pooling the model itself.
On distillation attacks against tactical AI: I flagged distillation attacks as an underappreciated threat vector in deployed military AI. If an adversary can interact with your tactical decision-support system enough times even indirectly, through observing its outputs in the field they can begin reconstructing its behaviour in a surrogate model. You've effectively handed them your doctrine without them ever touching your training data. Access control to AI system outputs matters as much as access control to the data that trained it.
On distillation attacks against tactical AI: I flagged distillation attacks as an underappreciated threat vector in deployed military AI. If an adversary can interact with your tactical decision-support system enough times even indirectly, through observing its outputs in the field they can begin reconstructing its behaviour in a surrogate model. You've effectively handed them your doctrine without them ever touching your training data. Access control to AI system outputs matters as much as access control to the data that trained it.
On KASLR bypass at the edge: At the device level, KASLR bypass deserves attention in hardened military hardware. Kernel Address Space Layout Randomisation is a standard mitigation, but known bypass techniques mean it can't be the last line of defence on edge battlefield devices. I raised this in the context of the network's physical endpoints the sensors and terminals that are closest to the threat environment and furthest from the patch cycle.
More from Amsterdam in the next post on cyber-geospatial convergence and what it means to protect digital borders that exist in three-dimensional space.
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
