Remote Host2 minutes to read
Imagine a hierarchical organization with a massive number of users and resources with the following organization setup:
With the above organization setup, the audits and reports reflect the IP address of the load balancer/proxy server through which the user request(s) is forwarded instead of the actual user machines' IP addresses. When multiple requests occur consecutively, the same IP address (of the load balancer/proxy server) is captured for all the user requests under audits and reports. Because of this, none knows who accessed what and the exact user access information is also lost. Here comes the need for the Remote Host Header - it identifies the IP addresses of user machines accessing target endpoints through the load balancer or proxy server. As a result, the product audits and reports provide good visibility into user access. PrerequisiteBefore configuring Remote Host, find the request header information (e.g., X-Real-IP, X-Forward-For, etc.) in the 'conf' file of your load balancer/proxy server. Notes:
| |