<?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: Security of Mobile OneAgent and beacon endpoint in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Security-of-Mobile-OneAgent-and-beacon-endpoint/m-p/192229#M4749</link>
    <description>&lt;P&gt;Thank you harp.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Aug 2022 14:20:38 GMT</pubDate>
    <dc:creator>JB</dc:creator>
    <dc:date>2022-08-08T14:20:38Z</dc:date>
    <item>
      <title>Security of Mobile OneAgent and beacon endpoint</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Security-of-Mobile-OneAgent-and-beacon-endpoint/m-p/191654#M4747</link>
      <description>&lt;P&gt;Hi all,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a client that is concerned that a malicious party may decompile the mobile app and extract the application id and beacon endpoint for future attacks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found in the documentation the use of&amp;nbsp;&lt;STRONG&gt;Beacon origins for CORS&lt;/STRONG&gt;&lt;SPAN&gt;. Can you confirm if this also applied for mobile and if this should be the solution to be sure that the bea&lt;/SPAN&gt;con endpoint will only accept requests from "known" or "authenticated" clients?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Johanna.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jul 2022 20:54:19 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Security-of-Mobile-OneAgent-and-beacon-endpoint/m-p/191654#M4747</guid>
      <dc:creator>JB</dc:creator>
      <dc:date>2022-07-29T20:54:19Z</dc:date>
    </item>
    <item>
      <title>Re: Security of Mobile OneAgent and beacon endpoint</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Security-of-Mobile-OneAgent-and-beacon-endpoint/m-p/191663#M4748</link>
      <description>&lt;P&gt;For detailed security inquiries I suggest to create a support ticket. CORS only applies for browser based traffic and not for native mobile agents.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Aug 2022 05:40:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Security-of-Mobile-OneAgent-and-beacon-endpoint/m-p/191663#M4748</guid>
      <dc:creator>Patrick_H</dc:creator>
      <dc:date>2022-08-01T05:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: Security of Mobile OneAgent and beacon endpoint</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Security-of-Mobile-OneAgent-and-beacon-endpoint/m-p/192229#M4749</link>
      <description>&lt;P&gt;Thank you harp.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2022 14:20:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Security-of-Mobile-OneAgent-and-beacon-endpoint/m-p/192229#M4749</guid>
      <dc:creator>JB</dc:creator>
      <dc:date>2022-08-08T14:20:38Z</dc:date>
    </item>
  </channel>
</rss>

