<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Auditd - Tag - vo.rs</title><link>https://vo.rs/tags/auditd/</link><description>Auditd - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Fri, 03 Oct 2025 11:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/auditd/" rel="self" type="application/rss+xml"/><item><title>Linux Audit Framework: Tracking Who Did What on Your Servers</title><link>https://vo.rs/story/linux-audit-framework-tracking-who-did-what-on-your-servers/</link><description>&lt;p&gt;The moment a server does something you didn&amp;rsquo;t expect — a file changes, a binary
appears, a user gains a privilege they shouldn&amp;rsquo;t have — the first question is
always the same: &lt;em&gt;who did this, and when?&lt;/em&gt; Ordinary logs rarely answer it. They
tell you a service restarted, not that someone read &lt;code&gt;/etc/shadow&lt;/code&gt; at 02:14. For
the real answer you need the Linux Audit Framework, the kernel-level recorder
that has been sitting on your box this whole time, almost certainly underused.&lt;/p&gt;</description><pubDate>Fri, 03 Oct 2025 11:00:00 +0000</pubDate></item></channel></rss>