Open the scan from Recent Scans, stay on the Overview tab and click the Profile link under Run details. It takes you straight to that page, which opens with every saved setting. A scan's subtitle also names its profile.
Steps
Use it to check the exact setup behind a run, such as the classes, roles and filters.
- Go to Recent Scans. Choose it in the sidebar.
- Click the scan. The detail page opens on Overview.
- Find Run details. It lists Status, Trigger, Location and Profile.
- Click the profile name. The profile page opens.
- Review the settings. Check scope, roles and reporting.
Good to know
The profile page is the edit form, with Scope, Authentication and Reporting sections. The target is read-only there, because a profile's target is fixed after creation.
Settings can change after a run. The link opens the profile as it is now, not as it was at launch. Keep that in mind when you compare old and new results.
Click Cancel at the top right to leave without changes, or edit and click Save.
Why open the profile
A short trip to the profile answers most why-did-it-find-this questions. You can see the ticked classes, whether the exploitation phase was on, which roles were set, and the report filters. If the link opens a profile that no longer exists, it was deleted after the scan ran.
When you edit a profile, save before you start a new scan, because unsaved changes are lost if you press Cancel. The next run then uses the saved version, which you can confirm from the same link. Save first.
Related questions
- How do I see which commit a white-box scan tested?
- How do I re-run a previous scan?
- What does the trigger badge, such as Manual, mean on a scan?
- How do I see the severity breakdown for one scan?
- Where do I see how much a scan cost and how many tokens it used?
How to edit a scan profile
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.