> Markdown version of [/videos/53-securing-your-web-application-pipeline-from-intruders?t=1540](https://www.wearedevelopers.com/videos/53-securing-your-web-application-pipeline-from-intruders?t=1540). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Securing Your Web Application Pipeline From Intruders Is your CI/CD pipeline an open door for attackers? Embed automated security testing directly into your deployments to stop threats without sacrificing release velocity. - **Speakers:** Milecia Mcgregor - **Event:** WeAreDevelopers LIVE - **Published:** October 12, 2020 - **Duration:** 44:30 - **URL:** https://www.wearedevelopers.com/videos/53-securing-your-web-application-pipeline-from-intruders ## Summary As the "Shift Left" movement in DevOps places CI/CD ownership directly in the hands of developers, the pressure to deliver rapid updates often causes pipeline security to be overlooked. Attackers routinely capitalize on this oversight by deploying open-source automated suites like Kali Linux to exploit misconfigurations, unchecked package vulnerabilities, and lingering open ports. By establishing fundamental operational hygiene—such as enforcing the pipeline as the exclusive deployment mechanism, maintaining strict pre-production environment parity, and keeping builds small for rapid execution—teams can significantly narrow the attack surface before even introducing specialized tools. Embedding automated testing organically throughout the pipeline creates robust defense-in-depth without sacrificing deployment velocity. During the build phase, Static Application Security Testing (SAST) tools like Snyk, OWASP Dependency-Check, and Retire.js preemptively identify vulnerable open-source packages and dependencies. As the artifact moves into testing and delivery, Dynamic and Interactive Application Security Testing (DAST/IAST) tools—including OWASP ZAP, Veracode, and SQLMap—actively hunt for runtime exploits like cross-site scripting and SQL injection. Furthermore, infrastructure testing platforms like Chef InSpec can automate technical compliance audits for regulatory frameworks such as HIPAA and GDPR. Applying these dynamic methodologies directly within CI/CD configurations—whether using traditional YAML in CircleCI and Travis CI or alternative Python-based frameworks—transforms security from a disruptive operational bottleneck into a continuous asset. Beyond automated software scans, securing a pipeline requires unyielding operational protocols: utilizing scanners like git-secrets to prevent credential leaks to version control, enforcing strict role-based access control (RBAC) to restrict risky deployment privileges, and engaging bug bounty platforms like HackerOne for continuous production monitoring. Ultimately, adopting an attacker’s mindset and encrypting all application data ensures that sophisticated threat actors face an inherently hostile and resilient cloud architecture. **Keywords:** ci/cd pipeline security, shift left devops, web application vulnerabilities, sast and dast tools, automated compliance testing, secret management in version control, open port scanning, environment parity, owasp top 10, dependency vulnerability scanning, role-based access control, yaml pipeline configurations, bug bounty programs, sql injection prevention, cross-site scripting mitigation, dynamic application security testing, penetration testing suites, secure continuous deployment ## Chapters 1. **Introduction to securing web application deployment pipelines** (00:00) — Mitigating the escalating risks of data breaches requires implementing proactive security measures directly inside deployment workflows. 1. **Establishing best practices for efficient deployment pipelines** (03:27) — Small build sizes and parity between staging and production environments prioritize fast and reliable code deployments. 1. **Why continuous integration security is often overlooked** (07:31) — The shift left movement imposes time constraints and unfamiliar configurations that delay pipeline security integration. 1. **Tactics and tools used by external malicious actors** (12:10) — External attackers leverage automated suites, misconfigurations, leaked secrets, and outdated dependencies to compromise existing software. 1. **Integrating static security scanning in the build phase** (17:06) — Software composition analysis scanners identify vulnerable dependencies before compiled artifacts reach subsequent deployment stages. 1. **Dynamic application security testing during the test phase** (20:51) — Dynamic and interactive application scanners actively detect runtime vulnerabilities like cross-site scripting and authentication failures. 1. **Running compliance and security audits in pre-production delivery** (23:32) — Specialized pre-production checks enforce regulatory compliance and prevent destructive database queries before production deployment. 1. **Managing vulnerabilities in production environments through bug bounties** (25:40) — Crowdsourced human testing uncovers deeply hidden logic flaws that automated tools miss in production systems. 1. **Implementing manual security practices and pipeline configuration management** (28:16) — Routine management of user access permissions and deployment controls prevents unauthorized pipeline usage and data leaks. 1. **Embedding automated vulnerability analysis within CircleCI workflows** (34:58) — Utilizing dedicated security orbs within YAML configurations surfaces critical dependency risks dynamically during scheduled builds. 1. **Constructing secure Python deployment sequences using Conductor** (38:15) — Structuring continuous delivery flows through Python rather than YAML streamlines dependency testing and containerized node execution. 1. **Configuring open source dependency tests in Travis CI** (40:42) — Adding security commands to standard open source build configurations blocks known vulnerabilities from entering public codebases. 1. **Reviewing core strategies for robust pipeline security** (41:45) — Committing to proactive credential scanning and routine pipeline audits blocks attackers from discovering easily explorable backdoors. ## Related Moments - [Evaluating current trends in CI/CD pipelines](https://www.wearedevelopers.com/videos/333-cd2cf-continuous-deployment-to-cloud-foundry) (from "CD2CF - Continuous Deployment to Cloud Foundry") - [Encouraging broader team adoption of security automation practices](https://www.wearedevelopers.com/videos/1193-it-s-a-testing-trap-common-testing-pitfalls-and-how-to-solve-them) (from "It's a (testing) trap! - Common testing pitfalls and how to solve them") - [Integrating security into initial continuous integration deployment pipelines](https://www.wearedevelopers.com/videos/338-demystifying-devops-pros-cons-dos-don-ts) (from "Demystifying DevOps—Pros, cons, dos & don'ts") - [Injecting automated security into mobile CI/CD pipelines](https://www.wearedevelopers.com/videos/273-devsecops-injecting-security-into-mobile-ci-cd-pipelines) (from "DevSecOps: Injecting Security into Mobile CI/CD Pipelines") - [Transitioning toward DevSecOps with dynamic scanning and secrets management](https://www.wearedevelopers.com/videos/83-enabling-automated-1-click-customer-deployments-with-built-in-quality-and-security) (from "Enabling automated 1-click customer deployments with built-in quality and security") - [Shifting left and creating internal security champion programs](https://www.wearedevelopers.com/videos/346-stranger-danger-your-java-attack-surface-just-got-bigger) (from "Stranger Danger: Your Java Attack Surface Just Got Bigger") ## Related Articles - [Walking Into The Era of Supply Chain Risks](https://www.wearedevelopers.com/magazine/106-walking-into-the-era-of-supply-chain-risks) - [Understanding and Mitigating Common Web Vulnerabilities](https://www.wearedevelopers.com/magazine/565-understanding-and-mitigating-common-web-vulnerabilities) - [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed) - [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development) ## Related Jobs - [Engineer, Offensive Security Organization](https://www.wearedevelopers.com/jobs/ext/1992296-engineer-offensive-security-organization) at **Twilio** - [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/1921051-staff-developer-advocate-github-security-lab) at **GitHub** - [Staff Engineer - Offensive Security](https://www.wearedevelopers.com/jobs/ext/1226927-staff-engineer-offensive-security) at **Twilio** - [Endpoint Security Engineer - OT](https://www.wearedevelopers.com/jobs/ext/1306782-endpoint-security-engineer-ot) at **ZEISS Group** - [Staff Engineer, Security Engineering Partners](https://www.wearedevelopers.com/jobs/ext/1187268-staff-engineer-security-engineering-partners) at **Twilio** - [Penetration Tester / Red team Specialist](https://www.wearedevelopers.com/jobs/ext/293774-penetration-tester-red-team-specialist) at **Raiffeisen Bank International AG**