Document Retention
Features
Benefits
White Papers
Data Services
Technology
Digital Thread
Architecture
Security
Hosted Security

nextPage® security strategies

use secure channels

NextPage requires minimal communication between NextPage clients and the Global Service, and the transport is completely compatible with standard firewall configurations.

Secure Communication

The Global Service never attempts to contact a NextPage client. Instead, each client periodically polls the Global Service (via HTTP/80) to check whether it has a message to retrieve. If there is a message, it conducts a secure conversation (via HTTPS/443) to pull the message. Similarly, if the client has information to push, it does so securely (via HTTPS/443).

Because messages are always outbound from a NextPage client to the Global Service, the system is compatible with network address translation (NAT), which has become de rigueur for private networks. The NextPage products also uses standard ports (80 and 443), eliminating the need to open non-standard ports in the firewall.

Proxy Servers
If your organization employs a proxy server, the NextPage service will automatically take advantage of browser settings in Microsoft Internet Explorer. Because it uses the WinInet API for network access, it will work in any network environment from which users are able to browse public Internet sites using Internet Explorer.
Communication Latency
The NextPage client service is architected to be immune to communication latencies introduced by security equipment such as proxy servers. This is possible because the NextPage client is designed to run smoothly when connectivity is intermittent or absent. Communication is asynchronous, so user operations are not blocked while the client waits for a response from the NextPage Global Service.
Non-Executable Metadata

The metadata sent between a NextPage client and the global service contain no executable code. They follow rigidly controlled formats that are not amenable to hijacking by a virus or macro worm.