<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security Monitoring on Nalar</title>
    <link>https://nalar.dev/tags/security-monitoring/</link>
    <description>Recent content in Security Monitoring 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/security-monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design Actionable Security Alerts</title>
      <link>https://nalar.dev/design-actionable-security-alerts/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/design-actionable-security-alerts/</guid>
      <description>&lt;p&gt;Collecting security logs does not guarantee that anyone will notice an attack or dangerous failure. A system can record every authentication failure and privilege change yet still leave responders searching through millions of events after the damage is done.&lt;/p&gt;&#xA;&lt;p&gt;A &lt;strong&gt;security alert&lt;/strong&gt; is a signal that selected activity may require investigation or action. The difficult part is not generating alerts. It is generating alerts that are timely, understandable, and reliable enough that responders know what to do next.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
