Reply to thread

Message

<blockquote data-quote="ForgottenSeer 58943" data-source="post: 838180">I am also unaware of any specific reviews regarding security. However, if you follow best practice, you can be pretty effective in securing them. Emerson Sensi is used by a log of folks I know in IT. The reason is, there is a long code printed on the back of the thermostat itself that is required to connect to it. Anyone not having that code paired to their account won&#039;t be able to connect or access it in any way.For IoT I like to do the following;1) Secure them on their own guest WiFi SSID. (or VLAN)2) Secure them behind a Gryphon, under a strict USER with &#039;Toddler&#039; as the policy and only permit the egress necessary for device functionality.That way, in general, it&#039;s not going to be compromised because nothing is WAN facing other than exactly what is needed for the operation, and the device is secured on it&#039;s own VLAN (or Guest SSID)</blockquote>

[QUOTE="ForgottenSeer 58943, post: 838180"] I am also unaware of any specific reviews regarding security. However, if you follow best practice, you can be pretty effective in securing them. Emerson Sensi is used by a log of folks I know in IT. The reason is, there is a long code printed on the back of the thermostat itself that is required to connect to it. Anyone not having that code paired to their account won't be able to connect or access it in any way. For IoT I like to do the following; 1) Secure them on their own guest WiFi SSID. (or VLAN) 2) Secure them behind a Gryphon, under a strict USER with 'Toddler' as the policy and only permit the egress necessary for device functionality. That way, in general, it's not going to be compromised because nothing is WAN facing other than exactly what is needed for the operation, and the device is secured on it's own VLAN (or Guest SSID) [/QUOTE]

Verification