Abstract

Integrating ATE into a network allows faster software upgrades to operating systems and Test Program Sets (TPS) for ATE systems. Upgrades to operating systems can be made to several ATE stations at one time from one computer TPS can be stored onto a sewer that can be shared by all the ATE stations. This allows upgrades to TPS at one location and not across ad of the ATE stations. Test data, calibration data, and other files on ATE stations can be monitored for troubleshooting of the system. Having ATE stations on a network, however, could pose some security risks if security is not addressed during the integration design process. The designer must have intimate knowledge of the network architecture and network security products to secure access to the equipment and protect the information flow to and from the ATE. The OSI model can assist the designer in understanding the network architecture and understanding at which level of the architecture the different security products can be applied to meet the security goals. At the network architectural level the ATE integrator becomes familiar with routers, switches, hubs, and methods of controlling traffic on a network. At the secured level the ATE integrator addresses which level of the OSI model to secure. Security can be applied at the top of the model at the application layer with products like Public Key Infrastructure (PKI), at the middle of the model at the session layer with products like firewalls, or at the bottom of the model at the physical layer with cryptographic devices. The last item that the designer needs to include during the integration of ATE onto a network is the network administrators.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call