A Finding is a vulnerability or exploit identified by a tester across your infrastructure, tracked from discovery through remediation.

Table of Contents


Getting Started

Welcome

Platform Onboarding

Testing Process


Using the Platform

Findings Management

Testing Activities

Reporting

Security Metrics & Analysis

Attack Surface

Account Management

Integrations


FAQs & Support

FAQs

Best Practices


<aside> 🔗

Quick Links

Location

Managing Remediation

Commenting and Collaboration

Integrations to Support Remediation

Sprocket Platform Public API

</aside>


Location

To view findings, select Open Findings or All Findings under Findings in the left navigation. [1]

By default, findings are sorted by Severity (descending). Use the filter bar [2] and column headers [3] to narrow and reorder results.

By default, findings are sorted by Severity (descending). Use the filter bar [2] and column headers [3] to narrow and reorder results.

Filters

Filter Description
Status Whether a finding is open or closed
In Project The engagement the finding belongs to, such as External Pentest, Internal Pentest, or Web Application Testing
State is The current remediation status of the finding. Options include Pending Fix, In Progress, Retest Ready, Risk Accepted, and Fixed
Severity The criticality level assigned by the tester. Options include Critical, High, Medium, Low, and Informational
Tag Framework classifications including MITRE ATT&CK, OWASP and PCI
Assigned To The organization member responsible for remediating the finding
Time Period Filters findings by the date they were published to you
Asset Custom Tag Filters by custom tags applied to associated assets

Sort

Click a column header to sort by Severity, Published, or Last Updated. [3]

Export

To export a list of findings, click the Download icon button, then select your preferred file type from the menu. [1]

Export List of Findings_Annotated_box.png

<aside> <img src="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" alt="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" width="40px" />

Note: Finding age is measured from the date the finding was published to you, including in exports and the Public API.

</aside>


Severity Levels

Every finding is assigned a severity level by your Sprocket testing team. Severity reflects the criticality of the vulnerability and the likelihood of successful exploitation.

Critical

High

Medium

Low

Informational


Managing Remediation

Your team can update the State of a finding to communicate remediation progress. The available options depend on the current State of the finding. You can move a finding from Pending Fix to In Progress, then to Retest Ready once you believe the vulnerability has been addressed. You can also move a finding backward at any point.

<aside> <img src="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" alt="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" width="40px" />

</aside>

| --- | --- |

<aside> <img src="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" alt="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" width="40px" />

</aside>

Updating State

State can be updated in two ways, standalone or alongside a comment.

Validating Fixes

Once a finding is marked Retest Ready, your Sprocket testing team is automatically notified and will begin retesting. No further action is required from your team.

<aside> <img src="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" alt="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" width="40px" />

</aside>

Commenting and Collaboration

Integrations to Support Remediation

Sprocket Platform Public API