Security
Security is a big concern with many of our customers and has led some to introduce egress filtering at their firewalls. This type of filtering controls outgoing connections from the customer network to ensure that their systems can only talk to approved destinations.
We use CloudFlare for DDoS mitigation, application firewalling, and attack detection, so customers connecting to the Splunk On-Call platform are connecting to a Cloudflare proxy server. This means that customer egress filters must allow connections to all of Cloudflare’s IP ranges in addition to Splunk On-Call’s ranges. Egress IP ranges are listed at https://www.cloudflare.com/ips
Future platform enhancements on our roadmap will mean that public IP addresses for the Splunk On-Call platform will see additions, deletions, and changes over time. Therefore we have some suggestions for working with Splunk On-Call:
Awareness
Egress Strategy
Ingress Strategy
In the event you have a firewall blocking Splunk On-Call webhooks, you may allow our IP address 34.208.78.175. WARNING our IP address is subject to change.