<?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: E token Cortex XDR blocking in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/e-token-cortex-xdr-blocking/m-p/1250557#M9202</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1520317151"&gt;@MEERSHAH&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3 data-section-id="7yz5e" data-start="139" data-end="197"&gt;&lt;FONT face="terminal,monaco"&gt;&lt;SPAN&gt;&lt;STRONG data-start="143" data-end="197"&gt;Allowing E-Tokens Blocked as CD-ROMs in Cortex XDR&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P style="margin: 0px;" data-start="199" data-end="529"&gt;&lt;SPAN&gt;To allow E-Tokens that are being blocked under the CD-ROM category in Cortex XDR, create a &lt;STRONG data-start="290" data-end="318"&gt;Device Control exception&lt;/STRONG&gt; based on the device’s &lt;STRONG data-start="341" data-end="360"&gt;Vendor ID (VID)&lt;/STRONG&gt; and &lt;STRONG data-start="365" data-end="385"&gt;Product ID (PID)&lt;/STRONG&gt;. Configure this in the &lt;STRONG data-start="409" data-end="442"&gt;Cortex XDR Management Console&lt;/STRONG&gt; under &lt;STRONG data-start="449" data-end="476"&gt;Policy &amp;gt; &lt;SPAN class="frame-title"&gt;Device Exceptions&lt;/SPAN&gt;&lt;/STRONG&gt;&amp;nbsp;by adding a rule to exempt the specific token IDs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 data-section-id="6wahh2" data-start="536" data-end="566"&gt;&lt;FONT face="terminal,monaco"&gt;&lt;SPAN&gt;&lt;STRONG data-start="540" data-end="566"&gt;Steps to Allow E-Token&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P style="margin: 0px;" data-start="571" data-end="593"&gt;&lt;SPAN&gt;&lt;STRONG data-start="571" data-end="593"&gt;1. Identify the Token&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="599" data-end="724"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="599" data-end="724"&gt;&lt;SPAN&gt;- Plug in the E-Token and find its &lt;STRONG data-start="632" data-end="643"&gt;VID/PID&lt;/STRONG&gt; from the blocked alert logs in Cortex XDR or via Device Manager on the endpoint.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="729" data-end="753"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="729" data-end="753"&gt;&lt;SPAN&gt;&lt;STRONG data-start="729" data-end="753"&gt;2. Navigate to Policies&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="759" data-end="826"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="759" data-end="826"&gt;&lt;SPAN&gt;- In the Cortex XDR Console, go to:&lt;/SPAN&gt;&lt;BR data-start="792" data-end="795" /&gt;&lt;SPAN&gt;&lt;CODE data-start="800" data-end="825"&gt;- Extensions Policy → Profile -&amp;gt; Create &lt;STRONG data-end="476" data-start="449"&gt;&lt;SPAN class="frame-title"&gt;Device Exceptions&lt;/SPAN&gt;&lt;/STRONG&gt;&amp;nbsp;&lt;/CODE&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="831" data-end="851"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="831" data-end="851"&gt;&lt;SPAN&gt;&lt;STRONG data-start="831" data-end="851"&gt;3. Create Exception&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="857" data-end="935"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="857" data-end="935"&gt;&lt;SPAN&gt;- Add a new rule to &lt;STRONG data-start="875" data-end="884"&gt;Allow&lt;/STRONG&gt; the specific device using its Vendor/Product ID.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="941" data-end="1031"&gt;&lt;SPAN&gt;- Set the permission to &lt;STRONG data-start="963" data-end="977"&gt;Read/Write&lt;/STRONG&gt; or &lt;STRONG data-start="981" data-end="990"&gt;Allow&lt;/STRONG&gt; to ensure the token functions correctly.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1036" data-end="1053"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1036" data-end="1053"&gt;&lt;SPAN&gt;&lt;STRONG data-start="1036" data-end="1053"&gt;4. Assign Policy&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1059" data-end="1173"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1059" data-end="1173"&gt;&lt;SPAN&gt;- Apply the updated policy to the relevant endpoint groups (e.g., specific departments or branches using the token).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1059" data-end="1173"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1180" data-end="1389"&gt;&lt;SPAN&gt;&lt;STRONG data-start="1180" data-end="1189"&gt;Note:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1180" data-end="1389"&gt;&lt;BR data-start="1189" data-end="1192" /&gt;&lt;SPAN&gt;If the token is being blocked by a &lt;STRONG data-start="1227" data-end="1251"&gt;Malware/BIOC profile&lt;/STRONG&gt; rather than Device Control, you may also need to add the &lt;STRONG data-start="1309" data-end="1341"&gt;signer of the token software&lt;/STRONG&gt; to the allow list within the malware profile.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1180" data-end="1389"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please help out other users and “Accept as Solution” if a post helps solve your problem !&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;A href="https://live.paloaltonetworks.com/t5/blogs/how-and-why-to-accept-solutions/ba-p/553827" target="_blank"&gt;Read more about how and why to accept solutions.&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Mar 2026 12:18:33 GMT</pubDate>
    <dc:creator>Vinothkumar_SBA</dc:creator>
    <dc:date>2026-03-19T12:18:33Z</dc:date>
    <item>
      <title>E token Cortex XDR blocking</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/e-token-cortex-xdr-blocking/m-p/1250418#M9196</link>
      <description>&lt;P&gt;In our Organization E-Token is widely used by different departments/branches for specified purpose .However our cortex XDR is blocking the same under CD ROM category . How to allow the same and where to allow.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2026 05:27:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/e-token-cortex-xdr-blocking/m-p/1250418#M9196</guid>
      <dc:creator>MEERSHAH</dc:creator>
      <dc:date>2026-03-18T05:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: E token Cortex XDR blocking</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/e-token-cortex-xdr-blocking/m-p/1250557#M9202</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1520317151"&gt;@MEERSHAH&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3 data-section-id="7yz5e" data-start="139" data-end="197"&gt;&lt;FONT face="terminal,monaco"&gt;&lt;SPAN&gt;&lt;STRONG data-start="143" data-end="197"&gt;Allowing E-Tokens Blocked as CD-ROMs in Cortex XDR&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P style="margin: 0px;" data-start="199" data-end="529"&gt;&lt;SPAN&gt;To allow E-Tokens that are being blocked under the CD-ROM category in Cortex XDR, create a &lt;STRONG data-start="290" data-end="318"&gt;Device Control exception&lt;/STRONG&gt; based on the device’s &lt;STRONG data-start="341" data-end="360"&gt;Vendor ID (VID)&lt;/STRONG&gt; and &lt;STRONG data-start="365" data-end="385"&gt;Product ID (PID)&lt;/STRONG&gt;. Configure this in the &lt;STRONG data-start="409" data-end="442"&gt;Cortex XDR Management Console&lt;/STRONG&gt; under &lt;STRONG data-start="449" data-end="476"&gt;Policy &amp;gt; &lt;SPAN class="frame-title"&gt;Device Exceptions&lt;/SPAN&gt;&lt;/STRONG&gt;&amp;nbsp;by adding a rule to exempt the specific token IDs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 data-section-id="6wahh2" data-start="536" data-end="566"&gt;&lt;FONT face="terminal,monaco"&gt;&lt;SPAN&gt;&lt;STRONG data-start="540" data-end="566"&gt;Steps to Allow E-Token&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P style="margin: 0px;" data-start="571" data-end="593"&gt;&lt;SPAN&gt;&lt;STRONG data-start="571" data-end="593"&gt;1. Identify the Token&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="599" data-end="724"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="599" data-end="724"&gt;&lt;SPAN&gt;- Plug in the E-Token and find its &lt;STRONG data-start="632" data-end="643"&gt;VID/PID&lt;/STRONG&gt; from the blocked alert logs in Cortex XDR or via Device Manager on the endpoint.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="729" data-end="753"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="729" data-end="753"&gt;&lt;SPAN&gt;&lt;STRONG data-start="729" data-end="753"&gt;2. Navigate to Policies&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="759" data-end="826"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="759" data-end="826"&gt;&lt;SPAN&gt;- In the Cortex XDR Console, go to:&lt;/SPAN&gt;&lt;BR data-start="792" data-end="795" /&gt;&lt;SPAN&gt;&lt;CODE data-start="800" data-end="825"&gt;- Extensions Policy → Profile -&amp;gt; Create &lt;STRONG data-end="476" data-start="449"&gt;&lt;SPAN class="frame-title"&gt;Device Exceptions&lt;/SPAN&gt;&lt;/STRONG&gt;&amp;nbsp;&lt;/CODE&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="831" data-end="851"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="831" data-end="851"&gt;&lt;SPAN&gt;&lt;STRONG data-start="831" data-end="851"&gt;3. Create Exception&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="857" data-end="935"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="857" data-end="935"&gt;&lt;SPAN&gt;- Add a new rule to &lt;STRONG data-start="875" data-end="884"&gt;Allow&lt;/STRONG&gt; the specific device using its Vendor/Product ID.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="941" data-end="1031"&gt;&lt;SPAN&gt;- Set the permission to &lt;STRONG data-start="963" data-end="977"&gt;Read/Write&lt;/STRONG&gt; or &lt;STRONG data-start="981" data-end="990"&gt;Allow&lt;/STRONG&gt; to ensure the token functions correctly.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1036" data-end="1053"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1036" data-end="1053"&gt;&lt;SPAN&gt;&lt;STRONG data-start="1036" data-end="1053"&gt;4. Assign Policy&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1059" data-end="1173"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1059" data-end="1173"&gt;&lt;SPAN&gt;- Apply the updated policy to the relevant endpoint groups (e.g., specific departments or branches using the token).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1059" data-end="1173"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1180" data-end="1389"&gt;&lt;SPAN&gt;&lt;STRONG data-start="1180" data-end="1189"&gt;Note:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1180" data-end="1389"&gt;&lt;BR data-start="1189" data-end="1192" /&gt;&lt;SPAN&gt;If the token is being blocked by a &lt;STRONG data-start="1227" data-end="1251"&gt;Malware/BIOC profile&lt;/STRONG&gt; rather than Device Control, you may also need to add the &lt;STRONG data-start="1309" data-end="1341"&gt;signer of the token software&lt;/STRONG&gt; to the allow list within the malware profile.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px;" data-start="1180" data-end="1389"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please help out other users and “Accept as Solution” if a post helps solve your problem !&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;A href="https://live.paloaltonetworks.com/t5/blogs/how-and-why-to-accept-solutions/ba-p/553827" target="_blank"&gt;Read more about how and why to accept solutions.&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 12:18:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/e-token-cortex-xdr-blocking/m-p/1250557#M9202</guid>
      <dc:creator>Vinothkumar_SBA</dc:creator>
      <dc:date>2026-03-19T12:18:33Z</dc:date>
    </item>
  </channel>
</rss>

