<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Community-Id on Joshua's Notebook</title><link>https://burnett.sh/tags/community-id/</link><description>Recent content in Community-Id on Joshua's Notebook</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 16 Jun 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://burnett.sh/tags/community-id/index.xml" rel="self" type="application/rss+xml"/><item><title>HoneyPi Part 5: Combining the Streams on the Mac</title><link>https://burnett.sh/posts/honeypi-enrich-mac/</link><pubDate>Tue, 16 Jun 2026 09:00:00 -0500</pubDate><guid>https://burnett.sh/posts/honeypi-enrich-mac/</guid><description>&lt;p&gt;In the &lt;a href="https://burnett.sh/posts/honeypi-enrich-pi/"&gt;previous post&lt;/a&gt; I got two of the three streams live on the Pi: Cowrie and Suricata, both shipping to Loki through Alloy with a shared &lt;code&gt;src_ip&lt;/code&gt; key. This post covers the Mac side, which is where the third stream comes in and where the whole correlation idea stops being a diagram and starts being something you can actually query. By the end of it, one attacker IP lights up across all three tools at once, and any single network flow can be matched between Suricata and Zeek deterministically rather than by eyeballing timestamps.&lt;/p&gt;</description></item></channel></rss>