<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on Teddy Ferdinand</title><link>https://tferdinand.net/en/tags/git/</link><description>Recent content in Git on Teddy Ferdinand</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 18 Jun 2020 20:02:35 +0000</lastBuildDate><atom:link href="https://tferdinand.net/en/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Turn your AWS DevSecOps Pipeline into bunker - Part 1</title><link>https://tferdinand.net/en/turn-your-aws-devsecops-pipeline-into-bunker-part-1/</link><pubDate>Thu, 18 Jun 2020 20:02:35 +0000</pubDate><guid>https://tferdinand.net/en/turn-your-aws-devsecops-pipeline-into-bunker-part-1/</guid><description>&lt;blockquote&gt;
&lt;p&gt;This post was co-authored by &lt;a href="https://zoph.me/"&gt;Victor Grenu&lt;/a&gt;. Who is working as Cloud Architect&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In this series, we will talk about the emergence of the DevSecOps movement, and more especially, what are the benefits of introducing a DevSecOps approach on your existing CI/CD Pipelines.&lt;/p&gt;
&lt;h2 id="cicd-pipeline"&gt;CI/CD Pipeline&lt;/h2&gt;
&lt;p&gt;To give you some context, you will find in the diagram below a standard CI/CD Pipeline.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://i.imgur.com/EMznwrL.png" alt=""&gt;&lt;/p&gt;
&lt;h2 id="devsecwhat"&gt;DevSecWhat?&lt;/h2&gt;
&lt;p&gt;DevSecOps could be defined as a shift from a central internal security team to the inclusion of security practices into the existing DevOps teams: DevSecOps&lt;/p&gt;</description></item></channel></rss>