| Allow only manager PCs access to factory GP data |
Set the GP-Web server's IIS Security settings to prevent anonymous access and allow log-ins only from authorized user accounts. This will prevent other PCs and unauthorized users from accessing valuable GP data.
|
| Design your system so data collection will not be effected by a GP-Web server crash |
Use separate PCs for GP data collection, and for the GP-Web server. Then, install the GP-Web Traffic Center and Pro-Server with Pro-Studio version 3.0 programs in the data collection PC, and install the GP-Web Traffic Center program on the Web server PC. Use the GP-Web Traffic Center program's routing feature to allow both PCs to easily share data.
|
| Prevent unauthorized writing of data by a third party |
Be sure to specify all the users authorized to write to the GP-Web Traffic Center Program, where you can set each user's log-in level. This will prevent unauthorized users from receiving write access.
|
| Eliminate line-stops due to illegal GP-Web server access |
Be sure to design your system so that it uses separate hardware for the GP-Web server and the data collection PC. Also, set up a security device, such as a fire-wall, between these PCs to prevent unauthorized access to your data collection system, even if the GP-Web server is accessed.
|
| Prevent unauthorized Internet monitoring of GP data |
Set up a virtual private network (VPN) in the GP-Web server and in the client PCs used by managers, which only allows access via the VPN. This will provide a high level of security, since all data is encrypted.
|
| Preventing hacking of Website contents |
| On the NTFS formatted hard disk drive, create a folder that is visible on the Web. Set this folder so that only the network administrator is able to write to or delete this folder's data. This will prevent hacking of Website data. |
|
