<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Real User API Security in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171101#M3062</link>
    <description>&lt;P&gt;Hi Matthias,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks for reaching out. We do validate the RUM data. However, if someone simulates valid data it is in theory possible to send bogus/fake data. I believe there isn't much we can do about it for real user monitoring of public pages.&lt;BR /&gt;This is a problem also&amp;nbsp;&lt;A href="https://security.stackexchange.com/questions/106892/how-does-google-analytics-prevent-fake-data-attacks-against-an-entitys-traffic" target="_blank" rel="noopener"&gt;other analytics solutions face&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said, there is always the option to only allow traffic from trusted sources or block suspicious sources on the network/firewall level.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;/P&gt;
&lt;P&gt;Philipp&lt;/P&gt;</description>
    <pubDate>Tue, 24 Aug 2021 10:29:42 GMT</pubDate>
    <dc:creator>Philipp_Kastner</dc:creator>
    <dc:date>2021-08-24T10:29:42Z</dc:date>
    <item>
      <title>Real User API Security</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171056#M3059</link>
      <description>&lt;P&gt;How is the abuse of the Real User Monitoring API secured?&lt;BR /&gt;From my point of view, the RUM data could currently be quite easily contaminated by means of external requests.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2021 08:12:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171056#M3059</guid>
      <dc:creator>Matthias-Versio</dc:creator>
      <dc:date>2021-08-23T08:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: Real User API Security</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171076#M3061</link>
      <description>&lt;P&gt;Want to add some additional context as Matthias and I initially discussed this question via email and I asked him to post it here as I didnt know the answer either:&lt;/P&gt;
&lt;P&gt;"Which mechanisms exist in the Dynatrace RUM API to prevent any misusage or tampering, e.g: sending bogus data or modifying data that is collected?"&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2021 15:26:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171076#M3061</guid>
      <dc:creator>andreas_grabner</dc:creator>
      <dc:date>2021-08-23T15:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: Real User API Security</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171101#M3062</link>
      <description>&lt;P&gt;Hi Matthias,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks for reaching out. We do validate the RUM data. However, if someone simulates valid data it is in theory possible to send bogus/fake data. I believe there isn't much we can do about it for real user monitoring of public pages.&lt;BR /&gt;This is a problem also&amp;nbsp;&lt;A href="https://security.stackexchange.com/questions/106892/how-does-google-analytics-prevent-fake-data-attacks-against-an-entitys-traffic" target="_blank" rel="noopener"&gt;other analytics solutions face&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said, there is always the option to only allow traffic from trusted sources or block suspicious sources on the network/firewall level.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;/P&gt;
&lt;P&gt;Philipp&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 10:29:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171101#M3062</guid>
      <dc:creator>Philipp_Kastner</dc:creator>
      <dc:date>2021-08-24T10:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Real User API Security</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171107#M3063</link>
      <description>&lt;P&gt;Hello Phillip,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you for your timely feedback.&lt;/P&gt;&lt;P&gt;That's exactly how I thought it would be.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Matthias&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 12:02:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/171107#M3063</guid>
      <dc:creator>Matthias-Versio</dc:creator>
      <dc:date>2021-08-24T12:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: Real User API Security</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/176899#M3266</link>
      <description>&lt;P&gt;Perhaps, as also suggested in the linked page, the RUM agent could pull a hash token from the server (activegate) and pass it along. And if that hash is based on the environment ID and timestamp, this could be verified upon reception of data?&lt;/P&gt;</description>
      <pubDate>Fri, 03 Dec 2021 09:19:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Real-User-API-Security/m-p/176899#M3266</guid>
      <dc:creator>fstekelenburg</dc:creator>
      <dc:date>2021-12-03T09:19:35Z</dc:date>
    </item>
  </channel>
</rss>

