ONVIF Introduces Draft Cloud Video Surveillance Standard
The new Profile V release candidate aims to prevent vendor lock-in by standardizing cloud-based video management systems.
- By Jesse Jacobs
- Jul 13, 2026
An open-standards group has introduced a draft standard for cloud-based video surveillance designed to eliminate single-vendor dependence for security systems.
ONVIF released the candidate for Profile V to bring a brand-independent approach to cloud video infrastructure. The standard provides a framework for system integrators, consultants and end users to deploy cloud video systems using products from multiple manufacturers.
Cloud-based video management systems replace or reduce local hardware by routing video through remote servers. The setup minimizes local server requirements, simplifies system maintenance, enables remote web access and allows for scalable storage expansion.
While most current cloud video surveillance systems rely on proprietary technology that ties cameras and software to a single provider, Profile V aims to allow conformant products from different brands to work together. Under the standard, individual system components can be replaced without a complete system redesign.
The draft standard allows a conformant cloud-based video management system to connect with cameras behind local firewalls without requiring virtual private networks or port forwarding configurations. Devices establish a secure outbound connection to the cloud system, streaming live video and audio over WebRTC to standard web clients.
Devices can also transmit event notifications to the cloud management software. Video and audio data are encrypted before being sent to cloud storage platforms like Amazon S3 or Microsoft Azure Blob Storage. Profile V can also be paired with existing ONVIF video and access control profiles for hybrid deployments.
Security protocols are managed through a dedicated Profile V Security Add-on. The add-on utilizes the OAuth 2.0 framework to restrict data exchange to authorized devices and clients while ensuring all recordings are encrypted during transit to the cloud. By placing these requirements in an add-on rather than the core profile, the organization can update security protocols independently as technology evolves.
The draft specification is open for review by members, with finalization expected by the end of the year.