![]() Your browser will not send an HTTPS request to your proxy if you try to redirect traffic transparently. With the transparent proxy setup, however, you will have a problem with HTTPS filtering because it violates the browser restriction for man-in-the-middle attacks. In principle, you can reduce the setup overhead by operating a transparent proxy server, but even then the devil is in the details. If you use an HTTP proxy server, for example, all your browser settings need to be edited. The challenge for the system administrator is to create a filtering infrastructure that does not require individual employees to change their work environments. The big result is that the web proxy agents only act as local web proxies for each individual user, which means no problems with network performance. Both are local web proxies themselves and can do everything that classic web filters offer, including blocking IP hosts. NxFilter also solves this limitation by implementing its own web proxy filtering through its agents NxLogon and NxClient. For example, you cannot enforce a secure search or keyword filtering for URLs because it is done at the DNS level. Much can be said for the use of a DNS filtering mechanism on a corporate network, but in practice, it leads to functional limitations. ![]() NxLogon is the AD single-sign-on agent for NxFilter, and NxClient is the remote user filter of the environment. To control the server, two agents, NxLogon and NxClient, provide convenient web-based applications to block UltraSurf, Tor, Skype, Minecraft, and so on. These methods result in potential approaches for the use of NxFilter in corporate networks, because it can differentiate between users and apply specific filtering policies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |