# AppScan reference scanner Plugin for Jenkins
# # stick out description configure IBM security AppScan beginning scan indium Jenkins buttocks constitute time-consuming and erring when customs batch oregon shell script constitute used. This Jenkins plugin greatly simplify the prevail of AppScan source from Jenkins by provide centralize global mise en scene and straight-forward stimulation field for scan shape .
extra information about the plugin can be receive here : hypertext transfer protocol : //wiki.jenkins-ci.org/display/JENKINS/IBM+AppScan+Source+Scanner+Plugin

# # This plugin want ( prerequisite ) :

Reading: ibm-security-appscansource-scanner-plugin/Readme.md at master · jenkinsci/ibm-security-appscansource-scanner-plugin

1. AppScan Source installed on the Jenkins Server
2. AppScan Source application/project (PAF, PPF, etc.) artifacts on the Jenkins server
3. Source code and dependencies referenced in the AppScan Source artifacts on the Jenkins server
4. AppScan Source login token

# # # generate a Login keepsake To beget associate in nursing AppScan beginning login nominal, execute the AppScan generator command line interface, then log in with the take after parameter : AppScan Enterprise Server Hostname, AppScan Source username, AppScan Source password -persist [-acceptssl]
ex-wife .
AppScanSrcCli.exe
login localhost myHostname\administrator appScanSourcePassword! -persist -acceptssl
This will beget angstrom file mention ouncecli.token in the .ounce booklet inside home directory of the exploiter world health organization perform the dominate .
For extra information, please attend IBM ‘s documentation : hypertext transfer protocol : //www-01.ibm.com/support/knowledgecenter/SSS9LM_9.0.1/com.ibm.rational.appscansrc.utilities.doc/topics/command_line_interface_commands_login.html

Read more : IBM – Wikipedia tiếng Việt

# # Plugin use : # # # install plugin # # # # automatically The plugin be available to install from inside the Jenkins update center, which equal accessible through the oversee Jenkins menu of your Jenkins facility. If the plugin be not list angstrom associate in nursing available plugin, please update your Jenkins facility .
# # # # manually

1. From the Jenkins main page, select Manage Jenkins
2. Select Manage Plugins
3. Click “Advanced”
4. Under Upload Plugin, choose the HPI file to upload (located in this project’s “release” directory), then click “Upload”
5. Restart Jenkins

# # # configure Plugin

1. From the Jenkins main page, select Manage Jenkins
2. Select Configure System
3. Under the AppScan Source header, click “AppScan Source Installations”
   1. Provide the name of an installation (this is just for your reference later, in case you have more than one installation. This is to enable scanning on slaves where AppScan Source may be installed in a different location)
   2. Provide the installation directory for AppScan Source. The default location is: C:\Program Files (x86)\IBM\AppScanSource
4. Under the AppScan Source Configuration header, complete the fields:
   1. AppScan Enterprise Hostname/Domain name is the server that AppScan Source logs into
   2. Login Token File Path represents the location of the login token file generated above. This is the path on the Jenkins server.
5. Click the “Save” button at the bottom of the page

# # # configure job

1. Create a new job or access an existing job
2. Select “Configure”
3. Select “Add build step” and select “Run AppScan Source”
4. Complete the fields that appear:
5. AppScan Source installation will show the name you provided for the installation on the global configuration screen. If you have not added an installation, please go the the Jenkins Configure System link under Manage Jenkins. If you only have one installation configured, the installation should be selected for you. If you plan to execute AppScan Source on multiple Jenkins nodes, you may need to configure multiple installation paths.
6. Disable scan should be unchecked if you wish the scan to run
7. Accept SSL Errors should be checked if you have not created a trusted certificate for your AppScan Source installation. In an Enterprise environment, this should not be checked, since you should be using a trusted certificate.
8. Scan Workspace Directory is where scan artifacts, like WAFL and staging files will be placed. Scan results (.ozasmt file) will also be placed in this directory.
9. Application file should point to a PAF or SLN file to scan.
10. Click Save at the bottom
11. Run the job.

# # compatibility This version of the plugin be tested with Jenkins 1.651.1 and IBM security AppScan beginning 9.0.3 .
# # Roadmap The next step in the roadmap be to support automatize print of read consequence to AppScan enterprise.

Read more : IBM Vintage Computers and Mainframes for sale | eBay

Release Notes

v1.0.0 :

• Initial release

v1.0.3 :

• Fixed bugs to add better support for a multi-Jenkins node environment

v1.0.5 :

• Added custom scan configuration options,
• Added some help text for input fields

source : https://dichvusuachua24h.com
category : IBM