<?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 Dynatrace Internal Tokens in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Internal-Tokens/m-p/202708#M24152</link>
    <description>&lt;P&gt;Dynatrace became part of the Github secret scanning program a while back and while browsing their supported patterns they make reference of "Dynatrace Internal Tokens" (&lt;A href="https://docs.github.com/en/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns" target="_blank" rel="noopener"&gt;https://docs.github.com/en/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns&lt;/A&gt;).&lt;/P&gt;
&lt;P&gt;These do not seem to be documented anywhere, at least that I could find, but since Github differentiates them from regular access tokens, I presume they follow a different format than the one documented on the Dynatrace site?&lt;BR /&gt;Surely they must be able to be exposed since rules for them exist, but I have yet to find out where these get used and how they look like, and no warning anywhere on how to guard against this.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Feb 2023 10:32:33 GMT</pubDate>
    <dc:creator>Tozya</dc:creator>
    <dc:date>2023-02-08T10:32:33Z</dc:date>
    <item>
      <title>Dynatrace Internal Tokens</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Internal-Tokens/m-p/202708#M24152</link>
      <description>&lt;P&gt;Dynatrace became part of the Github secret scanning program a while back and while browsing their supported patterns they make reference of "Dynatrace Internal Tokens" (&lt;A href="https://docs.github.com/en/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns" target="_blank" rel="noopener"&gt;https://docs.github.com/en/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns&lt;/A&gt;).&lt;/P&gt;
&lt;P&gt;These do not seem to be documented anywhere, at least that I could find, but since Github differentiates them from regular access tokens, I presume they follow a different format than the one documented on the Dynatrace site?&lt;BR /&gt;Surely they must be able to be exposed since rules for them exist, but I have yet to find out where these get used and how they look like, and no warning anywhere on how to guard against this.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2023 10:32:33 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Internal-Tokens/m-p/202708#M24152</guid>
      <dc:creator>Tozya</dc:creator>
      <dc:date>2023-02-08T10:32:33Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Internal Tokens</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Internal-Tokens/m-p/204532#M24559</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/58763"&gt;@Tozya&lt;/a&gt;&amp;nbsp;I think that the vernacular in GITHUB is different then Dynatrace Corp. Dynatrace has two Types of Tags, PaaS Tags and API Tokens.&amp;nbsp;&lt;BR /&gt;The PaaS tokens would be equivalent to&amp;nbsp;&lt;SPAN&gt;Dynatrace Access Tokens as listed in the GitHub Doc, where the API Tokens would be equivalent&amp;nbsp;to&amp;nbsp;Dynatrace Internal Tokens as listed in the GitHub Doc.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 13:19:23 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Internal-Tokens/m-p/204532#M24559</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-02-10T13:19:23Z</dc:date>
    </item>
  </channel>
</rss>

