• Overview
• Enterprise Connectivity
• Defense in Depth
• Features
• Request Demo

The eCentre enterprise application server can reside on one or more servers, depending on the number of machines that are going to be connected at the site. The eCentre server(s) are located in a factory's DMZ and are connected to a factory's VPN terminal device. Each of the servers utilize a software firewall to ensure that internal connections between the servers is made only by validated ports, thereby reducing the risk of an internal attack. Once these servers have been connected to the factory's equipment LAN, then equipment, selected by the system administrator, and secureWISE users may be registered to the eCentre server.

Ease of Access

To initiate machine registration, the system administrator must first authorize an eCentre system installation pack be installed on each of the selected machines. The installation pack includes an eCentre client and a subset of multiple system drivers that enable communication to and from the machine and the eCentre server. The installation pack is tailored to each machine's operating system and eCentre feature selection. In most deployments, the eCentre installation pack will be tested by the machine's manufacturer or equipment owner to ensure that there are no operating limitations encountered when running the eCentre client or system drivers while operating the machine in production.

Ease of Management

Next, the system administrator will assign a list of secureWISE users' to a team, define their access rights, their session privileges, and a complete listing of files and/or commands that may be accessed by each team member. When registering team members, the system administrator uses a simple hierarchal graphic interface to group like users into roles and assign or deny privileges to each. There are no CD's to distribute to team members as the Collaborative Client can be automatically downloaded to the client machine from the eCentre server on site. When team members log on for the first time they will be authenticated based on the password provided by the administrator and instructed to create a new password for future use with eCentre. Weak passwords will not be accepted and users will be prompted to change passwords based on a time interval set by the system administrator.

Ease of Use

When registration of the machines and team members is complete the system administrator can begin creating user sessions. Each session defines the list of specific machine(s) and team members that will be connected in a collaborative session via the eCentre collaborative client. The sessions can be created and stored in the eCentre server for future use, or activated immediately as required. Session management functions can also be delegated to an alternate administrator(s). The authority and privilege setting rights of these delegated administrators can be set by the master administrator to limit the extent of changes that they may grant to users or what equipment that they may include in a session.