<?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: Identifying Client Auth Cert Usage in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/identifying-client-auth-cert-usage/m-p/1420102#M703</link>
    <description>&lt;OL&gt;&lt;LI&gt;Use Venafi TLS Protect Cloud or TPP Discovery Work&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI&gt;Configure&amp;nbsp;Discovery Work&amp;nbsp;to scan for certificates across your environment.&lt;/LI&gt;&lt;LI&gt;Ensure templates used for issuance include the&amp;nbsp;Client Authentication extension, which is critical for identifying client auth certs&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Discovery can be scheduled or triggered manually, and supports both agentless and agent-based scanning&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;Filter by Certificate Extensions&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;During inventory review, filter certificates by their&amp;nbsp;Extended Key Usage (EKU)&amp;nbsp;to isolate those with&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Client Authentication&lt;UL&gt;&lt;LI&gt;&amp;nbsp;enabled.&lt;/LI&gt;&lt;LI&gt;This is typically visible in the certificate metadata pulled during scans&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;Use Application Groups for Contextual Mapping&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI&gt;Group certificates based on their application context (e.g., service accounts, user endpoints).&lt;/LI&gt;&lt;LI&gt;This helps distinguish between client auth certs used for&amp;nbsp;machine-to-machine&amp;nbsp;vs&amp;nbsp;user-to-service&amp;nbsp;authentication&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 14 Aug 2025 09:00:39 GMT</pubDate>
    <dc:creator>RobertS_Cyberark</dc:creator>
    <dc:date>2025-08-14T09:00:39Z</dc:date>
    <item>
      <title>Identifying Client Auth Cert Usage</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/identifying-client-auth-cert-usage/m-p/1420101#M702</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have tips on using Venafi to identify client auth cert usage? &lt;/P&gt;&lt;P&gt;I feel like this would come after installation and at point of connection. So Venafi might not be the tool for this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wanting to ensure we have as much visibility on who will be impacted by the stripping of server/client auth key usage from public certs in September. &lt;/P&gt;&lt;P&gt;https://www.ssl.com/blogs/removal-of-the-client-authentication-eku-from-tls-server-certificates-what-you-need-to-know/&lt;/P&gt;</description>
      <pubDate>Wed, 06 Aug 2025 22:07:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/identifying-client-auth-cert-usage/m-p/1420101#M702</guid>
      <dc:creator>Aaron_Goldblatt</dc:creator>
      <dc:date>2025-08-06T22:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying Client Auth Cert Usage</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/identifying-client-auth-cert-usage/m-p/1420102#M703</link>
      <description>&lt;OL&gt;&lt;LI&gt;Use Venafi TLS Protect Cloud or TPP Discovery Work&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI&gt;Configure&amp;nbsp;Discovery Work&amp;nbsp;to scan for certificates across your environment.&lt;/LI&gt;&lt;LI&gt;Ensure templates used for issuance include the&amp;nbsp;Client Authentication extension, which is critical for identifying client auth certs&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Discovery can be scheduled or triggered manually, and supports both agentless and agent-based scanning&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;Filter by Certificate Extensions&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;During inventory review, filter certificates by their&amp;nbsp;Extended Key Usage (EKU)&amp;nbsp;to isolate those with&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Client Authentication&lt;UL&gt;&lt;LI&gt;&amp;nbsp;enabled.&lt;/LI&gt;&lt;LI&gt;This is typically visible in the certificate metadata pulled during scans&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;Use Application Groups for Contextual Mapping&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI&gt;Group certificates based on their application context (e.g., service accounts, user endpoints).&lt;/LI&gt;&lt;LI&gt;This helps distinguish between client auth certs used for&amp;nbsp;machine-to-machine&amp;nbsp;vs&amp;nbsp;user-to-service&amp;nbsp;authentication&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Aug 2025 09:00:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/identifying-client-auth-cert-usage/m-p/1420102#M703</guid>
      <dc:creator>RobertS_Cyberark</dc:creator>
      <dc:date>2025-08-14T09:00:39Z</dc:date>
    </item>
  </channel>
</rss>

