Securing Video Management: Navigating Cybersecurity Across Cloud and On-Premises Environments

Choosing between on-premises and cloud-based video management involves more than deciding where the hardware is located. It is also about determining how cybersecurity responsibilities are divided, making it important for organisations to understand who is responsible for securing different parts of the environment.

Both on-premises and cloud-based video deployments can provide secure and hardened systems, but each comes with different strengths and considerations. Responsibilities between vendors and customers vary, as do the threats each model may face, and the expertise required to keep systems protected. Understanding these differences can help organisations select an approach that aligns with their security requirements and operational capabilities.

Barry Nortan, Fellow, Milestone Systems

Understanding the Security Divide

 

One of the biggest differences between on-premises and cloud deployments is how responsibility for security is distributed.

With on-premises systems, the organisation retains control over most aspects of the environment. Cameras, servers, network connections, encryption keys, passwords and security updates all need to be managed by the organisation, either through its internal IT team or the systems integrator responsible for deployment.

Manufacturers develop and release security updates, but customers using on-premises systems need to download, test and apply them. Cloud-based Video Security as a Service (VSaaS) takes a different approach. The vendor manages much of the underlying infrastructure, including servers, patches, recorded-video storage and threat monitoring.

Moving to the cloud does not, however, mean that every security responsibility shifts to the provider. Customers remain responsible for areas such as user access, permissions and configuration. The provider protects the platform, while the customer remains responsible for how that platform is used.

This division can sometimes lead to confusion. Organisations adopting managed cloud services may assume that security is entirely handled by the provider, when they still need to control who can access video and how credentials are managed. The difference is that responsibility for securing the underlying infrastructure moves to the cloud provider.

On-premises environments, meanwhile, require strong technical expertise. Integrators need to configure network security, manage certificates, maintain suitable network isolation and ensure connected devices are not operating with default credentials. Their involvement can continue beyond deployment through guidance on emerging threats, updates and configuration reviews.

The vendor supports this process through secure product development, updates, documentation and technical assistance. Ultimately, developers, integrators and organisations each have a role to play in maintaining security throughout the system’s lifecycle.

For organisations in India, this shared responsibility is increasingly relevant as the country’s data-protection framework develops. The Digital Personal Data Protection Act, 2023 requires Data Fiduciaries to implement reasonable security safeguards to prevent personal data breaches and places responsibility on them for processing undertaken by Data Processors on their behalf.

The Act also provides that the Central Government may restrict the transfer of personal data by a Data Fiduciary for processing to specified countries or territories outside India. While this does not amount to a blanket data-residency requirement, it makes data-processing and transfer arrangements relevant considerations when evaluating cloud, on-premises or hybrid VMS deployments.

Network Architecture and the Changing Risk Landscape

 

Network connectivity creates another important distinction between deployment models.

On-premises systems can be physically isolated from the internet through air-gapping or protected through network segmentation. This can provide meaningful security benefits, particularly for organisations operating sensitive environments or facing strict compliance requirements. Keeping systems away from the public internet can also remove certain categories of remote attacks.

However, isolation does not eliminate every risk. Insider access, compromised removable media and incorrectly configured network zones can still create vulnerabilities. Air-gapped systems also cannot receive automatic updates or remote monitoring, making security maintenance more dependent on manual processes. Delayed patches or configuration changes can therefore reduce the protection an air gap provides.

Cloud-based systems remain connected to the internet by design and consequently face some degree of internet-exposed risk. At the same time, cloud providers can invest in continuous monitoring, intrusion detection and rapid response capabilities that may be difficult for individual organisations to maintain.Centralised infrastructure can also support automated security updates, scalable storage and more consistent management across distributed environments.

These capabilities can reduce some of the operational effort required from customers, particularly where maintaining servers, applying infrastructure updates and managing storage would otherwise require significant internal resources. However, the security benefits depend on how the cloud service is designed, configured and managed, making it important for organisations to understand the responsibilities that remain with them.Hybrid deployments combine elements of both approaches, such as on-premises recording with cloud management or edge devices connected to cloud services. They therefore inherit considerations from both models while creating additional security boundaries between environments. Misconfigured access points or poorly secured devices can potentially provide pathways for attacks.

For organisations in India, these architectural decisions can also be considered alongside data-protection requirements. Where video systems process personal data, organisations may need to assess how information is collected, accessed, processed, stored and transferred. This can make infrastructure control and data-transfer arrangements relevant factors when deciding between on-premises, cloud and hybrid approaches.

Creating a Stronger Security Partnership

 

Neither on-premises nor cloud VMS is inherently more secure. On-premises systems can provide greater control and network isolation, which may suit organisations with strong IT capabilities or specific data-sovereignty considerations. Cloud systems, meanwhile, shift much of the infrastructure management to providers, who have specialised security teams and automated update capabilities, acting on behalf of customer requirements.

Both models can be implemented effectively or poorly. The right choice ultimately depends on an organisation’s environment, risk profile, technical capabilities and operational requirements.

What remains consistent is the need for a shared commitment to cybersecurity. Manufacturers must develop secure platforms and respond to vulnerabilities. Integrators must make security a priority during deployment and continue advising customers as systems and threats evolve. Organisations must maintain secure configurations, manage access.In non-cloud environments, they also take on greater responsibility for applying updates, monitoring infrastructure and maintaining the underlying environment, while in cloud deployments, much of this infrastructure-level responsibility is handled by the provider.

As VMS platforms become connected to analytics, access control, intercoms and cloud services, in addition to more-and-more cameras — very often from multiple different vendors — clearly defining these responsibilities becomes even more important.

Ultimately, no single stakeholder can provide complete protection for a video security environment. Manufacturers, integrators and end-user organisations each have a distinct role. When those responsibilities are clearly understood, organisations can make more informed deployment decisions and build cybersecurity into their systems as an ongoing, shared commitment.

Authored by Barry Nortan, Fellow, Milestone Systems