<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Audit Logs on Nalar</title>
    <link>https://nalar.dev/tags/audit-logs/</link>
    <description>Recent content in Audit Logs on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/audit-logs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Protect Audit Logs from Tampering</title>
      <link>https://nalar.dev/protect-audit-logs-from-tampering/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/protect-audit-logs-from-tampering/</guid>
      <description>&lt;p&gt;Audit logs are most valuable when something has already gone wrong. They help answer who changed a permission, which account performed a sensitive action, and what happened before an incident was detected. But there is a difficult dependency hidden in that design: if the same compromised system can freely rewrite its own audit history, the evidence may become unreliable exactly when responders need it most.&lt;/p&gt;&#xA;&lt;p&gt;The defensive goal is therefore not merely to record events. It is to make important audit records harder to alter without authorization and make suspicious loss or modification easier to detect.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
