AI Can’t Fix Camera System Governance Problems

Camera systems frequently remain in use long after the original installers have ceased operations.

Challenges of Long-Term Surveillance System Management

Camera systems frequently remain in use long after the original installers have ceased operations. In an interview, Rob Janssens, EMEA Cyber Security Director at Hikvision Europe, outlines the challenges that arise when integrators dissolve, documentation is lost, and administrative credentials are inaccessible. He emphasizes the necessity of self-sufficient customer control mechanisms and the role of secure-by-default configurations in mitigating predictable installation errors.

The Role of Secure-by-Default Configurations

The discussion also covers source code escrow agreements, country-of-origin regulations, and the limitations of vendor-provided evidence for critical infrastructure operators. Most surveillance systems operate beyond the lifespan of the organizations that initially deployed them. By year six, when the original installer has dissolved, commissioning records are unavailable, and administrative access is lost, the operational risks become significant.

Lifecycle Management and Customer Ownership

A device with a decade-long operational lifespan may outlive the company responsible for its initial setup by several years. Staff turnover, shifting contractor relationships, and poor documentation practices contribute to this scenario. From the manufacturer’s perspective, the system is the customer’s responsibility. Dependence on a specific integrator to maintain control is an unsustainable model.

Foundational Requirements for Secure Systems

The foundational requirements for addressing this issue include a secure activation process, robust account management, a reliable method for recovering or resetting access, firmware maintenance capabilities, and comprehensive audit trails. Mandatory password creation during setup, login attempt monitoring, IP address filtering, and controlled SSH access are essential safeguards. However, these measures are only effective if the system remains under the customer’s ownership and ongoing management.

Industry Trends and AI’s Role

A growing trend in the industry is improved asset management practices. Security teams are increasingly adept at identifying devices, verifying configurations, and detecting systems that have fallen out of standard management protocols. While artificial intelligence can enhance these efforts, it is not a substitute for fundamental governance structures. The core priorities remain ownership, clear governance frameworks, and documented recovery procedures.

Secure-by-Design vs. Secure-by-Default

When an installer disappears and a customer loses administrative control over their cameras, the issue becomes a lifecycle management challenge. Manufacturers must design products that enable customers to regain control without relying on the original integrator. A significant portion of physical security equipment is procured based on cost, installed by non-specialist personnel, and left unattended thereafter.

Engineering Solutions for Unreliable Installers

Engineering solutions for such environments require acknowledging that installers may not follow detailed security guidelines. Relying on human compliance with complex manuals is unrealistic. Instead, products must incorporate inherent security features. For example, requiring a unique password during activation is more effective than shipping devices with universal defaults. Unused services should not be exposed by default, and remote administration capabilities must be tightly controlled.

Hikvision’s Security Development Lifecycle

The distinction between secure-by-design and secure-by-default principles is critical. Secure-by-design involves integrating security throughout the product lifecycle, while secure-by-default ensures that users do not need specialized knowledge to achieve a baseline level of protection. Hikvision’s Security Development Lifecycle encompasses requirements, design, development, verification, release, and maintenance phases. This approach aligns with industry best practices, as security cannot be an afterthought in installation projects.

Addressing Common Installation Mistakes

While manufacturers cannot mitigate all poor network designs—such as cameras exposed directly to the public internet without patches—products can be made more resilient to common mistakes. For instance, if an integrator disables security features to expedite remote access, the customer must be fully informed of the risks. Such decisions should not be concealed in installation scripts or driven by convenience alone.

Remote Access and Network Security

High-risk settings should require explicit user acknowledgment, and critical changes must generate audit records. The preferred solution to remote access challenges is architectural design rather than disabling security controls. Limiting access points, using secure protocols, segmenting video networks, and exposing only necessary services are more effective strategies. Hikvision’s product-security guidelines recommend restricting remote access and prioritizing methods like virtual private networks over direct internet exposure.

Evolving Threats and Customer Responsibilities

While customers may make risk-based decisions, manufacturers have a responsibility to ensure these choices are transparent and to provide a secure baseline configuration. The evolving threat landscape, including automated scanning tools, means configurations that might have gone unnoticed for months can now be identified rapidly. This shifts the burden of justification from “we have always done it this way” to proactive security measures.

European Buyer Demands and Technical Evaluations

European buyers increasingly demand source code escrow agreements, third-party binary analysis, or country-of-origin restrictions. While these measures address different risks, none alone constitute security theater. Independent testing and vulnerability research provide valuable insights, and binary analysis helps customers verify what is actually running on devices. Source code escrow is useful for business continuity but does not inherently guarantee product security.

Country-of-Origin and Supply Chain Considerations

Country-of-origin requirements reflect legitimate concerns for critical infrastructure operators, including legal, geopolitical, and supply chain considerations. However, these should not replace objective technical evaluations. The focus should be on the evidence and technical controls in place, rather than nationality alone. Hikvision emphasizes continuous improvement through security testing, vulnerability disclosure, and secure development practices.

Transparency and Continuous Improvement

Transparency is essential, allowing customers to verify how security is managed. When questioned about trust in firmware, Hikvision highlights its Security Development Lifecycle, published security controls, and certified vulnerability reporting processes. The company also notes its ISO/IEC 42001 certification for AI governance, ensuring ethical, transparent, and secure AI systems.

Product Security Documentation and External Scrutiny

Product security documentation outlines password policies, activation requirements, anti-downgrade protections, and default SSH configurations. Independent validation through third-party assessments and customer testing is encouraged. However, no manufacturer can guarantee the absence of vulnerabilities or absolute trust. The emphasis remains on providing sufficient information for customers to evaluate technology, continuously improving products, and accepting external scrutiny.

About Author

Anuj

See author's posts