<?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 Logging and Change Management in Prisma Cloud in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571468#M115062</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Summary:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;There is currently a size limit of 128kb in compute console history logs&lt;/SPAN&gt;&lt;SPAN&gt;. &lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;It's likely to hit this limit and then only an error will display in the changes section: "diff size exceeded limit (128KB)". &lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;&lt;STRONG&gt;This makes the history log useless for auditing a specific endpoint&lt;/STRONG&gt;, as experienced by multiple&amp;nbsp;users.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are there ways to overcome this issue in the short and long term? Consider upvoting the idea linked below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hoping to get this issue to the relevant teams as logging is essential for Prisma Cloud configuration and change management monitoring. Can we please have this idea reviewed by the appropriate team?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Idea source:&amp;nbsp;&lt;A href="https://prismacloud.ideas.aha.io/ideas/PANW-I-4799" target="_blank"&gt;Fix Manage&amp;gt;Logs&amp;gt;History | Prisma Cloud New Features Request Portal (aha.io)&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jan 2024 16:16:52 GMT</pubDate>
    <dc:creator>patriciar</dc:creator>
    <dc:date>2024-01-02T16:16:52Z</dc:date>
    <item>
      <title>Logging and Change Management in Prisma Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571468#M115062</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Summary:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;There is currently a size limit of 128kb in compute console history logs&lt;/SPAN&gt;&lt;SPAN&gt;. &lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;It's likely to hit this limit and then only an error will display in the changes section: "diff size exceeded limit (128KB)". &lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;&lt;STRONG&gt;This makes the history log useless for auditing a specific endpoint&lt;/STRONG&gt;, as experienced by multiple&amp;nbsp;users.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are there ways to overcome this issue in the short and long term? Consider upvoting the idea linked below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hoping to get this issue to the relevant teams as logging is essential for Prisma Cloud configuration and change management monitoring. Can we please have this idea reviewed by the appropriate team?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Idea source:&amp;nbsp;&lt;A href="https://prismacloud.ideas.aha.io/ideas/PANW-I-4799" target="_blank"&gt;Fix Manage&amp;gt;Logs&amp;gt;History | Prisma Cloud New Features Request Portal (aha.io)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jan 2024 16:16:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571468#M115062</guid>
      <dc:creator>patriciar</dc:creator>
      <dc:date>2024-01-02T16:16:52Z</dc:date>
    </item>
    <item>
      <title>Re: Logging and Change Management in Prisma Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571479#M115063</link>
      <description>&lt;P&gt;What is this related to as a function of Prisma?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jan 2024 19:20:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571479#M115063</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2024-01-02T19:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: Logging and Change Management in Prisma Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571492#M115066</link>
      <description>&lt;P&gt;Hi Brandon - I'm looking at the audit logs available in Prisma Cloud Compute, under Manage -&amp;gt; View Logs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As per documentation goes,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Administrative activity audit trail&lt;/P&gt;
&lt;P&gt;All Prisma Cloud administrative activities are logged.&lt;/P&gt;
&lt;P&gt;Changes to any settings (including previous and new values), changes to any rules (create, modify, or delete), changes to the credentials (create,modify, or delete), and all logon activity (success and failure) are logged. For every event, both the user name and source IP are captured."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many of the log entries exceed the limit 128KB, which results in a log entry stating that fact. Do you know of a way to make these logs clearer?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;P&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jan 2024 22:43:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571492#M115066</guid>
      <dc:creator>patriciar</dc:creator>
      <dc:date>2024-01-02T22:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: Logging and Change Management in Prisma Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571604#M115082</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/309452"&gt;@patriciar&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Hi Brandon - I'm looking at the audit logs available in Prisma Cloud Compute, under Manage -&amp;gt; View Logs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As per documentation goes,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Administrative activity audit trail&lt;/P&gt;
&lt;P&gt;All Prisma Cloud administrative activities are logged.&lt;/P&gt;
&lt;P&gt;Changes to any settings (including previous and new values), changes to any rules (create, modify, or delete), changes to the credentials (create,modify, or delete), and all logon activity (success and failure) are logged. For every event, both the user name and source IP are captured."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many of the log entries exceed the limit 128KB, which results in a log entry stating that fact. Do you know of a way to make these logs clearer?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;P&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Oh ok...My company doesn't use Prisma Cloud so I can't speak to running into this issue, but if there's a config audit limit and it's not even 1MB that seems really small.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jan 2024 14:12:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/logging-and-change-management-in-prisma-cloud/m-p/571604#M115082</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2024-01-03T14:12:41Z</dc:date>
    </item>
  </channel>
</rss>

