<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Credential-Dumping on Linux Security</title><link>https://linuxtransfer.com/tags/credential-dumping/</link><description>Recent content in Credential-Dumping on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 02 Nov 2026 10:39:48 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/credential-dumping/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Sysmon Event ID 1 Patterns to Spot Silent Credential Dumping in Windows 10 Workstations</title><link>https://linuxtransfer.com/post/2026-11-02-using-sysmon-event-id-1-patterns-to-spot-sile/</link><pubDate>Mon, 02 Nov 2026 10:39:48 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-11-02-using-sysmon-event-id-1-patterns-to-spot-sile/</guid><description>&lt;h2 id="spotting-silent-credential-dumping-on-windows-10-workstations-with-sysmon-eventid1">Spotting Silent Credential Dumping on Windows 10 Workstations with Sysmon Event ID 1&lt;/h2>
&lt;h3 id="why-a-linuxcentric-blog-cares-about-windows-sysmon">Why a Linux‑centric blog cares about Windows Sysmon&lt;/h3>
&lt;p>Mixed‑platform environments are the norm now. A Windows 10 workstation behind the same perimeter firewall, on the same Active Directory domain, can be the entry point for a lateral attack that eventually hits your Linux servers. Detecting credential dumping early on Windows is not a luxury; it’s a practical part of a sysadmin’s defensive toolbox. Sysmon, a lightweight Microsoft Sysinternals agent, writes detailed process‑creation events to the Windows event log. Event ID 1 (“Process creation”) is the most common entry and, when filtered correctly, can expose the classic “silent” credential‑dumping techniques that slip past traditional AV.&lt;/p></description></item></channel></rss>