Pulse Sensor installation

Connect device to your network

In order to function properly, please be sure your device is physically connected to your network.

• Select a secure location for the device.
• Connect an ethernet cable to Port 2 on the device, and connect to your local network.
• Connect the power cable to the device and plug it in. Please power the device via battery backup or surge protector.

Setup your Pulse Sensor with a static IP address

There are several ways to set this up, depending on your network infrastructure.

Choose one of the following:

• Preferred: Assign the IP address from your DHCP server using the MAC address on the Pulse Sensor. (Use the “MAC 2” address shown on the sticker on the sensor device.)

• Alternate: Set a static IP address on the Pulse Sensor directly.

1. Disconnect the computer from any other wired networks and turn off wifi (if it was on to begin with)
2. Make sure the computer is set for DHCP (automatic) network configuration.
3. Directly connect an ethernet cable between the computer and PORT 1 (NOT the same port as in the previous instructions)
4. Open a browser tab and enter the following IP address:  172.29.11.1
5. You should see a menu of options.  Select “Configure Static IP”
6. You should now have the option to set IP Address, Subnet Mask, and Gateway.  Set those as needed based on your local network.
7. Select Set Static IP.
8. Select Reboot.
9. The process is complete.  You can return your computer to its normal configuration and finish installing the Pulse Sensor.

Forward your firewall traffic logs to your sensor

Traffic logs are the logs containing the source and destination ports and IP addresses of traffic passing through the firewall.  

• Use the IP address assigned to the sensor in step 2 for the remote log server IP setting.
• Configure the firewall to send traffic logs to the sensor over UDP port 514.
  

Configure your firewall to support your device

NOTE: This step is only needed if your firewall is configured to restrict outbound access.

• The following ports must be opened for outbound traffic between the sensor and SecurityMetrics:
  • TCP: 80, 443, 3219, 8457, 8932, 9093, 62513
  • UDP: 10490-10500
• Your firewall must allow the device to connect to SecurityMetrics IP addresses.  There are two methods to accomplish this and both are shown below, however, only one is necessary.

Preferred:  Enable the fully qualified domain name (FQDN) *.securitymetrics.com and *.api.sm-pulse.com

NOTE: The above address & port configuration may need to be updated from time-to-time.

Alternate:  Enable the following IP addresses (and ranges):

• 204.238.82.53 TCP Ports 80, 443,3219, 8457, 8932, 9093,62513
• 204.238.82.50  TCP Port 443
• 204.238.82.52  TCP Port 443
• 76.8.204.12 TCP Port 443
• 45.60.241.32:443
• 162.211.152.0/24  UDP 10490 - 10500
• Syslog Pipeline: We use Route 53 - US-West Region 2 - Full IP list is found here - Route 53 is dynamic, you may need to setup a configuration rule to pull from the official AWS list of IP ranges. The JSON file can be found here https://ip-ranges.amazonaws.com/ip-ranges.json

NOTE: The above address & port configuration may need to be updated from time-to-time.

Verify everything is working properly

• Go to https://www.securitymetrics.com/login and sign in using the primary admin email and password.
• Select “Pulse” from the menu in the upper left corner.  
• In the Dashboard screen, find your device in the list and verify that the Status & SM Link both say “Online"

801.995.6804 | pulse@securitymetrics.com

7am-5pm MST | Monday - Friday