<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security, Delivery on Secure Delivery</title><link>https://securedelivery.io/tags/security-delivery/</link><description>Recent content in Security, Delivery on Secure Delivery</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 01 Jul 2020 09:41:00 +0100</lastBuildDate><atom:link href="https://securedelivery.io/tags/security-delivery/index.xml" rel="self" type="application/rss+xml"/><item><title>The Biggest Misconception in Application Security</title><link>https://securedelivery.io/articles/biggest-misconception-in-appsec/</link><pubDate>Wed, 01 Jul 2020 09:41:00 +0100</pubDate><guid>https://securedelivery.io/articles/biggest-misconception-in-appsec/</guid><description>I&amp;rsquo;ve touched on this in previous articles, but it&amp;rsquo;s worth dedicating a little time to this misconception as it&amp;rsquo;s at the root of so many of the problems that organisations have with security and delivery. A common way to think about maintaining security while delivering software systems at pace is this.
Where rapid delivery of changes into production is one end of a scale, being secure is at the other end and, as an organisation, you pick where along the scale you&amp;rsquo;re comfortable according to your risk appetite.</description></item></channel></rss>