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 see only one vulnerability class, like Injection?

Quick answer

On the Issues page, open the third dropdown (All classes) and pick a class such as Injection, Xss or Authz. The table then lists only findings of that class. Choose All classes to clear it. The class is also a column in the table.

Every finding belongs to a vulnerability class. The Issues page lets you view one class at a time.

Steps

  1. Click Issues in the sidebar.
  2. Open the dropdown that reads All classes.
  3. Choose the class you want, such as Injection.
  4. Only that class remains. Check the Class column to confirm.

Good to know

The list offers these classes:

ClassCovers
InjectionSQL, NoSQL, command and template injection, and similar.
XssReflected, stored and DOM cross-site scripting.
AuthLogin, session, MFA, OAuth and token handling.
AuthzAccess control, such as one account reading another's data.
SsrfServer-side request forgery.
CryptoWeak keys, wrong algorithms, unsafe comparisons.
ConfigHeaders, CORS, cookies, TLS, error detail.
Business-logicPricing, quota, replay and workflow flaws.
DependencyVulnerable libraries.
SecretsCredentials and keys in the wrong place.

The in-app documentation describes eight specialist areas that analyse code. The filter list is wider, because it also includes Dependency and Secrets.

Each finding sits in the lane it came from. Each lane stays separate so the same weakness is not reported many times. An injection issue shows up once, not under several classes.

When you start a profile, you can also choose which classes to scan. If a class never appears, check the profile's Scope section.

Filtering by class is handy when one developer owns one area, because the person who looks after login code can work through Auth findings while a colleague takes Injection. Share the filtered view with the owner of that code, and agree who takes which class before the sprint starts so that nothing is picked up twice or missed. Split the work.

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.