It's time to talk about Security on our networks.

[Jay Ashworth]

And that, right there, is why your DMX doesn't run your flyrail.

(Yes, yes, I know; there are dozens of other reasons. But we (internet engineering people) try really hard, we do, to keep people from hooking things to the internet that can actually hurt actual people.

 

[RickR]

By the same token, you could say that about ControlBooth. We take great care and effort to ensure data security, but nothing is able to be a 100% guarantee. A zero-day exploit could target our server, even though we are diligent about keeping it up to date. Best we can ask for is a policy that states our goals and an understanding that it would hurt us, as much, if not more than our customers.

And therefore I limit what information you have. Once out it can not be retrieved! Ongoing access to an entire show critical network takes some deep trust.

 

[Rob]

Ongoing access to an entire show critical network takes some deep trust.

You should have a look at our SixEye device profiles exposed on the portal and SixEye's extensive permission database. Pathway only exposes some of the properties of the devices. Those that are handy to an administrator, such as device re-boot, are locked out to all other users. Allowing general invited staff read-only access to properties like device up-time and DMX Levels are benign and pose no risk to the performance, but can aid in debugging a system.

We have thought about this.