Ketura is intended only for deployment on internal networks on which all users and machines are trusted. Araxis strongly recommends that it not be installed on insecure networks or machines.
Making Ketura available to remote users
If your organization wishes to make Ketura available to remote users (that is, those not at the same physical location as the Ketura server) over the Internet, a Virtual Private Network should be used to secure communications between the users’ web browsers and the Ketura server. Under no circumstances should a Ketura server be made available directly to users over the Internet.
Please consult your organization’s network administrator if you wish to make Ketura available to remote users.
How Ketura clients communicate with the Ketura server
Users communicate with the Ketura server from their web browsers over the network using the HTTP protocol. This protocol does not encrypt information, and so anyone with access to the network could potentially monitor the information being sent between users’ web browsers and the Ketura server. If this is not acceptable, a Virtual Private Network should be employed to secure the communication.