# Finding states and definitions

Findings display with any one of the following states on the Findings page in the NetSPI Platform and/or remediation reports. Each state's meaning is described below. Findings can move from one state to any other state.

# Finding states set by NetSPI Platform users

Finding State	Condition
User Remediated	You can set a finding status to User Remediated when you have remediated the finding, do your own testing, and consider remediation complete. NetSPI does not retest findings in this state.
Ready for Retest	You can set a finding to Ready for Retest when you have remediated the finding from your end and want NetSPI to retest it to confirm the vulnerability is resolved.
Accepted Risk	You can set a finding to Accepted Risk when you acknowledge the vulnerability but consider it a low priority. NetSPI does not retest findings in this state.

Note: After an engagement is completed, only client users will have the ability to change the finding state. Any post-engagement finding state changes made by clients will be view-only by NetSPI staff.

# Finding states set by NetSPI Platform agents

Finding State	Condition
Final	The Final state is set by the NetSPI Agent when they publish a new, verified finding for your organization.
Not Remediated	The NetSPI Agent sets the finding's state to Not Remediated if that specific finding's vulnerability or risk is still present.
Remediated	The NetSPI Agent sets the finding's state to Remediated once they have tested and confirmed the finding has been fixed by your organization.
Not Retested	The NetSPI Agent sets the finding state to Not Retested for a variety of reasons that will be included along with the state. This state is often applied to groups of published findings that have not been retested or are determined to not be in scope.

# Findings and the different NetSPI Platform modules

If you subscribe to more than one NetSPI Platform module (i.e., PTaaS, EASM, and/or BAS) then your findings are viewed and treated by each of the different modules as described below.

A finding created by the following:	Displays/acts as follows under the following module activity:
PTaaS engagement	The finding is updated and used by both PTaaS and EASM if an EASM scan discovers a vulnerability affecting an asset in the PTaaS engagement
PTaaS engagement or EASM with a CVE (critical vulnerability enumeration)	The finding table displays the CVE ID for that finding
PTaaS engagement	The finding is updated and is used by both BAS and PTaaS when a BAS play runs that affects an asset in that PTaaS engagement
EASM	The finding table displays EASM in the Identified By column in the Findings table