“ONVIF compatible” is not enough: verify the exact model, firmware, and profile

What official conformance means

Source fact: ONVIF identifies its Conformant Products database as the authoritative source for determining whether a product is officially conformant and which profiles it supports. Registration follows successful use of the relevant ONVIF test tool and submission of required documents by an ONVIF member manufacturer.

Conformance is tied to a specific firmware or software version. It remains valid indefinitely for that registered version, but the installed version must match the database entry. ONVIF also requires each specific model in a family to be tested, registered, and listed individually. A database record can identify related products, but the registry expressly notes that related products have not necessarily been individually tested.

Membership and conformance are different. Only qualifying ONVIF members can make conformance claims, yet membership alone does not make every product conformant. Products can use parts of ONVIF specifications without completing the conformance process, but they cannot properly claim ONVIF conformance on that basis.

Read beyond the profile name

ONVIF’s process requires implementation of all mandatory and applicable conditional features for a claimed profile, successful use of its test tools, and submission of a Declaration of Conformance, Feature List, and Interface Guide. A mandatory feature is required for the profile. A conditional feature is required when the product supports that capability, including through a proprietary method. Those documents are therefore more informative than a profile logo alone.

Conformance does not certify image quality, analytic accuracy, storage capacity, cybersecurity hardening, availability, or every project-specific integration. It also does not eliminate the need to test a client and device together. A later firmware release may fix vulnerabilities while no longer matching the exact registered record, so both lifecycle and interoperability evidence need to be retained.

DSE verification checklist

DSE recommendation: This is DSE operational synthesis, not an additional ONVIF certification process.

1. Record manufacturer, full model, hardware revision, installed firmware or software, and product role.
2. Locate the exact record in the ONVIF database; do not substitute a family name or related-product listing.
3. Save the profile list, Feature List, Declaration of Conformance, Interface Guide, and test date.
4. Map mandatory and conditional features to the project’s written requirements.
5. Flag products whose installed version differs from the listed version and obtain manufacturer guidance.
6. Bench-test discovery, authentication, configuration, streams, events, metadata, recording, access decisions, and failure recovery as applicable.
7. Store the evidence with commissioning records and repeat the check before material firmware or client changes.

Official references

• Conformant Products — ONVIF’s authoritative product and version registry.
• Conformance FAQ — model, version, mandatory-feature, and conditional-feature boundaries.
• Conformance Process — test and document requirements for a claim.