Findings and endpoints
This guide covers the deeper technical routes that sit underneath an engagement.Findings
Finding records live inside an engagement. They are the primary place to preserve:- title and description
- severity and status
- affected endpoints
- remediation and recommendations
- references and evidence
- reproduction steps
- impact, likelihood, and risk details
Open a finding detail page
Use a finding detail page when you need to refine the writeup instead of just scanning the table on the engagement page.Edit and delete behavior
Endpoint editing
Use the endpoint edit page when you need to update:- endpoint name
- operating system
- endpoint type
- linked domain
- address records and address types
Service inventory
The service inventory page is a filtered service view for one engagement. Use it to:- review services discovered across addresses
- filter by address, protocol, or state
- move from service review into finding creation context
Nmap XML parser
Use the Nmap parser page when you have XML exports from Nmap and want to normalize them into the current engagement. The page gives you:- an import surface for the XML file
- a preview of the engagement’s current endpoints
- a way to bring discovered hosts and services into the engagement record instead of recreating them manually
Related routes covered by this guide
/dashboard/engagements/[engagementId]/findings/[findingId]/dashboard/engagements/[engagementId]/endpoints/[endpointId]/edit/dashboard/engagements/[engagementId]/services/dashboard/engagements/[engagementId]/nmap-parse