Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Results & findings

Results & findings

How do I search findings by title or file location?

Quick answer

On Issues, type in the box that reads Search findings by title or location. It matches finding titles and the Location column. Use a word from the title, an endpoint such as /search, or part of a file path. Search works together with the filters.

The search box is the quickest way to find one finding when you remember a word from it.

Steps

  1. Click Issues.
  2. Click the box that reads Search findings by title or location....
  3. Type a term. The table narrows as you type.
  4. Delete the text to clear the search.

Good to know

The Location column has two shapes, and search covers both.

Finding typeLocation looks likeTry searching for
Black-boxAn HTTP method and path, such as POST /searchThe path, like /search
White-boxA source file and line rangePart of a file name or folder

Search sits on top of the filters. If you get no rows, check that a severity, class or target filter is not hiding the finding. Also check the triage chips. A finding marked Fixed may be hidden.

Some tips:

  • Use short terms. One word beats a full sentence.
  • Search by file name to see everything one file is responsible for.
  • Search by path to see all findings on one endpoint.

Titles are cut off with an ellipsis in the table, but the full title is searchable and shows in the dialog. To search by finding ID, read how to search by issue ID.

Several findings can share one file. That is normal. See why several findings sit in the same file.

Search is also the fastest way to answer a question from a colleague, such as whether the scan has ever reported anything on a particular route or in a particular folder of the code. Type, read, done.

Full tutorial

How to search and filter vulnerability findings on the Issues page

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.