> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strikepoint.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Findings and endpoints

> Manage detailed technical work inside an engagement, including finding writeups, evidence attachments, remediation workflow, endpoint editing, service inventory, and Nmap import.

export function PermissionRequired({label = "Permission required", children}) {
  return <Callout type="warning">
      <strong>{label}:</strong> {children}
    </Callout>;
}

# 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 narrative and recommendations
* references and evidence text
* reproduction steps
* impact, likelihood, and risk details
* remediation substatus, retest state, owner, due date, and SLA target

### 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.

The finding header summarizes remediation workflow state (substatus, retest, owner, due date, SLA target) and links into the dedicated remediation page.

### Edit and delete behavior

<PermissionRequired>
  Finding edits require finding-edit access. Deleting a finding requires finding-delete access. Depending on your role, you may be able to edit only your own findings unless your role can view and manage all findings.
</PermissionRequired>

### Evidence attachments

Beyond the evidence text field, each finding supports private **Evidence Attachments**.

You can:

* upload evidence files linked to the finding
* download attachments through the secure download route
* delete outdated attachments when you have edit access

Supported uploads follow the same private attachment rules as other engagement files.

### Publish finding to the portal

<PermissionRequired label="Permission required for publishing">
  Approvers with finding-approval access can use **Publish Finding** on the finding detail page to create a portal snapshot for that finding.
</PermissionRequired>

The finding page also shows publication history when prior snapshots exist.

## Remediation workflow

Remediation is more than a text field on the finding writeup. Strikepoint tracks workflow state on a dedicated remediation page and on the org-scoped remediation dashboard.

```mermaid theme={null}
flowchart TD
  A[Finding detail] --> B[Remediation page]
  B --> C[Owner + due date]
  B --> D[Substatus + retest]
  B --> E[Activity timeline]
  F[Remediation dashboard] --> B
```

### Finding remediation page

Open `/dashboard/engagements/[engagementId]/findings/[findingId]/remediation` to manage:

* remediation owner
* due date and SLA target
* remediation substatus (not started through complete, including blocked and risk accepted)
* retest status (not requested through passed or failed)
* activity comments on the remediation timeline

### Remediation dashboard

The remediation dashboard at `/dashboard/remediation` lists findings with active workflow state across your visible engagements.

<Callout type="info">
  **Visibility note:** Remediation is not listed in the dashboard sidebar. Reach it from finding remediation links or by navigating directly to `/dashboard/remediation`.
</Callout>

The dashboard table shows finding title, owner, substatus, retest state, due date, SLA target, and engagement context, with a link into each finding’s remediation page.

Engagement, finding, and remediation surfaces also show a disabled **Jira handoff planned** control. Jira integration is deferred; workflow updates stay inside Strikepoint for now.

## Endpoint editing

Use the endpoint edit page when you need to update:

* endpoint name
* operating system
* endpoint type
* asset owner, application owner, and business unit routing
* asset criticality and rationale
* linked domain
* address records and address types

<PermissionRequired>
  Endpoint edits require endpoint-edit permission.
</PermissionRequired>

## 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, state, subnet, criticality, business unit, or dangerous-service flag
* review subnet-grouped host/service matrix cells for quick assessment-wide situational awareness
* spot common risky exposed services such as RDP, SMB, Telnet, and FTP
* save reusable table views for recurring triage layouts
* 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]/findings/[findingId]/remediation`
* `/dashboard/remediation`
* `/dashboard/engagements/[engagementId]/endpoints/[endpointId]/edit`
* `/dashboard/engagements/[engagementId]/services`
* `/dashboard/engagements/[engagementId]/nmap-parse`

## Related guides

* [Engagements](/dashboard/engagements)
* [Reports](/dashboard/reports)
* [Customer portal](/dashboard/customer-portal)
* [Create and run an engagement](/workflows/create-and-run-an-engagement)