<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>LogTriage Research — attack data from a real server</title>
  <link>https://logtriage.app/</link>
  <description>Monthly measurements from LogTriage's own internet-facing server: what attacks it (SSH brute force, web probes, scanners and the networks behind them) and how well free IP blocklists catch those attackers. Aggregates only, free to reuse under CC BY 4.0. Plus notes on detection engineering.</description>
  <language>en</language>
  <lastBuildDate>Sun, 08 Nov 2026 00:00:00 GMT</lastBuildDate>
  <atom:link href="https://logtriage.app/reports/rss.xml" rel="self" type="application/rss+xml"/>
  <atom:link href="https://pubsubhubbub.appspot.com/" rel="hub"/>
  <item>
    <title>What finds a new MCP server: directories, monitors and scanners</title>
    <link>https://logtriage.app/reports/mcp-scanners/</link>
    <guid isPermaLink="true">https://logtriage.app/reports/mcp-scanners/</guid>
    <description>Who called a public MCP server after its listing in the official MCP Registry, and the scanners that probed /mcp before it existed. Aggregated from our own logs, updated weekly.</description>
    <category>Reports</category>
    <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title>Which free IP blocklists stop real attacks? (2026-10)</title>
    <link>https://logtriage.app/reports/ip-blocklists/</link>
    <guid isPermaLink="true">https://logtriage.app/reports/ip-blocklists/</guid>
    <description>Free IP blocklists measured monthly against every address that attacked a real production server: coverage of attackers and attack traffic, list by list.</description>
    <category>Reports</category>
    <pubDate>Mon, 02 Nov 2026 02:40:16 GMT</pubDate>
  </item>
  <item>
    <title>What attacks an internet-facing server — 2026-10 edition</title>
    <link>https://logtriage.app/reports/server-attacks/2026-10/</link>
    <guid isPermaLink="true">https://logtriage.app/reports/server-attacks/2026-10/</guid>
    <description>Monthly data report from LogTriage's own production server: SSH brute force, web probes, attacking networks and tools, aggregated.</description>
    <category>Reports</category>
    <pubDate>Sun, 01 Nov 2026 02:10:54 GMT</pubDate>
  </item>
  <item>
    <title>What attacks an internet-facing server — 2026-09 edition</title>
    <link>https://logtriage.app/reports/server-attacks/2026-09/</link>
    <guid isPermaLink="true">https://logtriage.app/reports/server-attacks/2026-09/</guid>
    <description>Monthly data report from LogTriage's own production server: SSH brute force, web probes, attacking networks and tools, aggregated.</description>
    <category>Reports</category>
    <pubDate>Tue, 06 Oct 2026 14:53:47 GMT</pubDate>
  </item>
  <item>
    <title>Why a curl User-Agent Isn't Automatically Malicious</title>
    <link>https://logtriage.app/blog/context-aware-risk-scoring/</link>
    <guid isPermaLink="true">https://logtriage.app/blog/context-aware-risk-scoring/</guid>
    <description>Context-aware risk scoring explained: why the same user-agent string can be low risk on one endpoint and critical on another.</description>
    <category>Blog</category>
    <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title>Detecting Impossible Travel Without Expensive UEBA Tooling</title>
    <link>https://logtriage.app/blog/impossible-travel-detection/</link>
    <guid isPermaLink="true">https://logtriage.app/blog/impossible-travel-detection/</guid>
    <description>Impossible travel detection doesn't need a UEBA platform — haversine distance and elapsed time on sign-in coordinates is enough.</description>
    <category>Blog</category>
    <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title>What a Single Confirmed-Malicious Threat Intel Hit Should Do to Your Risk Score</title>
    <link>https://logtriage.app/blog/single-ti-hit-should-spike-score/</link>
    <guid isPermaLink="true">https://logtriage.app/blog/single-ti-hit-should-spike-score/</guid>
    <description>Why additive risk scoring under-reacts to a single confirmed-malicious threat intelligence verdict, and how a floor rule fixes it.</description>
    <category>Blog</category>
    <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
  </item>
</channel>
</rss>
