<?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>article Audit does not capture API activity in Workforce Identity Articles</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-articles/audit-does-not-capture-api-activity/ta-p/1427653</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;Does Audit capture activity when performed via API request?&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;Audit logs are designed to capture actions performed by human users during interactive sessions. Activities initiated by system accounts or service principals, such as creating roles through an API, are considered “non-human events.”&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By design, these events are excluded from the Audit interface because its purpose is to track user-driven activity for compliance and accountability.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While API calls do change configuration, they will not appear in the Audit interface since they are not tied to a human user session. These actions may be recorded in other operational or diagnostic logs, but they are not published to the Audit feed.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Dec 2025 16:13:46 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-12-29T16:13:46Z</dc:date>
    <item>
      <title>Audit does not capture API activity</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-articles/audit-does-not-capture-api-activity/ta-p/1427653</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;Does Audit capture activity when performed via API request?&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;Audit logs are designed to capture actions performed by human users during interactive sessions. Activities initiated by system accounts or service principals, such as creating roles through an API, are considered “non-human events.”&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By design, these events are excluded from the Audit interface because its purpose is to track user-driven activity for compliance and accountability.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While API calls do change configuration, they will not appear in the Audit interface since they are not tied to a human user session. These actions may be recorded in other operational or diagnostic logs, but they are not published to the Audit feed.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Dec 2025 16:13:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-articles/audit-does-not-capture-api-activity/ta-p/1427653</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-12-29T16:13:46Z</dc:date>
    </item>
  </channel>
</rss>

