Acclaimed by the DevOps world and best known as the leading open source automation server for continuous integration (CI) and continuous delivery (CD), Jenkins is a Java-based program designed to monitor a set of executions in a software environment. Jenkins allows developers to rapidly detect and resolve errors in the code base and boosts automated build testing.
For example, Jenkins works on autopilot and presents an easy continuous system for integration. From there on out, developers can complete test cycles quickly and comfortably so that each new build can be delivered quickly and efficiently.
To date, Jenkins has over 1 million users and more than 147,000 active users around the world, along with well over 1,000 plugins integrating Jenkins with various development, deployment and testing tools. Among those plugins, developers can be sure to find an array of plugins on the topic of security. By adding such security plugins, developers are integrating security from step one in the development stage, making the writing of safer and better code easy.
A Closer Look: Securing with Jenkins
Some of the biggest security vulnerabilities to bring down applications can be flagged and fixed way before the application should be ready for release. Yet, more often than we want to believe, security testing does fall between the cracks – mainly due to that developers simply don’t have the time to perform them.
One of the most effective ways to ensure security is by integrating security directly into a developer’s toolbox, and if Jenkins is your chosen CI/CD server – you’re in luck. Thanks to Jenkins, you have plenty of automated security tools at your fingertips, to help you catch vulnerabilities earlier in the development lifecycle.
ZAP – Zed Attack Proxy
ZAP is an open source tool developed by OWASP, aiming to help developers test for common vulnerabilities typically found within web applications, such as SQL Injection and Cross-Site Scripting. ZAP breaks down the application’s code to find vulnerabilities, and then analyzes the issues found, flags error messages and marks the areas within the application that expose sensitive information.
As open source projects may not have updated vulnerability databases, having a dependency checker on your side is vital. OWASP’s Dependency-Check is a plugin that seeks known and/or publicly disclosed vulnerabilities. By using this dependency-checker during the build, developers bypass old and out-of-date vulnerability libraries thus allowing them to detect vulnerabilities as they appear and avoid potentially disastrous mistakes all in all.
CxSAST Jenkins plugin is a source code analysis solution that helps identify, monitor and fix errors, vulnerability issues and compliance problems found within the source code. The CxSAST plugin scans the source code and supplies scan results as either static or interactive reports; interactive meaning the enablement of runtime tracking per vulnerabilities in the code. This plugin will then administer the necessary remediation guidelines and action items.
Continue reading: The AppSec How To: Application Security in Continuous Integration
She aims to educate and inspire developers, security professionals, and organizations to find the best defense against online threats.
Latest posts by Arden Rubens (see all)
- Continuous Security Testing for Microservices – October 19, 2017
- Checkmarx Expands Codebashing Developer Application Security Training With New Interactive Mobile Security Courses – October 18, 2017
- Checkmarx Expands Codebashing Developer Application Security Training With New Interactive Mobile Security Courses – October 17, 2017
Sign up today & never miss an update from the Checkmarx blog
This is a Security Bloggers Network syndicated blog post authored by Arden Rubens. Read the original post at: Blog – Checkmarx