https://community.splunk.com/t5/Security/Disable-automatic-and-undesired-traffic-to-beam-scs-splunk-com/m-p/692058#M17950 <P>I did install adguard (DNS blocker) and sees that&nbsp;<SPAN>beam.scs.splunk.com is one of the default blocked sites.</SPAN></P> Mon, 01 Jul 2024 06:40:05 GMT jotne 2024-07-01T06:40:05Z https://community.splunk.com/t5/Security/Disable-automatic-and-undesired-traffic-to-beam-scs-splunk-com/m-p/691940#M17946 <P>We deployed our first Splunk in AWS using the tooling in AWS to do this and see that there is unallowed traffic calling out from our Splunk to&nbsp;beam.scs.splunk.com, which I see is for Splunk Cloud Edge processor, which we have no intention to use.&nbsp; We would like to disable this traffic but there is no documentation on it.&nbsp; Can this be done?</P> Fri, 28 Jun 2024 13:25:39 GMT https://community.splunk.com/t5/Security/Disable-automatic-and-undesired-traffic-to-beam-scs-splunk-com/m-p/691940#M17946 woodcock 2024-06-28T13:25:39Z https://community.splunk.com/t5/Security/Disable-automatic-and-undesired-traffic-to-beam-scs-splunk-com/m-p/692058#M17950 <P>I did install adguard (DNS blocker) and sees that&nbsp;<SPAN>beam.scs.splunk.com is one of the default blocked sites.</SPAN></P> Mon, 01 Jul 2024 06:40:05 GMT https://community.splunk.com/t5/Security/Disable-automatic-and-undesired-traffic-to-beam-scs-splunk-com/m-p/692058#M17950 jotne 2024-07-01T06:40:05Z