- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
You can configure a proxy server to limit outbound access from EPM agents to the EPM service only. You can also use any other proxy server that follows the communication methods described below.
The following example shows how a Squid proxy server is used to allow EPM agents installed on an isolated network to communicate with the EPM service.
This section describes how to configure the Squid proxy server and allow it access to the EPM server only.
As an example, the Squid proxy server could have the following minimum requirements:
|
Item |
Requirement |
|---|---|
|
Hardware or VM |
1 CPU core 1G RAM 10G disk |
|
Operating system |
RHEL 7 or higher |
|
Port |
TCP port 3128 open for LAN connections from EPM agents |
|
Internet |
Outbound internet on port 443 |
Install Squid by running the following commands.
On yum-based Linux (RHEL/Centos/Fedora):
|
On apt-based Linux (Ubuntu/Debian):
|
Enable, start, and check the status of Squid.
|
Configure Squid to allow access to the EPM service only.
Enable the host server and the dispatcher domains, and disable all other domains.
|
|
For the host server, specify the domain prefix for your region and the three numbers from the EPM console URL after login. For example, na123.epm.cyberark.com or jp123.epm.cyberark.com. For the dispatcher domain, specify the domain prefix for your region. For example, login.epm.cyberark.com or jp.epm.cyberark.com. |
Open the Squid configuration file using squid acl.
On a fresh Squid installation, add the following four lines to the top of /etc/squid/squid.conf. Make sure you include the http_access deny all command.
|
After you have updated squid.conf, reload the Squid service.
|
Open the Squid access log.
|
View the requests that were issued.
|
1600975689.552 119942 10.0.1.4 TCP_TUNNEL/200 4495 CONNECT login.epm.cyberark.com:443 - HIER_DIRECT/104.17.195.105 - |
In squid.conf, disable or change epm_cyberark acls, and check that requests are blocked. The following steps lead you through an example check.
Change allowed_domain_epm_cyberark 123.epm.mycompany.com to 456.epm.mycompany.com.
Reload Squid.
|
Open /var/log/squid/access.log and check that a tcp_denied string was issued.
|
1600988752.530 0 10.0.1.4 TCP_DENIED/403 3816 CONNECT 123.epm.mycompany.com:443 - HIER_NONE/- text/html |
In the EPM Management console > My Computers, your computer now appears as 'disconnected'.
Change allowed_domain_epm_cyberark 456.epm.mycompany.com back to 123.epm.mycompany.com.
Reload Squid again.
|
Test with shell to check that Google is blocked, but the EPM agent is not.
Try to access Google.
|
export HTTP_PROXY=10.0.1.5:3128 export HTTPS_PROXY=10.0.1.5:3128 curl http://google.com |
The following response should be returned.
|
HTTP/1.1 403 Forbidden Server: squid/3.5.27 |
Try to access the EPM agent.
|
curl -I https://123.epm.mycompany.com |
The following response should be returned.
|
HTTP/1.1 200 Connection established |
This KB article is provided for educational purposes only and is not actively maintained. As product features may evolve over time, configuring a Squid server should always be done using the official product documentation. For support, please consult the Squid community or your specific software vendor.