For those networks without a proxy Web server, Panda GateDefender Performa includes, from version 4.00.00, a Web cache server.
This server accelerates the download of pages and files via HTTP and HTTPS. Additionally, by implementing authentication methods that use local databases or LDAP, its use can be restricted to specific network users, integrating with the user management infrastructure already installed.
If Panda GateDefender Performa is not operating on the network infrastructure along with a proxy, you will have to enable the internal (explicit) proxy for the various HTTP/HTTPs protection profiles depending on the user.
Finally, the integrated proxy also helps to configure and deploy protection profiles and prevents installing and configuring validation servers on the corporate network. This allows you to optimize the number of servers.
Features and specifications
You can only access the internal proxy through the internal networks configured in the appliance. If there are no internal networks, the proxy will be disabled.
As with other types of proxy, the user must be included in one of the local or remote groups (LDAP servers) defined in Panda GateDefender Performa. The protection profile will be defined by the group to which the user belongs.
The user must be able to authenticate in the Panda GateDefender Performa internal proxy. Although this authentication is optional, a profile must be applied. To access the internal proxy, the IP of the user must belong to one of the internal networks configured in Panda GateDefender Performa.
There are two different ports for HTTP and HTTPS.
It is also possible to enable a Web page cache to speed up browsing. Similarly, you can clear the proxy cache on-demand (the size of the cache is 1024 MB).
There are entries in the security reports for restricted access attempts via the explicit proxy.
Restricted access attempts generate a system event which can be seen in the Security reports
screen. In the Warnings settings screen you can configure this event to be notified to a remote Syslog server.