<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>continuous-integration on Rietta Cybersecurity</title>
    <link>https://rietta.com/tags/continuous-integration/</link>
    <description>Recent content in continuous-integration on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <atom:link href="https://rietta.com/tags/continuous-integration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automate Security Scans with Continuous Integration</title>
      <link>https://rietta.com/blog/automate-security-scans-with-continuous-integration/</link>
      <pubDate>Tue, 03 Oct 2017 00:00:00 -0500</pubDate>
      <guid>https://rietta.com/blog/automate-security-scans-with-continuous-integration/</guid>
      <description>&lt;p&gt;There are many tools out there that help you get a quick idea of possible security issues in your code and dependencies, but how often do you run them? If you&amp;rsquo;re running a Rails app and have never run &lt;a href=&#34;https://github.com/presidentbeef/brakeman&#34;&gt;brakeman&lt;/a&gt; or &lt;a href=&#34;https://github.com/rubysec/bundler-audit&#34;&gt;bundler-audit&lt;/a&gt;, I strongly urge you to run these tools immediately. Brakeman finds common insecure coding patterns that might be exploitable in the correct context and bundler-audit checks for known vulnerabilities within your installed gem dependencies.&lt;/p&gt;&#xA;&lt;p&gt;The premise of this blog post isn&amp;rsquo;t to teach you to run these tools, but rather to teach you how to implement these tools into your Continuous Integration service. If you&amp;rsquo;re curious of how to run these tools outside of the test suite, both tool&amp;rsquo;s READMEs are informative.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
