<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Secure Configuration on Nalar</title>
    <link>https://nalar.dev/tags/secure-configuration/</link>
    <description>Recent content in Secure Configuration 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/secure-configuration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Harden Security Configuration with Secure Defaults</title>
      <link>https://nalar.dev/harden-security-configuration-with-secure-defaults/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/harden-security-configuration-with-secure-defaults/</guid>
      <description>&lt;p&gt;Many security failures do not require a broken cryptographic algorithm or a sophisticated exploit. A system can expose unnecessary services, leave a sensitive feature enabled, grant broader access than intended, or silently keep an old setting after the application changes.&lt;/p&gt;&#xA;&lt;p&gt;This is a &lt;strong&gt;secure configuration&lt;/strong&gt; problem. The software may be capable of operating safely, but its deployed settings place it in a riskier state.&lt;/p&gt;&#xA;&lt;p&gt;A useful defensive mental model is simple: begin from a known secure baseline, make every relaxation intentional, and verify that the deployed system still matches that intent. This reduces the number of accidental paths from a normal installation to an exposed one.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
