Source
Developer workflow, quality gates & fixes — found from sitemap — Mend.io
Checked for Mend.io on 17 Nov 2026
- Page
- https://docs.mend.io/platform/latest/triage-your-code-security-findings
- Checked
- 17 Nov 2026, 12:03 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:8e08d6db34818b93e97f27704360f806afcff10c07ac8c96df28866bbcb598c2
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Triage purpose Report an error
“As a Security Champion or AppSec manager, Mend.io helps you triage the Mend SAST findings more efficiently.”
-
Prerequisite entitlement Report an error
“Access to the Mend Platform with Code entitlement (SAST) is required to browse the Findings details.”
-
Risk factors Report an error
“Risk Factors in Mend SAST help you prioritize security findings by highlighting key indicators that make a vulnerability more critical or urgent to fix. Each finding may include one or more risk factors based on confidence level, data flow characteristics, and known exploitation patterns.”
-
High confidence default Report an error
“By default, Mend SAST focuses on high-confidence findings to reduce noise and ensure developers receive actionable issues without the need for prior triage.”
-
API endpoint indicator Report an error
“When a finding is accessible via an API endpoint or multiple endpoints, this will be denoted by a corresponding icon in the Risk Factors column”
-
Data flow consolidation Report an error
“To minimize the noise level, the application consolidates findings by taint sink (the snippet at the top). All tainted data flows that reach this sink are combined into one finding.”
-
Source code link Report an error
“there’s a button that contains a link to view the entire source code of the affected file in its repository of origin (GitHub, BitBucket, GitLab, or Azure DevOps)”
-
Cwe description tab Report an error
“It also lists all the Compliance Standard Violations related to the CWE, lists the recommended ways to remediate the finding, and provides resources for further reading related to the type of CWE found.”
-
Secure code warrior training Report an error
“The Training section is available for each finding to see context-based links to content for established training material provided by Secure Code Warrior.”
-
Change severity Report an error
“Change Severity: If you disagree with the severity assigned to the finding, you can change it by clicking it and selecting a different severity from the drop-down menu.”
-
Severity scoring Report an error
“Note: Severity is based on SCA data and takes into account all reported CVEs for a certain CWE. For each CWE a weighted average CVE score is computed from: The CVSS attack vector (confidentiality, integrity, availability) for all CVEs A weighted average CAPEC score (severity and likelihood)”
-
Mark reviewed Report an error
“Mark as Reviewed: Finding classified as true positive, but no immediate action will be taken (maybe because there are other priorities).”
-
Jira issue creation Report an error
“Note: Creating Jira Issues from within the Mend Platform requires you to have Mend's Jira Integration installed and configured.”
-
Suppress findings Report an error
“When a false-positive/acceptable risk is reported, the workflow is to suppress it. This action can be coupled with a suppression reason, for tracking and future reference.”
-
Suppressed jira restriction Report an error
“After a finding is suppressed, it is not possible to create Jira tickets for it. In such scenarios, you will need to unsuppress the finding and only then create Jira tickets for it.”
-
Suppression report Report an error
“You can generate a report of all of your code finding suppressions and their reasons, to detect findings that were suppressed too hastily or accidentally.”
-
Suppression columns Report an error
“Suppressed By Suppression Date Suppression Reason”
-
Comments tab Report an error
“The Comments tab of the finding details pane allows you to comment on the finding, regardless of whether it’s a false-positive or a true-positive. It also displays the finding’s detection date.”
-
Bulk actions Report an error
“This menu allows you to submit Jira issues (requires integration with Jira), suppress/unsuppressed findings, mark findings as reviewed/unreviewed, change severity levels, and add comments.”
-
Share deep link Report an error
“Share: You can share the finding hyperlink (deep link) with your developers, by clicking the pin icon at the top right corner of the finding details pane.”
Scores citing this record
- The Application Security Engineer Code analysis (SAST & code quality)
- The Application Security Engineer Developer workflow, quality gates & fixes
- The Application Security Engineer Platforms, deployment & administration
- The Engineering Manager Code analysis (SAST & code quality)
- The Engineering Manager Developer workflow, quality gates & fixes
- The Engineering Manager Platforms, deployment & administration
- The Lead Developer Code analysis (SAST & code quality)
- The Lead Developer Developer workflow, quality gates & fixes
- The Lead Developer Platforms, deployment & administration
- The Platform Engineer Code analysis (SAST & code quality)
- The Platform Engineer Developer workflow, quality gates & fixes
- The Platform Engineer Platforms, deployment & administration
- The Product Security Officer Code analysis (SAST & code quality)
- The Product Security Officer Developer workflow, quality gates & fixes
- The Skeptic Code analysis (SAST & code quality)
- The Skeptic Developer workflow, quality gates & fixes
- The Skeptic Platforms, deployment & administration