EVENTS / BUYER WORKSHEET
Security Trade Show Research Checklist for CCTV Buyers and Integrators
A security trade show checklist helps CCTV buyers and integrators compare vendors on the same evidence: scene performance, network and storage conditions, cybersecurity lifecycle, interoperability, privacy, support, and total ownership responsibility.
Updated 2026-08-31 · Events
- PURPOSE
- State the scene, target, image task, operating hours, movement, light, retention, users, network boundary, and failure condition. Add the commercial decision: new installation, replacement, expansion, cloud migration, support renewal, or compliance review.
- CONDITIONS
- A written decision prevents a show-floor feature from becoming the requirement by default. It also makes later quotes and proof-of-concept tests comparable. Ask how the product performs at the actual target distance and lighting, what bitrate and storage assumptions apply, how firmware and vulnerabilities are handled, how remote support is authorized and logged, where cloud or analytics data travels, what ONVIF or other integration is supported, and how accounts, exports, backups, replacement, and end-of-life work.
- LIMITS
- This is a planning or editorial guide. It does not replace a site survey, current official source, legal review, or vendor acceptance test.
Define the decision before the demo
State the scene, target, image task, operating hours, movement, light, retention, users, network boundary, and failure condition. Add the commercial decision: new installation, replacement, expansion, cloud migration, support renewal, or compliance review.
A written decision prevents a show-floor feature from becoming the requirement by default. It also makes later quotes and proof-of-concept tests comparable.
Ask the same questions at every booth
Ask how the product performs at the actual target distance and lighting, what bitrate and storage assumptions apply, how firmware and vulnerabilities are handled, how remote support is authorized and logged, where cloud or analytics data travels, what ONVIF or other integration is supported, and how accounts, exports, backups, replacement, and end-of-life work.
For physical-security convergence, ask how access events, alarms, identity, and video are correlated, which protocol owns each path, and what happens when a network, power, controller, or cloud dependency fails.
Leave with a comparable record
Record vendor, exact model, firmware or software version, feature claim, source document, missing answer, price or licensing assumption, support boundary, data path, and required test. After the show, score only the requirements with evidence and keep unknowns visible.
Use the record to request a proof of concept, acceptance test, risk review, supplier review, and implementation quote. A trade show is the start of research, not the final commissioning result.
FIELD CHECKLIST
Record the result, not only the intention
- Write the use case, image task, operating condition, and commercial decision.
- Ask identical scene, network, storage, cyber, privacy, integration, and lifecycle questions.
- Record the exact product, firmware, claim, source, assumption, and unanswered question.
- Separate mandatory requirements, desirable features, and marketing demonstrations.
- Convert shortlisted claims into proof-of-concept and acceptance tests.
- Keep vendor, cloud, support, data, renewal, and exit responsibilities in the decision record.
Sources to verify
- ISC West — Why attend
Official event scope, exhibitor categories, education, and convergence information.
- NIST SP 800-213 IoT device cybersecurity guidance
A reference for cybersecurity considerations during IoT device selection, acquisition, deployment, and use.
- SIA security industry events calendar
Use the industry association calendar to verify recurring ISC and related event dates.
FAQ / LONG-TAIL QUESTIONS
Frequently asked questions
What should I ask a CCTV vendor at a trade show?
Ask about the image task, lighting and motion limits, codec and bitrate, firmware support, vulnerability reporting, remote access, cloud data paths, ONVIF or other integration scope, warranty, replacement, and exit or export behavior.
How do you compare security expo exhibitors fairly?
Use the same written requirements, record model and firmware, separate mandatory from optional features, request evidence, note unanswered questions, and schedule an authorized proof-of-concept or acceptance test after the show.
What should a physical security technology evaluation record?
Record the use case, target zone, system boundaries, vendor and product, claims, source documents, data and support paths, cost assumptions, risks, test owner, decision date, and conditions that would change the result.