iPrism Internet Filter Network Integration . . .

iPrism can be deployed in a networking environment in several different ways. The two most commonly used configurations are:

• To insert iPrism on the network and use as a proxy
• To insert iPrism as a bridge between an external router and an internal hub/switch. (It is also common to place iPrism between the core hub/switch and a firewall.)

The network diagrams below demonstrate hoe iPrism can be integrated into a number of different network topologies:

iPrism Using a Single Interface

This configuration hat the least physical impact on the network and requires only a single IP address.

All HTTP requests originating from workstations will go through iPrism before being sent out to their destinations.

To achieve this, either the switch needs to be configured to redirect HTTP requests to iPrism, or, the workstations must be configured to use iPrism as a proxy server.

iPrism as a bridge

( Simple Network )

In a simple network the iPrism internet filter is best deployed between the hub/switch that connects the local subnet, and the router that connects out to the internet.

iPrism as a Bridge

( Complex Network )

In a complex network the iPrism internet filter should be employed inside the firewall. If iPrism is outside the firewall, it may not "see" the individual workstations on the network, and will not be able to do any individual user tracking or monitoring.

iPrism as a Bridge

( Routed Network )

In a routed network, the client connects to a remote network on which iPrism is employed.

In order for iPrism to "see" the client workstations, you must specify a "static route" in iPrism. In this case, the static route would specify that the LAN IP address from the Internet router (1) be used as the gateway to the network.