<?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 Events forwarding to PTA in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/events-forwarding-to-pta/m-p/1422044#M88819</link>
    <description>&lt;P&gt;Can we forward AWS / Azure events to PTA via splunk , and what is best practice ?  And which AWS and Azure events we should forward to PTA  ?&lt;/P&gt;</description>
    <pubDate>Mon, 17 Mar 2025 13:18:07 GMT</pubDate>
    <dc:creator>pradeep07</dc:creator>
    <dc:date>2025-03-17T13:18:07Z</dc:date>
    <item>
      <title>Events forwarding to PTA</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/events-forwarding-to-pta/m-p/1422044#M88819</link>
      <description>&lt;P&gt;Can we forward AWS / Azure events to PTA via splunk , and what is best practice ?  And which AWS and Azure events we should forward to PTA  ?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 13:18:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/events-forwarding-to-pta/m-p/1422044#M88819</guid>
      <dc:creator>pradeep07</dc:creator>
      <dc:date>2025-03-17T13:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: Events forwarding to PTA</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/events-forwarding-to-pta/m-p/1422045#M88820</link>
      <description>&lt;P&gt;It does appear that you could configure alerts to funnel through Splunk in this manner, but in my opinion your results would be limited. For example, routing the AWS and Azure events through Splunk would limit the integration to the events supported by the Splunk forwarder in general. It looks like Splunk would generally be sending Windows Events with the following codes: "REGEX = .*EventCode=4624|4720|4723|4724|4732.*"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What this tells me is that you might be looking at a lot of effort to do a transformation of that data (between AWS/Azure and Splunk) on your own to ensure the AWS and Azure events match up with what is supported between Splunk and PTA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If we review the existing integrations for AWS and Azure, they both come with a bit of infrastructure built-in to perform this transformation for you (with Lambda scripts or Function Apps), meaning you don't have to reinvent the wheel if you go with the native integrations instead of routing through Splunk.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Azure config (CyberArk Docs): https://docs.cyberark.com/pam-self-hosted/13.2/en/content/pta/configuring-azure-forward-syslog-messages.htm?TocPath=Administrator%7CComponents%7CPrivileged%20Threat%20Analytics%7CConfigure%20Privileged%20Threat%20Analytics%7CForward%20Log%20Data%20to%20PTA%7C_____10&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AWS config (CyberArk Docs): https://docs.cyberark.com/pam-self-hosted/13.2/en/content/pta/configuring-aws-forward-syslog-messages.htm?tocpath=Administrator%7CComponents%7CPrivileged%20Threat%20Analytics%7CConfigure%20Privileged%20Threat%20Analytics%7CForward%20Log%20Data%20to%20PTA%7C_____9&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Splunk config (CyberArk Docs): https://docs.cyberark.com/pam-self-hosted/13.2/en/content/pta/configuring-splunk-forward-syslog-messages.htm?tocpath=Administrator%7CComponents%7CPrivileged%20Threat%20Analytics%7CConfigure%20Privileged%20Threat%20Analytics%7CForward%20Log%20Data%20to%20PTA%7C_____3&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 15:18:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/events-forwarding-to-pta/m-p/1422045#M88820</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-03-17T15:18:54Z</dc:date>
    </item>
  </channel>
</rss>

