The Secrets tab of the application details section lets you see a complete list of secrets (or sensitive data) exposed by your application.

For each finding in the list, you'll see its:

  • ID
  • Severity level (e.g., critical)
  • Brief description, including vulnerability type and where it is found
  • Tags (e.g., OWASP a1-injection or CVSS 9)
  • Status (e.g., Fixed)
  • Assigned to information (i.e., the team member tasked with further work on this issue)

Filtering findings

You can filter the findings displayed by:

  • Its severity level
  • Its status
  • The person the finding is assigned to

There are also a variety of Advanced Filters that you can use (e.g., category, CVSS score).

The ShiftLeft dashboard's Secrets tab

Viewing detailed finding information

Clicking on a finding in your results list will open a new window pane on the right with detailed information.

  • Description: the description tab shows you the specific secret detected and where ShiftLeft CORE detected it in your code. This section includes a write-up of the issue and why it's a problem, as well as mitigation suggestions for securing your app

  • Comments: the comments tab allows you and your team members to make notes specifically about this finding; if there are multiple comments for this finding, ShiftLeft displays them in reverse chronological order.

Expanded details

In addition to the summary-level information displayed in the findings pop-up, you can open a larger window with additional features; to do so, click Details in the top-left of the initial window opened by ShiftLeft when you click on a specific finding.

The expanded details view features everything in the summary-level view, plus the ability to:

  • Set the finding's status to reflect completed work (e.g., set the status of the finding to Fixed if you've mitigated the issue)

    • Fixed: Mark the finding as fixed (note that setting this status does fix the finding) so that it will no longer be included in that specific set of scan results. Used to indicate that you've applied a remediation of some type.

    • Ignored: Mark the finding as ignored so that it doesn't show up in scan results again. Used to indicate that something is a false positive or is unlikely to impact the application's security. If you set the status to ignored, you must also provide a comment that includes information on your reasoning for choosing this status

    • 3rd Party: Mark the finding as 3rd party to indicate that the finding is in a third-party library; the finding can't be fixed at the moment, but it should be something they return to at a later date.

      Note that status can be changed at a later date if needed.

  • Assign to a team member the vulnerability for further research and work

  • Get a link to issue that's specific to this finding that you can share with others

To return to the summary view, click Minimize in the top-left.