<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DevSecOps - Aqua</title>
	<atom:link href="https://www.aquasec.com/category/devsecops/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Cloud Native Security, Container Security &#38; Serverless Security</description>
	<lastBuildDate>Mon, 06 Jan 2025 19:18:33 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>From Theory to Practice: How to Make DevSecOps Work in Your Organization</title>
		<link>https://www.aquasec.com/blog/from-theory-to-practice-how-to-make-devsecops-work-in-your-organization/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Wed, 04 Dec 2024 07:10:06 +0000</pubDate>
				<category><![CDATA[DevSecOps]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=23789</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/from-theory-to-practice-how-to-make-devsecops-work-in-your-organization/" title="From Theory to Practice: How to Make DevSecOps Work in Your Organization" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2024/12/blog-main-DevSecOps-Buyers-Guide-1200x628-2024-final.jpg" alt="From Theory to Practice: How to Make DevSecOps Work in Your Organization" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>Houston, we have a problem: implementing DevSecOps isn’t as straightforward as it seems. DevSecOps has redefined security in modern software development, becoming the benchmark for organizational success. By embedding security into every phase of the development lifecycle, organizations can deploy faster and collaborate more efficiently while ensuring security at every step. Yet, despite its advantages,&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Cloud Native Best Practices: Security Policies in CI/CD Pipelines</title>
		<link>https://www.aquasec.com/blog/cloud-native-security-best-practices-devops-security/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Wed, 22 Jan 2020 13:17:09 +0000</pubDate>
				<category><![CDATA[DevSecOps]]></category>
		<category><![CDATA[CI/CD]]></category>
		<category><![CDATA[Cloud Native Security]]></category>
		<category><![CDATA[Image Vulnerability Scanning]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=15654</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/cloud-native-security-best-practices-devops-security/" title="Cloud Native Best Practices: Security Policies in CI/CD Pipelines" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2020/01/ezgif-5-363063120a.jpg" alt="Cloud Native Best Practices: Security Policies in CI/CD Pipelines" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>With the continual leftward shifting movement of traditional DevOps responsibilities, organizations can now detect security issues earlier in the software development lifecycle (SDLC). Using CI/CD tools such as Jenkins, GoCD, or Bamboo, organizations can continually develop, test, and ship applications. As containers are becoming the architecture of choice for cloud native applications development, developers are&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Shift Security Left, Then Shift Up</title>
		<link>https://www.aquasec.com/blog/devsecops-pipeline/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Wed, 12 Jun 2019 12:50:57 +0000</pubDate>
				<category><![CDATA[DevSecOps]]></category>
		<category><![CDATA[Image Vulnerability Scanning]]></category>
		<category><![CDATA[Software Supply Chain Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=15824</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/devsecops-pipeline/" title="Shift Security Left, Then Shift Up" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2019/06/shift-left-shift-up_blog-2.jpg" alt="Shift Security Left, Then Shift Up" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>Many of you may be familiar with the shift left security approach in which security is built in at an early stage of the application development life cycle. It is easier and more effective to do it early, rather than discover security issues later in the game, when applications are already deployed. When issues are&#160;&mldr;]]></description>
		
		
		
			</item>
	</channel>
</rss>
