FAQs Archive

Q: Do users share the username and password to access their CORIS account?

No, each user sets up their own unique username and password to access the account.

Q: Can an unauthorized user intercept the wireless signal to read or modify the temperature readings?

No. In addition to DNS protection, we use AES128 encryption for all temperature data transmitted from the sensor to the cloud, and back to the sensor. We also use an additional layer of TLS encryption between the CORIS Gateway and the cloud. LoRa communications include enhanced security to guard against data capture during wireless transmission.

Q: Does CORIS use Wi-Fi for communications?

CORIS does not use Wi-Fi. The CORIS system runs on LoRa wireless communications, which has much greater range and security than Wi-Fi.

Q: Will my IT department need to put a “hole” in the firewall to allow CORIS equipment to communicate with the internet?

No modification or configuration of the firewall is required. This is a unique feature of the CORIS system. CORIS has two network security patents that allow CORIS devices to communicate with its cloud servers without any new configuration or permissions in the firewall.

Q: Does the CORIS Gateway require a static (dedicated) IP address?

No, the CORIS Gateway uses DHCP to obtain a local IP address, and to find the IP address of a DNS server. Gateways can be provisioned with static IPs if required.

Q: How do CORIS sensors communicate readings to the CORIS servers in the cloud?

The CORIS sensors wirelessly transmit temperature and other sensor readings to the local CORIS Gateway, which forwards them to the CORIS servers in the cloud.