<?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 Triage process to eliminate  endpoint issues prior to Prisma Access queries in Prisma Access for MSPs and Distributed Enterprises Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-for-msps-and/triage-process-to-eliminate-endpoint-issues-prior-to-prisma/m-p/1237401#M17</link>
    <description>&lt;P&gt;Has anybody come across or developed a triaging (L1/L2) process to eliminate endpoint issues before submitting Prisma SASE (PA and Prism SDWAN) to support?. It is important for customers, provisioned with Prisma SASE to be efficient and effective before submitting ticket to MSSP. This document may be of great value to PA customers. Thank you&lt;/P&gt;</description>
    <pubDate>Fri, 05 Sep 2025 13:29:43 GMT</pubDate>
    <dc:creator>Kreshby202</dc:creator>
    <dc:date>2025-09-05T13:29:43Z</dc:date>
    <item>
      <title>Triage process to eliminate  endpoint issues prior to Prisma Access queries</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-for-msps-and/triage-process-to-eliminate-endpoint-issues-prior-to-prisma/m-p/1237401#M17</link>
      <description>&lt;P&gt;Has anybody come across or developed a triaging (L1/L2) process to eliminate endpoint issues before submitting Prisma SASE (PA and Prism SDWAN) to support?. It is important for customers, provisioned with Prisma SASE to be efficient and effective before submitting ticket to MSSP. This document may be of great value to PA customers. Thank you&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 13:29:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-for-msps-and/triage-process-to-eliminate-endpoint-issues-prior-to-prisma/m-p/1237401#M17</guid>
      <dc:creator>Kreshby202</dc:creator>
      <dc:date>2025-09-05T13:29:43Z</dc:date>
    </item>
    <item>
      <title>Re: Triage process to eliminate  endpoint issues prior to Prisma Access queries</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-for-msps-and/triage-process-to-eliminate-endpoint-issues-prior-to-prisma/m-p/1237414#M18</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/288304"&gt;@Kreshby202&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;So are you the MSSP in this case or someone paying per ticket opened with the MSSP?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I ask because that will actually change what you're actually asking for. An average end-user is not going to be that efficient at troubleshooting anything with Prisma Access before contacting support, but the MSSP should have basic tests that ideally can be ran from an RMM or EDR to validate basic connectivity and simple log parsing for issues.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 19:33:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-for-msps-and/triage-process-to-eliminate-endpoint-issues-prior-to-prisma/m-p/1237414#M18</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2025-09-05T19:33:41Z</dc:date>
    </item>
  </channel>
</rss>

