NormaglobeDigital Compliance

VMS and video analytics software

Examples: On-premise and cloud video management systems (VSaaS), AI video analytics, face and licence plate recognition, PSIM

VMS software is a product with digital elements under the CRA and, when it includes AI analytics, may fall under the AI Act, up to prohibited or high-risk biometric cases. Cloud versions add service-provider obligations: NIS2, the Data Act and the role of data processor.

Most common problems

AI features and the AI Act

Object or intrusion detection is generally minimal risk. Remote biometric identification is high-risk, and some uses are prohibited: real-time identification by law enforcement in public spaces (with exceptions), emotion recognition at work and in schools, building facial databases by scraping.

Provider or deployer

Whoever develops the analytics module is the "provider" under the AI Act; the customer using it is the "deployer". Instructions for use and the ability to disable features per country become part of compliance.

Vulnerabilities and updates

Since 11 September 2026 actively exploited vulnerabilities must be reported within 24 hours. You need a patch release process compatible with on-premise installations that customers often do not update.

Cloud and data transfers

In VSaaS the vendor is a data processor (Art. 28 GDPR), must manage transfers outside the EU and allow switching providers under the Data Act.

Biometrics in the US

State laws such as Illinois' BIPA require written consent and damages of up to $5,000 per violation: a real risk for face recognition features.

NIS2 customer requirements

Customers in critical sectors ask for security questionnaires, contract clauses, SBOMs and vulnerability response times as a condition of purchase.

IEC 62443 standards

For VMS used in critical infrastructure and OT environments, customers ask for IEC 62443-4-1 (secure development process) and often 4-2 for the application. 4-1 maps well to the CRA's process obligations: vulnerability handling, updates, documentation.

Find the rules for your product

Choose the product type, markets and features: get the list of rules that are likely to apply, with the reason why.

Product type
Sales markets

Europe

Americas

Asia-Pacific

Middle East

Features

4 rules and requirements to consider

European Union

  • MandatoryCyber Resilience Act

    Essential cybersecurity requirements, vulnerability handling, SBOM, updates for at least 5 years and CE marking. Exploited vulnerability reporting from 11 September 2026, full application from 11 December 2027. Normally default category; Class I or II if the product includes identity management, privileged access, SIEM or hypervisors.

    Regulation page →
  • Depends on useAI Act

    Non-biometric analytics (object detection, intrusion, counting) are generally minimal risk, but AI literacy is required and, if the system is a safety component of critical infrastructure, a high-risk check is needed.

    Regulation page →
  • Depends on useGDPR – privacy by design and cloud role

    Customers must comply with the GDPR (EDPB Guidelines 3/2019 on video surveillance) and require products compliant with Art. 25.

    Regulation page →
  • Depends on useItaly – Workers' Statute (Art. 4)

    Systems that may allow remote monitoring of workers require a union agreement or authorisation from the Labour Inspectorate. Masking features and documented configurations help Italian customers.

    Text or source →

The result is general guidance, not a legal assessment: the exact classification depends on the product's features and intended use.

What to prepare

  • Classify the software under the CRA (normally default category)
  • Map each analytics feature under the AI Act (prohibited, high-risk, transparency, minimal)
  • Be able to disable biometric features per country or customer
  • Technical documentation and instructions for use for AI modules
  • PSIRT, SBOM and a 24-hour reporting process
  • Customer features: roles and permissions, audit logs, configurable retention, masking, controlled export
  • For cloud: Art. 28 DPA, EU data region, exit plan and data export
  • Ready answers to customers' NIS2 questionnaires
  • Development process compliant with IEC 62443-4-1 and possible 4-2 certification for OT customers