IDIS devices, such as NVRs, use a proprietary embedded Linux (i.e. not off-the-shelf) that only authorized network modules can run, and IDIS does not allow any third-party apps to run inside the IP camera. Since IDIS leverages proprietary protocols, this makes them very difficult to exploit. IDIS has also developed proprietary file structures whereas some manufacturers use Windows or off-the-shelf Linux, another example of IDIS hardening network resilience. Even a common network module, such as our HTTP/HTTPS server, is a proprietary implementation, which will make many known attacks ineffective. IDIS also uses industry-standard SSL/TLS when communicating across a network as well as the encryption of login details, IP filtering, IEEE 801.1x, and TLS/SMTP.
Often times, there are concerns that manufacturers can access an end user’s system. With IDIS, technology users’ passwords are encrypted. For example, if an administrator account password for an NVR is lost, then there is no way to reset it, even by IDIS engineers who designed the system. Unlike other manufacturers, IDIS does not use “backdoors.” These “backdoors” are typically used to gain access and provide remote customer support, but at the same time, they can spur fears of spying and espionage. There are recovery options with IDIS systems, but these need to be set up by the installer when the system is implemented. So, for the sake of network security, IDIS cannot access any of its own installed systems.