<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Monitoring on Nalar</title>
    <link>https://nalar.dev/tags/monitoring/</link>
    <description>Recent content in Monitoring on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design Security Logs for Incident Detection</title>
      <link>https://nalar.dev/design-security-logs-for-incident-detection/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/design-security-logs-for-incident-detection/</guid>
      <description>&lt;p&gt;Security logging is not simply collecting more application output. Its purpose is to leave reliable evidence of security-relevant activity so that suspicious behaviour can be detected, investigated, and explained.&lt;/p&gt;&#xA;&lt;p&gt;Useful logs answer practical questions: what happened, when did it happen, which identity or client was involved, what resource was affected, and what was the result?&lt;/p&gt;&#xA;&lt;h2 id=&#34;log-security-decisions-not-every-detail&#34;&gt;Log security decisions, not every detail&lt;/h2&gt;&#xA;&lt;p&gt;Start with events that represent changes in identity, authority, access, or security state.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
