View the results of your Mend Developer Platform SCA scan in Bitbucket Cloud
Overview
Once your Mend Developer Platform engine scans are completed, there are multiple resources provided to help you review, analyze, and triage your results.
Viewing Details of the Scan
Results can be viewed in the following places:
The Issues Tracker section in your Bitbucket Cloud repository.
The Commits tab shows build statuses for each commit to the specified base branch.
The commits comments inside each specific commit.
Code Insight report in the Pull Requests.
The Mend Platform UI
Via email notifications
Viewing the Issues section
If you do not see the Issues section in the left panel of Bitbucket Cloud, please go to Repository settings → Issue tracker and enable issue tracker for this repo. Admin rights for this repository are required.
If you are performing Pull Requests or push commands via the Web browser, refresh your Web browser in order to view the issues that were generated by Mend.
Note: It may take a number of minutes for the issues to be scanned and displayed after a valid push command is initiated.
The Issues section displays all the issues that the Mend Integration detected. As part of your workflow, you have the option to close issues that were resolved. Issues manually closed will not be re-opened during future Mend scans unless their tag and/or name are changed.
Viewing Mend Security Checks
Once Mend Security Check is running, Status Check messages are displayed for each commit. Clicking a specific security check message opens a related head commit with detailed information about found vulnerabilities:
Security Check
The Security Check report displays all the vulnerabilities that were found in descending order according to the severity and CVSS score. The following information is displayed for each vulnerability:
CVE: A link to the related CVE page for the vulnerability. Displayed in a collapsible format (click the arrow to expand/collapse for more information regarding the vulnerability).
Severity: Overall score of the severity (
High, Medium, Low
).CVSS Score
Vulnerable Library
Suggested Fix
Issue: A link to the Mend issue that was generated for the vulnerability.
Types of Indicators
The following status indicators are available as feedback on a head commit:
Queued: Scan has not begun and is scheduled to begin.
In progress: Scan is in progress.
Completed: Scan completed with one of the following conclusions:
Success: When the parameter 'vulnerable.check.run.conclusion.level' is set to 'success', the status of the head commit is always success A 'Success' status is displayed for the commit even when it fails.
Failure: Default for all completed scans. When the parameter 'vulnerable.check.run.conclusion.level' is set to 'failure' (default), the status of a 'failed' head commit is 'failure', and a policy for approving merging pull requests that include failed head commits with another branch in the repository is enforced. Note that a 'failed' status can be caused due to security vulnerabilities or due to an error that occurred during the scan.
Neutral: Conclusion occurs when the push command was not valid.
Samples of Check Status Indicators
In Progress
The following is a sample of a 'Running' status, which indicates that the security check is currently scanning the head commit.
Completed with Success Conclusion
When no vulnerabilities are found and no errors occurred during the scan, Mend will display the following commit status, and a security report indicating that no vulnerabilities were detected.
Completed with Failure Conclusion
All head commits that fail the scan due to the security check detecting vulnerabilities or due to an error that occurred during the scan, will display a failed commit status.
The following screenshot displays a failure indicator for a head commit
Security Check with Partial Scan results
In case when during the scanning of the repository Mend encountered exceptions thrown by the package managers there will be a message indicating that the scan results might be partial (i.e. Mend was not able to pull all of the dependencies for scanning).
This message is displayed only in the description of the Security Check and does not affect its status. It is also possible to use the strictMode parameter so all the Checks with this message will fail even if no vulnerabilities are detected during the scan.
Viewing Mend License Checks
On the Commits page, you can view the status and results of each scan. Open a specific commit in order to view the Mend check.
Types of Mend License Check Indicators
The following commit status indicators are available as feedback on the head commits:
Success: No license policy violations were detected.
Failed: One or more license policy violations were detected during the Mend scan.
Viewing Details in the Mend Application
In the Mend Application, Mend Projects will have the same name as the corresponding Bitbucket Cloud repository, with a "BB_
" prefix. The name of the Mend Application will be your Bitbucket Cloud Project name preceded by "BB_".
When a scan is completed for each branch defined in your baseBranches parameter, a Mend project is created for that branch with a “BB_
" prefix. Let’s look at an example:
Bitbucket hierarchy:
vulnerable-node repository
main
branch [default branch]Mend Developer Platform settings for
"baseBranches": ["main", "dev"]
dev
branch
We run a scan on both the main
and dev
branches. The Mend hierarchy appears as:
Mend Platform hierarchy:
Application: BB_vulnerable-node
Project: BB_vulnerable-node_main
Project: BB_vulnerable-node_dev
Within the Mend Application, You can filter the results by engine type:
(1) Dependencies -> Open-Source Security
(2) Code -> Code Security