General operational and educational information for corrections professionals. Not legal, medical, or compliance advice, and not a certification of compliance with any law or standard. Policies and standards vary by agency and jurisdiction; follow your facility's policy and your own legal, medical, and professional advisors.
The IT questions about correctional video monitoring are the normal ones: what touches the network, what leaves the building, who can see what, how access is controlled, and what happens when something fails. This page answers them at the level a county IT director needs before a deployment conversation, and flags the items that must be confirmed against your specific environment.
Most county jails run an existing IP camera system with a recorder, often from a mainstream manufacturer, sometimes a mixed estate accumulated over a decade. The realistic starting position is that some cameras are modern, some are analog behind an encoder, and documentation of the estate is incomplete.
The first technical task in any engagement is therefore an inventory: what cameras exist, what they actually see, what protocols they speak, and which ones are working. Facilities are routinely surprised by how many cameras are recording something other than what the map says.
Design intent is to consume existing streams rather than to require a rip and replace. Where a specific camera cannot be integrated or its image is unusable, that should be stated plainly rather than papered over.
The questions to settle before anything is connected: which VLAN the camera estate lives on, whether any outbound connectivity is permitted from it, what is required at the firewall, whether processing happens on premises or off, and what data classes leave the building if any.
Video from a correctional facility is sensitive by nature and may be subject to state law, facility policy, and records retention rules. Treat it with the same discipline as other protected data on the county network.
Access control is the item most often underspecified. Define who can view live, who can view recorded, who can export, and whether export actions are logged. An export without an audit trail is a future problem.
Confirm failure behavior in writing. If the link drops or a service stops, the existing camera and recording system should continue to operate as it does today, and staff procedures should not depend on the added layer being up.
Where a deployment touches systems in scope for criminal justice information policy, the applicable requirements are set by your state control agency and your local policy, and the determination is theirs and not a vendor's.
Practical items to raise in review: authentication method and whether it federates with county identity, session and credential handling, patching cadence and responsibility, logging and log retention, physical security of any on-premises appliance, and the offboarding process for departed users.
Ask for the incident response commitment in writing: notification timeline, point of contact, and what the vendor will and will not do during an investigation.
Ask what happens at end of contract. Who holds what data, in what format it is returned, and what the deletion commitment is.
Virtual Patrol is designed to work with the camera infrastructure a facility already owns and to add a review and record layer on top of it, with a person reviewing every raised event before action. No facial recognition is used.
The company supports documentation, discipline, review, and proof. It does not certify any facility as compliant with any security or correctional standard; that determination belongs to the relevant authority.
Specific architecture, hosting, data flow, and control details should be confirmed against your environment during the technical review rather than assumed from a web page. Ask for them in writing and have your security reviewer read them.
Usually not. The approach is built around existing IP camera estates. Individual cameras with unusable image quality or unsupported protocols may not be integrable, and that should be identified during inventory.
That depends on the deployment design chosen for your site. Settle VLAN placement, firewall requirements, and whether processing is on premises before connecting anything, and get the answer in writing.
Access is role based and should be defined by the facility during setup. Define live view, recorded view, and export rights separately, and confirm that export is logged.
No vendor can answer that for your agency. Requirements are applied by your state control agency and your local policy. Route the technical documentation through your normal security review.
Your existing camera and recording system should continue operating as it does today. Confirm the specific failover behavior for your deployment in writing.
No.
Ask for the data return format, the deletion commitment, and the timeline, in the contract rather than in a conversation.
Confirm patch cadence, who initiates, what the maintenance window is, and whether an update can change behavior the facility depends on.
