How to Vet Security Camera Vendor Demos to Protect Sensitive Spaces

Introduction

In a striking incident, a city discovered that a security camera vendor, Flock, had accessed live feeds from a children's gymnastics room during a sales demo—without explicit permission. Even after the city learned of this breach, it renewed the contract anyway. This case underscores the critical need for organizations to establish strict protocols when vetting vendor demos, especially in sensitive areas like childcare facilities, changing rooms, or private offices. By following a structured approach, you can prevent unauthorized access, protect privacy, and maintain trust. This guide provides a step-by-step process to ensure that vendor demonstrations never compromise the security of your most vulnerable spaces.

What You Need

• A written demo access policy that defines permissible activities during vendor presentations.
• A current list of sensitive or restricted areas where cameras cannot stream live feeds to external parties.
• Technical controls to isolate demo networks or simulate feeds (e.g., sandboxed environment, recorded footage).
• Legal and privacy review templates for vendor agreements and non-disclosure statements.
• Audit logs or monitoring tools to track all access during demos.
• Internal approval chain (e.g., IT, security, legal) that must sign off on each demo request.

Step-by-Step Guide

Step 1: Identify and Map Sensitive Areas

Before any vendor demo begins, walk through your facility and pinpoint all spaces that require the highest privacy protection. These may include children's rooms, locker rooms, medical offices, or executive meeting rooms. Create a formal list and mark them clearly on floor plans. This proactive step ensures that no live feed from these zones ever appears on a vendor's screen. Without such mapping, you risk repeating the mistake of the city that allowed a children's gym to become a demo showcase.

Step 2: Draft a Comprehensive Demo Access Policy

Develop a policy that explicitly states: Live feeds from sensitive areas are never to be accessed, recorded, or transmitted during any demo. The policy should cover all aspects of vendor interaction—preparation, execution, and post-demo handling. Include language about using only simulated or pre-recorded footage, and about requiring signed acknowledgement from vendors. Reference Step 1 to tie the policy directly to your facility's unique sensitive zones.

Step 3: Get Vendor Agreement in Writing

Before the demo date, send the policy to the vendor and obtain a signed agreement. This document should state that the vendor understands and will comply with all restrictions. If the vendor balks at any clause—especially the prohibition against live feeds from sensitive spaces—consider that a red flag. In the Flock case, the vendor apparently used the demo as a sales pitch by accessing real feeds; a signed policy would have made that violation a contractual breach.

Step 4: Use an Isolated Test Environment

For the actual demo, set up a completely separate network or a sandboxed system. Never give vendors direct access to your production camera feeds. Instead, provide either recorded footage from non-sensitive areas or a simulated environment that mirrors camera functionality without real data. This isolates your live operations and prevents any accidental (or intentional) streaming of protected spaces. Even if the vendor has the best intentions, technical isolation is your strongest safeguard.

Step 5: Monitor and Log All Vendor Actions

During the demo, have a staff member observe or deploy automated logging that records every system access, command executed, and feed viewed. If a vendor attempts to switch from simulated to live feeds, the log will catch it. After the session, review these logs before sending the vendor away. The city in the Flock incident might have discovered the gym access earlier if it had been monitoring in real time.

Step 6: Conduct a Post-Demo Audit

Immediately after the demo, perform a thorough audit. Check access logs, review any recordings made, and question the vendor about specific actions. Verify that no sensitive areas were accessed. If you find any unauthorized access, escalate immediately and refuse to renew or continue the contract until the issue is resolved and remediation steps are taken. The city's decision to renew despite knowing of the breach suggests a lack of follow-through—something a robust audit process can prevent.

Step 7: Evaluate the Vendor's Security Culture

Use the demo experience as a data point to assess the vendor's overall attitude toward privacy and security. Did they voluntarily comply with your policy? Were they transparent about their methods? Vendors who treat privacy as an afterthought are more likely to cut corners in other areas. Consider this evaluation when negotiating the final contract. If the vendor demonstrated problematic behavior (like accessing a children's room for a sales pitch), it may be wise to look elsewhere, even if the product seems excellent.

Step 8: Establish Ongoing Oversight and Periodic Audits

After signing a contract, do not relax vigilance. Build into the agreement the right to conduct unannounced audits of vendor access to your systems. Schedule regular reviews of access logs and hold quarterly privacy meetings with the vendor. Continuous oversight ensures that the vendor's demo-day behavior was not an isolated incident and that they maintain high standards throughout the relationship.

Tips for Success

• Never allow live feeds from sensitive areas during any demo, even if the vendor claims it's necessary for a proper evaluation. There are always alternative methods (simulated data, test labs).
• Include contractual penalties for unauthorized access to camera feeds, such as termination of contract without penalty to your organization.
• Involve legal and privacy officers from the very first vendor contact. They can help tailor policies to comply with local laws (e.g., COPPA, GDPR).
• Train your own staff to recognize red flags during demos—like a vendor asking to 'just quickly check' a live feed from a sensitive zone. Empower them to stop the demo.
• Document everything: every step of the demo, every log entry, every agreement. This paper trail protects you if a privacy incident occurs later.
• Remember the lesson from Flock: a vendor's eagerness to demo real feeds may reveal a deeper disregard for privacy. Let that inform your decision—not just the functionality of their product.

By following these steps, you can avoid the pitfalls that led to a city's children's gymnastics room being used as a sales tool. Protect your sensitive spaces, your reputation, and most importantly, the people who rely on you to keep them safe.