Treat CallPilot servers as closed systems. Customers must not install unauthorized software on any CallPilot server.
See Part 1 of the CallPilot Installation and Configuration binder.
Ensure that each CallPilot server is physically secured.
See Part 2 of the CallPilot Installation and Configuration binder for your platform.
Ensure that all CallPilot backup tapes are physically secured.
[MCRAE, Linda] Administrator's Guide
Ensure that all passwords to Windows NT accounts are changed from their default values to strong values known only by the customer. This includes the ìgamrootî account used for the AR352 RAID card. CallPilot security is ultimately only as good as the passwords used.
See Parts 3 and 5 of the CallPilot Installation and Configuration binder for your platform.
Always run he CallPilot server with its console in a logged out state.
Do not map remote drives onto a CallPilot server.
[MCRAE, Linda]Adminstrator's Guide/Preventive Maintenance checklist
Do not map a CallPilot server drive onto another server.
[MCRAE, Linda]Adminstrator's Guide/Preventive Maintenance checklist
Do not add additional users or shares to a CallPilot server.
[MCRAE, Linda]Adminstrator's Guide/Preventive Maintenance checklist
The CallPilot server should be connected inside the customer’s LAN firewall.
See Part 1 of the CallPilot Installation and Configuration binder.
Install and configure one of the authorized third party anti-virus solutions according to Nortel recommendations.
Caution: Do not install third party anti-virus software unless it has been approved by your IT department.
See Part 4 of the CallPilot Installation and Configuration binder for your platform.
Disable the remote access modem unless needed.
[MCRAE, Linda] could be stated Part 2 server installation [MCRAE, Linda] ; should also be stated in Administrator's Guide/Preventive Maintenance checklist