Indusface WAS CICD plugin publish

[productteam-was]

Repository URL

https://github.com/productteam-was/indusface-was-scan

New Repository Name

indusface-was-plugin

Description

1. A DAST Scanner Plugin for Automated Security Testing: This plugin integrates seamlessly into the Jenkins Pipeline interface, allowing for automated security/DAST scanning within CI/CD workflows.
2. Streamlined Security Integration: Incorporating security checks early in the development lifecycle, it helps identify vulnerabilities before they reach production, ensuring faster and safer releases.
3. Enhanced CI/CD Security: Indusface WAS plugin enables early detection and mitigation of security vulnerabilities through automated DAST scans within the development process.

• Automatically triggers security scans during the build process.
• Retrieves and displays scan results.
• Fails builds based on predefined security thresholds. -If your plugin provides a more user-friendly interface or simplified configuration process.

GitHub users to have commit permission

@productteam-was @techieabhishekakash @AzureAD\GamyaSriyaSomalaraju

Jenkins project users to have release permission

@indusface_jenkins_plugin

Issue tracker

Jira

[jenkins-cert-app]

Security audit, information and commands

The security team is auditing all the hosting requests, to ensure a better security by default.

This message informs you that a Jenkins Security Scan was triggered on your repository. It takes ~10 minutes to complete.

Commands

The bot will parse all comments, and it will check if any line start with a command. Security team only:

• /audit-ok => the audit is complete, the hosting can continue :tada:.
• /audit-skip => the audit is not necessary, the hosting can continue :tada:.
• /audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

• /request-security-scan => the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository :mag:.
• /audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:. It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.31.74)

[github-actions[bot]]

Hello from your friendly Jenkins Hosting Checker

It appears you have some issues with your hosting request. Please see the list below and correct all issues marked Required. Your hosting request will not be approved until these issues are corrected. Issues marked with Warning or Info are just recommendations and will not stall the hosting process.

• :no_entry: Required: The following usernames in 'Jenkins project users to have release permission' need to log into Jira: @indusface_jenkins_plugin (reports are re-synced hourly, wait to re-check for a bit after logging in)
• :no_entry: Required: The following usernames in 'Jenkins project users to have release permission' need to log into Artifactory: @indusface_jenkins_plugin (reports are re-synced hourly, wait to re-check for a bit after logging in)
• :no_entry: Required: The following usernames in 'GitHub Users to Authorize as Committers' are not valid GitHub usernames or are Organizations: AzureAD\GamyaSriyaSomalaraju
• :no_entry: Required: The dependency org.json:json should be replaced with a dependency to the api plugin io.jenkins.plugins:json-api
• :no_entry: Required: The dependency com.google.code.gson:gson should be replaced with a dependency to the api plugin io.jenkins.plugins:gson-api

You can re-trigger a check by editing your hosting request or by commenting /hosting re-check

[jenkins-cert-app]

The Jenkins Security Scan discovered 2 finding(s) :mag:.

For every identified issue, please do one of the following:

• Implement the recommended fix to address the issue.
• If you think it's a false positive, suppress the warning directly within the code.
• Alternative, you write an explanation here about why you think it's irrelevant. That will require a manual review, leading to a slower process.

After addressing the findings through one of the above methods:

• If all modifications have been made to the code, please initiate a new security scan by triggering the /request-security-scan command.
• If there are any unresolved findings (those not corrected or suppressed), request a review from the Jenkins security team by using the /audit-review command.

---

Jenkins: Plaintext password storage

You can find detailed information about this finding here.

SamplePostBuildAction.java#29

``` Field should be reviewed whether it stores a password and is serialized to disk: accessKey ```

ScanAndBuildStatus.java#7

``` Field should be reviewed whether it stores a password and is serialized to disk: secretKey ```