So according to this page: https://docs.splunk.com/Documentation/SplunkCloud/9.0.2303/Data/UsetheHTTPEventCollector?ref=hk&_ga=2.72855443.1448184042.1688033344-2100016873.1685462082&_gac=1.226256360.1685462108.CjwKCAjwvdajBhBEEiwAeMh1U20mvHGc8u_1xWRevnEqtIe1jRTqZV8YufwHzF2XLG--EZcojVnuwhoC-XIQAvD_BwE&_gl=1*zxhtvo*_ga*MjEwMDAxNjg3My4xNjg1NDYyMDgy*_ga_5EPM2P39FV*MTY4ODAzMzM0My4xMS4wLjE2ODgwMzMzNDMuNjAuMC4w#Send_data_to_HTTP_Event_Collector Port 8088 is only for trial accounts. Full accounts should use port 443 in their command. Hope this helps! ... View more

For @muradgh and anyone else struggling with this, I've managed to get it working. The BitDefender guide is out of date/incorrect about the Splunk address to use. I found the correct format on this page: https://docs.splunk.com/Documentation/SplunkCloud/9.0.2303/Data/UsetheHTTPEventCollector?ref=hk#Send_data_to_HTTP_Event_Collector Long story short, you need to add http-inputs- before your URL and use port 443, not 8088 as BD say. So my full URL (with hostname removed, obviously) is: https://http-inputs-[hostname].splunkcloud.com:443/services/collector  After doing that, I now get the success return value that the BD guide shows. Hope this helps other people! ... View more