Epiphany Collector Prerequisites
Release 1.0
About This Guide
The Epiphany Intelligence Platform can leverage customer data sources based in the cloud and/or on premise. While the cloud-based data collector generally does not require additional resources, some customers require a local device to collect, encrypt, and transmit data to the platform. There are network and virtual hardware considerations, which are outlined in this document.
Version Compatibility
Epiphany Local Site Collector Version 1.x.
Hardware Requirements
Platform: VMWare or Hyper-V
RAM: 16GB (expandable to 32GB)
Cores: 2 (expandable to 4)
Storage: 55GB (minimum)
Outbound Firewall Rules/Exceptions
You must permit the following addresses within your firewall rules for the collector to communicate to the Epiphany Intelligence Platform:
fm1.epiphanysys.com:4505,4506
fm2.epiphanysys.com:4505,4506
pv1.epiphanysys.com:443
client-eip-raw.s3.amazonaws.com:443
045125109764.dkr.ecr.us-east-1.amazonaws.com:443
api.ecr.us-east-1.amazonaws.com:443
Internal Communications
For the Site Collector to communicate to your internal systems effectively you must permit the following services/ports from the site collector within your firewall:
RPC endpoint mapper: port 135 TCP, UDP
NetBIOS name service: port 137 TCP, UDP
NetBIOS datagram service: port 138 UDP
NetBIOS session service: port 139 TCP
SMB over IP (Microsoft-DS): port 445 TCP, UDP
LDAP: port 389 TCP, UDP
LDAP over SSL: port 636 TCP
Global catalog LDAP: port 3268 TCP
Global catalog LDAP over SSL: port 3269 TCP
Kerberos: port 88 TCP, UDP
DNS: port 53 TCP, UDP
WINS resolution: port 1512 TCP, UDP
WINS replication: 42 TCP, UDP
RPC: Dynamically assigned ports TCP, unless restricted.
HTTPS: port 443 TCP, UDP
HTTP: port 80 TCP, UDP
Any others as required by implementation
Last updated