<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets Management, Best Practices on Secure Delivery</title><link>https://securedelivery.io/tags/secrets-management-best-practices/</link><description>Recent content in Secrets Management, Best Practices on Secure Delivery</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 18 Apr 2022 14:38:14 +0000</lastBuildDate><atom:link href="https://securedelivery.io/tags/secrets-management-best-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>The Lost Art of Keeping a Secret</title><link>https://securedelivery.io/articles/the-lost-art-of-keeping-a-secret/</link><pubDate>Mon, 18 Apr 2022 14:38:14 +0000</pubDate><guid>https://securedelivery.io/articles/the-lost-art-of-keeping-a-secret/</guid><description>When we&amp;rsquo;re working with product development teams, one of our foundational principles is that product security isn&amp;rsquo;t just a quality of what&amp;rsquo;s being delivered, it&amp;rsquo;s in the quality of your ways of working, too. There are many ways that how you&amp;rsquo;re delivering products can cause security issues. One of these ways is how you&amp;rsquo;re handling the secrets that are part of your product development (credentials, API keys, private certificates, etc.). A screw-up here can very quickly cause a Very Bad Day™, so what should we be doing to keep our secrets, well, secret?</description></item></channel></rss>