We would like most basic and obvious web security testing cases to be done automatically while human testing is focused on deeper security issue reviews. The objective of automated web security testing is to integrate the security testing tools with a continuous integration framework, such as Jenkins. The web security testing can be automatically triggered every time the build is submitted. To be able to integrate web security testing tools with Jenkins, there are several key criteria that we need to consider:
- Command console: Most security testing tools provide a command console or GUI interface to operate the security testing procedures. It would be ideal for the tool to provide both interfaces. The command console can be used for Jenkins to trigger the execution of the security testing, and the GUI can help the human testing. From the automated...
