Security implications for Private Last Mile

The security risks are low for running Private Last Mile on your system.

Network security

Communication between Private Last Mile and the AppMon-hosted application server is potentially sensitive, because script definitions may embed login credentials for sites under test. To protect this data, the application server transmits all messages over SSL-encrypted secure channels.

Inter-process communication, file access, and user privacy

Private Last Mile does not interact with other programs running on the system, does not open files outside its own installation tree, and does not record user interaction with programs other than the peer.

During installation, Private Last Mile writes the peer's application information into the Windows registry. Otherwise, however, Private Last Mile does not write to the Windows registry, and the registry is accessed only once during startup to retrieve the browser's proxy settings.

Performance data is collected exclusively via autonomous tests run by the instrumented browser simulation embedded in Private Last Mile. Information owned by the end user, such as interactions with the user's personal Web browser, is never examined, nor is it used for any purpose by Private Last Mile.

Proxy servers

Private Last Mile supports operation behind the following proxy servers:

  • Microsoft Internet Security and Acceleration (ISA) Server

  • Squid