How drone security works within XProtect

Drones are often discussed as if they are simply another type of camera, but in practice, they behave very differently from the fixed devices most video systems are designed around. Traditional surveillance cameras are persistent, network-addressable devices. They are installed in a fixed location, continuously connected and can be accessed directly by a video management system at any time.

Drones, by contrast, are mobile, temporary and operator controlled. Video is typically captured by the drone, transmitted to a handheld controller and then displayed through a mobile application. In many cases, the drone itself is not directly accessible on the network. Instead, the drone or its controller sends the video stream during a flight to a receiving service or server, where it can be captured and made available to other systems, rather than waiting for a video management system to pull the footage from it.

This creates a fundamental mismatch in how video is handled in a VMS. Most video management systems, including XProtect, are designed to retrieve video streams from devices using a pull-based model, commonly through RTSP. Drone video, on the other hand, is usually delivered as a push-based stream, often using RTMP. As a result, without additional components, the system cannot simply “connect” to a drone in the same way it would connect to a fixed camera.

Understanding this difference is key. Integrating drones into a VMS is not simply about adding another device — it is about bridging two different methods of video transmission.

To support drone video integration within XProtect, a translation layer is required to convert the incoming video into a format the system can ingest and manage. In most cases, the drone or its controller sends video as an RTMP stream. RTMP is a push-based streaming protocol designed to send video from a source device to a receiving service, rather than waiting for another system to request it. This is typically handled through third-party drivers or services that can receive and translate the stream for XProtect.

These drivers allow XProtect to accept the incoming stream and present it as a standard video source within the system. Once connected, the video can be viewed, recorded and managed alongside all other devices in the platform. Some vendors offer commercial RTMP drivers designed for XProtect, such as our partner, Orbnet Systems, which provides a solution for ingesting incoming streams. There are also independently developed options available, including community-built RTMP push drivers that enable similar functionality.

While these tools allow a drone’s video stream to be sent directly into XProtect, they also introduce important networking considerations. Because the stream is initiated from a mobile device or controller, that device must be able to securely reach the XProtect server. In many RTMP-based setups, this would require the server to accept incoming connections over a specific port (commonly port 1935 for RTMP). While it is technically possible to expose the server to the internet to allow this connection, most organizations will avoid doing so due to security concerns.

Instead, many deployments rely on secure networking approaches such as virtual private networks (VPNs). For example, solutions like ZeroTier can be used to create a secure connection between the mobile device and the server without requiring port forwarding or direct exposure to the public internet. By running the VPN client on both the mobile device and the server, the two systems can communicate securely as if they were on the same local network. This allows drone video to be transmitted reliably while maintaining standard security practices.

Unlike fixed cameras, drone video is not continuously available. It appears in the system only when a drone is actively deployed, which changes how operators interact with it.

In practical terms, this creates a different interaction model than traditional cameras. Instead of continuously pulling video from a fixed endpoint, XProtect can be configured with a camera tile that remains idle until a drone connects. When a flight begins and the stream is initiated, the feed becomes active in the interface, appearing in real time for operators. When the drone disconnects, the tile returns to an offline state, ready for the next deployment.

From a system perspective, each active drone feed is typically treated as a standard camera stream within XProtect. This means it can be configured and managed in the same way as other video sources. However, the underlying behavior remains different, as the stream is only available when the drone is actively transmitting.

The way organizations deploy drones for security operations is shaped by how quickly video is needed, where coverage is required and how resources are managed across an operation. Because drone video in XProtect is only available when a device is actively deployed, organizations must decide how and when to use drones to best support their workflows.

Common approaches include:

• On-demand use
  Drones are launched in response to a specific situation and provide video only for the duration of that activity. This approach is centered on flexibility and rapid deployment when conditions change.
• Pre-positioned drones
  Devices are placed in strategic locations so they can be deployed quickly when needed. This model prioritizes faster response times by reducing the distance between the drone and the area of interest.
• Event-based use
  Drones are deployed temporarily to provide additional coverage during planned activities. This approach allows organizations to extend visibility in specific areas without making permanent changes to their camera infrastructure.

In practice, most organizations use a combination of these approaches. Because drone video can be integrated into XProtect as needed, teams can adapt how they use drones in the field without changing how video is viewed or managed. This makes it easier to scale coverage up or down depending on the situation, while maintaining a consistent operational workflow.

1. Real-time incident response
One of the most common uses of drone video in XProtect is real-time incident response. In public safety environments, drones are increasingly deployed to provide immediate visibility into a situation before police officers arrive on site. Instead of relying solely on fixed cameras or verbal reports, operators can view a live aerial perspective directly within the same interface they use to monitor the rest of the system. This allows them to assess the situation more quickly and provide better information to teams in the field. In some deployments, this approach is used to provide rapid aerial support in place of traditional, expensive methods like helicopters, offering faster response times and more flexible coverage when every second counts.

Drones are also used to extend visibility in areas where fixed coverage is limited or unavailable. During large public events, for example, temporary aerial coverage can be deployed to monitor crowd movement, identify potential risks and support coordination across teams.

Because the video feed can appear within XProtect alongside existing cameras, operators can move between ground-level and aerial views without switching systems, creating a more complete understanding of the environment.

2. Pre-event planning
In addition to active incidents, drones can support pre-event planning and inspection workflows. Organizations may use them to capture baseline imagery of critical areas, such as rooftops or infrastructure, before an event takes place. This makes it easier to identify changes or anomalies later. In some cases, drones equipped with thermal capabilities can also be used to detect issues that are not visible to standard cameras, further extending their value beyond traditional surveillance.

Across both of these use cases, flexibility is a key advantage. Unlike fixed cameras, drones can be deployed on demand and repositioned as needed, making them particularly useful in dynamic situations where conditions change quickly or where coverage needs to be established temporarily. Within XProtect, this flexibility is reflected in how drone feeds appear and disappear based on active use, allowing operators to incorporate them into their workflow without disrupting the broader system. As a result, drone video is not a replacement for fixed surveillance, but a complementary layer that enhances situational awareness—helping organizations extend their visibility, respond more effectively and make better-informed decisions in real time.

While drones provide a powerful extension to traditional video systems, their use also comes with practical and operational considerations that organizations need to account for.

One of the most important factors is regulatory compliance. In the European Union (EU), for example, evolving regulatory frameworks — including directives like the NIS2 Directive and the Critical Entities Resilience Directive (CER) — are increasing expectations around risk management, cybersecurity and operational continuity. In many regions, drone operations require a licensed pilot and must follow strict rules around flight paths, altitude and line-of-sight operation. In the United States, for example, these rules are governed by the Federal Aviation Administration (FAA), while in the EU they are regulated under frameworks established by the European Union Aviation Safety Agency (EASA). These requirements can limit how and where drones are deployed, particularly in dense urban environments or sensitive areas.

Operational constraints also play a significant role. Unlike fixed cameras, drones are typically used for short, mission-based deployments rather than continuous monitoring. Flight time is limited by battery capacity, and coverage depends on the drone’s position and the availability of a trained operator. Even in advanced public safety deployments, drones are used selectively to support specific incidents rather than replace existing infrastructure entirely.

Technical considerations, particularly around network connectivity, are another key factor. As discussed earlier, drone video often relies on mobile or wireless connections, which can vary in reliability depending on the environment. Ensuring secure and stable communication between the drone, the control device and XProtect is essential for consistent performance.

Taken together, these considerations highlight an important point: drones are not a replacement for fixed surveillance systems, but a complementary capability that must be used thoughtfully. When integrated into XProtect with a clear understanding of these limitations, they can provide meaningful operational value.

Drones are becoming an important part of modern security operations, but their value depends on how effectively they are integrated into a broader system.

XProtect provides the foundation to bring these capabilities together — enabling drone video to be ingested, viewed and managed alongside fixed cameras and other systems.

As both drone usage and airspace awareness technologies continue to evolve, the ability to integrate new tools into a unified platform will be critical. XProtect’s open approach supports this flexibility, helping organizations adapt to changing operational needs.

Interested in more information on how XProtect can support drones? Get in touch with us!