Required external resources for web protection solutions
- Forcepoint Web Security, v8.5.x
- Forcepoint URL Filtering, v8.5.x
- TCP/IP
Policy enforcement is available for TCP/IP-based networks only.
- DNS server
A DNS server is used to resolve requested URLs to an IP address. Content Gateway, Network Agent, or your third-party integration product requires efficient DNS performance. DNS servers should be fast enough to support policy enforcement without becoming overloaded.
- Directory services
If web protection software is configured to apply user- and group-based policies, User Service queries the directory service for user information. Although these users and group relationships are cached, directory service machines must have the resources to respond rapidly if web protection components request user information. See System requirements for this version, for supported directory services.
For information on configuring web protection software to communicate with a supported directory service, see the Administrator Help. Web protection components do not need to run on the same operating system as the directory service.
- Network efficiency
The ability to connect to resources such as the DNS server and directory services is critical. Minimize network latency for efficient Filtering Service performance. Excessive delays under high load circumstances can impact Filtering Service and may cause lapses in policy enforcement.
- Microsoft SQL Server
A supported version of Microsoft SQL Server is required to host the Log Database, which stores reporting data. See System requirements for this version for supported SQL Server versions.
- SQL Server Standard or Enterprise works best for larger networks, or networks with a high volume of Internet activity, because of its capacity for storing large amounts of data over longer periods of time (several weeks or months).
- SQL Server Express, a free, limited-performance database engine bundled into the Forcepoint Security Installer in certain versions, is best-suited to evaluation or proof of concept deployments. It can also be used by organizations with a low volume of Internet activity, or organizations planning to generate reports on only short periods of time (for example, daily or weekly archived reports, rather than historical reports over longer time periods).