What is "On Your Network" vs. "Not on Your Network"?
What is "On Your Network" vs. "Not on Your Network"?
In the world of wireless document cameras, especially for educational districts, security is paramount. With devices like cameras increasingly connected wirelessly, understanding whether a device is truly "on your network" or isolated from it can mean the difference between a secure setup and a potential catastrophe. This distinction isn't just technical jargon—it's about protecting your entire network from vulnerabilities that could lead to data breaches, surveillance risks, or even botnet attacks. Drawing from the architecture of HoverCam's Orbit Pro/Air and comparisons to other wireless cameras, let's break down what these terms really mean and why it matters.
The Risks of Wireless Cameras in Educational Settings
Wireless document cameras offer convenience for teachers, allowing seamless integration into classrooms without cumbersome cables. However, they can introduce serious network vulnerabilities if not designed with security in mind. Remember the 2016 Mirai botnet attack? IoT devices like cameras with default passwords were hijacked to launch massive DDoS attacks. Your district's camera system could similarly be turned into a botnet—or worse, a surveillance tool for attackers.
Common vulnerabilities in other wireless cameras include:
Requiring a global password for setup, creating a single point of failure that can compromise your entire network.
Directly accessing your Wi-Fi network, meaning any breach in the camera could lead to district-wide network failure.
Needing special software and/or network drivers, which expose teachers' computers to Trojan Horse or back-door attacks.
Vendor software that lacks proper certification and security inspection, potentially presenting the worst network breach by opening access to student and faculty information systems. Even with measures in place, network-accessing software is never 100% safe.
These issues highlight why simply going wireless isn't enough— the way the device connects matters.
The Misconception: USB Dongles Don't Always Mean Isolation
Many customers are quick to conclude a vendor's wireless camera products or a casting solution is safe because they use a USB plugged-in dongle as a second NIC card. However, this is misleading, because connecting to the 2nd NIC card on a computer does not eliminate the need for the camera to connect as a network device. Therefore, it requires the vendor to install their proprietary network driver and app software, and the newly installed driver and app are unaudited potentially risky code leaving the possibility of a backdoor or trojan unexamined.
The driver and app they install is on the customer's computer, and any breach on their code is a direct breach of your network. Therefore, even if they use a second NIC card plugged into the computer's USB port, they should still be considered "on your network."
This setup bypasses the system's built-in security, making the entire network vulnerable. The diagram below illustrates this peer-to-peer or vendor NIC approach, where the camera connects via an AP, PC NIC, or vendor NIC, directly integrating with the network and requiring apps/drivers that are prone to backdoor attacks.
In essence, "on your network" means the device is part of your Wi-Fi or local network infrastructure, exposing it (and everything connected) to external threats through shared access points, required software, and potential unvetted code.
Orbit's Approach: Truly "Not on Your Network"
This is in contrast to Orbit's architecture, where the Orbit camera or dongle is not only plugged into a USB port of the host computer, but also as USB UVC or UAC or HID devices, not as a network device. The host computer's built-in generic driver handles them as USB devices which is accessible to any local app as a system resource, or webcam, or microphone, or peripheral. The Orbit's connection is like a fire gap between its internal network link and the computer by switching to a local USB wired connection. Any breach on the Orbit's internal network is isolated from the host computer. That's what we meant by "Not on your network," and it is much safer, by design.
HoverCam's Orbit Pro/Air stands out as the only safe bet for wireless document cameras because it avoids these pitfalls entirely:
Rather than connecting as a network device to your computer, Orbit is the only camera that connects through USB as a locked-down and trusted local device. Orbit is NOT on your network and presents near-zero vulnerabilities.
Orbit uses a patented isolated closed-loop wireless link between two locked-down Tx and Rx dongles that will not access your Wi-Fi network.
Each Orbit pair is uniquely encrypted end-to-end. No global or default passwords.
With Orbit, you don't need to download any drivers or software—it works with the generic drivers already built into your operating system. No new software = no new vulnerabilities.
Orbit Pro even takes security to another level: mmWave signals are confined inside of each classroom. Without being physically present in the room, it is simply not possible to even attempt a hack against any of our cameras.
Comparison Table: Orbit vs. Other Wireless Cameras
Based on the security features and architectures discussed, here's a high-level comparison table to illustrate the key differences:
| Feature | Orbit Pro/Air | Other Wireless Cameras |
|---|---|---|
| Network Connection | Not on your network; isolated USB as UVC/UAC/HID device | On your network; connects as network device via Wi-Fi or vendor NIC |
| Required Software/Drivers | None; uses built-in OS generic drivers | Proprietary apps and drivers required, vulnerable to backdoors/Trojans |
| Password Setup | Unique end-to-end encryption per pair; no global/default passwords | Often uses global passwords; single point of failure |
| Attack Surface | Near zero; isolated closed-loop wireless link | High; direct network access leads to potential district-wide breaches |
| Physical Security | mmWave signals confined to room (Pro model) | No such confinement; accessible remotely |
| Vulnerability to Breaches | Breaches isolated from host computer (fire gap via USB) | Direct breach to network via installed code |
| Overall Safety | High; designed for zero network exposure | Low; exposes computers to unaudited risks |
This table underscores why Orbit minimizes risks while others amplify them through network integration.
Why This Matters for Your District
In an era where cyber threats target educational institutions for sensitive data, choosing a wireless camera that's truly "not on your network" isn't optional—it's essential. Orbit's design ensures that even if a breach occurs in its internal link, it doesn't propagate to your broader network, unlike competitors that rely on potentially risky software and direct connections. By opting for Orbit, districts can enjoy wireless convenience without compromising security.
If you're considering wireless cameras for your classrooms, prioritize architectures like Orbit's that keep devices off the network. For more details on HoverCam Orbit Pro/Air, visit their official resources or consult with IT security experts to evaluate your setup.
This post is based on security documentation and architectural comparisons from HoverCam.