{"id":80322,"date":"2023-06-05T13:09:57","date_gmt":"2023-06-05T17:09:57","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=80322"},"modified":"2024-06-11T14:18:16","modified_gmt":"2024-06-11T18:18:16","slug":"agent-networking-and-port-requirements","status":"publish","type":"support","link":"https:\/\/jumpcloud.com\/support\/agent-networking-and-port-requirements","title":{"rendered":"JumpCloud Agent Networking and Port Requirements"},"content":{"rendered":"\n
The agent does not listen on any port for traffic initiated external to the localhost, thus does not increase potential attack vectors. However, as outbound connections are made, any egress filtering performed by Antivirus software, firewalls, routers, etc.. would need to be opened. No inbound TCP connections need to be explicitly defined.<\/p>\n\n\n\n
Environments using DNS proxies, or other mechanisms that may cache JumpCloud IP addresses may pin themselves to a single server. For larger environments, this could result in rate limiting which will disrupt installations and functionality. Caching JumpCloud IPs is not recommended.<\/p>\n\n\n\n