<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jordan on ZAP</title>
    <link>/authors/jordan/</link>
    <description>Recent content in Jordan on ZAP</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Nov 2016 00:00:00 +0000</lastBuildDate>
    <atom:link href="/authors/jordan/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Announcing the ZAP Jenkins Plugin</title>
      <link>/blog/2016-11-22-announcing-the-official-zap-jenkins-plugin/</link>
      <pubDate>Tue, 22 Nov 2016 00:00:00 +0000</pubDate>
      <guid>/blog/2016-11-22-announcing-the-official-zap-jenkins-plugin/</guid>
      <description>&lt;p&gt;Using ZAP during the development process is now easier than ever. We are proud to present the Jenkins plugin, it extends the functionality of&#xA;the ZAP security tool into a CI Environment.&lt;/p&gt;&#xA;&#xA;&lt;figure&gt;&#xA;&#x9;&lt;img src=&#34;/blog/2016-11-22-announcing-the-official-zap-jenkins-plugin/images/ZAP_CI_SMALLER.png&#34; alt=&#34;&#34; /&gt;&#xA;&#x9;&lt;figcaption&gt;&lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;h5 id=&#34;the-process-explained&#34;&gt;The process explained&lt;/h5&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;A Jenkins CI Build step initializes ZAP&lt;/li&gt;&#xA;&lt;li&gt;Traffic flows (Regression Pack) through ZAP (Web Proxy)&lt;/li&gt;&#xA;&lt;li&gt;ZAP modifies requests to include Vulnerability Tests&lt;/li&gt;&#xA;&lt;li&gt;Target Application/Server sends Response back through ZAP&lt;/li&gt;&#xA;&lt;li&gt;ZAP sends reporting data back to Jenkins&lt;/li&gt;&#xA;&lt;li&gt;Jenkins publishes and archives the report(s)&lt;/li&gt;&#xA;&lt;li&gt;Jenkins creates JIRA tickets for the alerts&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;The ZAP Jenkins plugin makes use of the readily available and diverse ZAP API, allowing you to use the same session files and scan policy&#xA;profiles between ZAP and the Jenkins plugin, so they can be interchangeably loaded.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
