Required ports and endpoints
The RocketCyber Agent communicates to the RocketCyber Cloud via the following destinations.
If the network environment limits access to the internet, please allow the following destinations and ports via firewalls or proxies for proper agent functionality.
For RocketCyber US Instance
Description | PORT | Hostname |
---|---|---|
Main agent endpoint |
443/SSL |
app.rocketcyber.com |
S3 - Agent Binary Downloads |
443/SSL |
s3.amazonaws.com |
Agent WebSocket |
443/SSL |
ws.app.rocketcyber.com |
Threat Lookup Service |
443/SSL |
tls-us.rocketcyber.com |
Device Heartbeat Service |
443/SSL |
dhs.us.rocketcyber.com |
Agent App Results |
443/SSL |
agent.us.rocketcyber.com |
Agent Installation |
443/SSL |
*.digicert.com |
IoC App, Ransomware Detection |
443/SSL |
content.rocketcyber.com |
For RocketCyber EU Instance
Description | PORT | Hostname |
---|---|---|
Main agent endpoint |
443/SSL |
eu.rocketcyber.com |
S3 - Agent Binary Downloads |
443/SSL |
s3.amazonaws.com s3.eu-west-1.amazonaws.com |
Agent WebSocket |
443/SSL |
ws.eu.rocketcyber.com |
Threat Lookup Service |
443/SSL |
tls-eu.rocketcyber.com |
Device Heartbeat Service |
443/SSL |
dhs.eu.rocketcyber.com |
Agent App Results |
443/SSL |
agent.eu.rocketcyber.com |
Agent Installation |
443/SSL |
*.digicert.com |
IoC App, Ransomware Detection | 443/SSL |
content.rocketcyber.com |
NOTE RocketCyber does not currently maintain static IPs for whitelisting. All whitelisting must be performed by hostname and port.