<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automated Security on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/automated-security/</link><description>Recent content in Automated Security on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 04 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/automated-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 18: Security Testing &amp;amp; Integration into CI/CD Pipelines</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/security-testing-ci-cd/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/security-testing-ci-cd/</guid><description>&lt;h2 id="introduction-to-automated-security"&gt;Introduction to Automated Security&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 18! So far, you&amp;rsquo;ve learned to think like an attacker, understand common web vulnerabilities, and implement secure coding practices. That&amp;rsquo;s fantastic! But imagine having to manually check every line of code or every deployed application for these issues. It would be slow, error-prone, and unsustainable, especially in today&amp;rsquo;s fast-paced development environments.&lt;/p&gt;
&lt;p&gt;This chapter is all about automation! We&amp;rsquo;ll explore how to integrate security testing directly into your development workflow, specifically leveraging Continuous Integration and Continuous Delivery (CI/CD) pipelines. This proactive approach, often called &amp;ldquo;Shift Left,&amp;rdquo; means finding and fixing security issues earlier, when they are much cheaper and easier to resolve. By the end of this chapter, you&amp;rsquo;ll understand different types of automated security tests and how they fit into a modern development pipeline.&lt;/p&gt;</description></item></channel></rss>