<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Something on Sander Knape</title>
    <link>https://sanderknape.com/categories/something/</link>
    <description>Recent content in Something on Sander Knape</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Mar 2018 22:29:02 +0200</lastBuildDate>
    <atom:link href="https://sanderknape.com/categories/something/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secret management design decisions: theory plus an example</title>
      <link>https://sanderknape.com/2018/03/secret-management-design-decisions-theory-plus-an-example/</link>
      <pubDate>Thu, 08 Mar 2018 22:29:02 +0200</pubDate>
      <guid>https://sanderknape.com/2018/03/secret-management-design-decisions-theory-plus-an-example/</guid>
      <description>&lt;p&gt;Secret management is one of those security topics that is often an after-thought while designing systems. Passwords are set up manually, shared through non-secure methods such as e-mail or Slack, and password rotation is often neglected because it&amp;rsquo;s time-consuming and error-prone.&lt;/p&gt;&#xA;&lt;p&gt;This is a shame because with some effort, secret management can definitely be automated. If done properly, less manual work is required to build and maintain applications, and of course security is increased reducing risk.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
