<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fingerprinting on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/fingerprinting/</link>
    <description>Recent content in Fingerprinting on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 03 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/fingerprinting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted TLS Fingerprinting for Network Security: JA3/JA4 vs Zeek SSL vs Suricata TLS Analysis</title>
      <link>https://www.pistack.xyz/posts/2026-06-03-self-hosted-tls-fingerprinting-ja3-ja4-zeek-suricata-guide/</link>
      <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-03-self-hosted-tls-fingerprinting-ja3-ja4-zeek-suricata-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;TLS fingerprinting is a passive network monitoring technique that identifies client applications and malware by analyzing the unique characteristics of their TLS handshakes. Every TLS client — whether it is Chrome, a Python script, or a malware command-and-control beacon — produces a distinctive fingerprint based on its supported cipher suites, TLS extensions, elliptic curves, and signature algorithms. By capturing and analyzing these fingerprints, security teams can detect unauthorized applications, identify malware families, and enforce network policy without decrypting traffic.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
