- August 17, 2023: Linked to definitions; Separated refresh by risk vector to its own page.
- January 30, 2023: Published.
Remediated findings are not reflected in Findings until we detect them with our scans. To initiate a scan, request a refresh. This process is outlined below.
1. Request a Refresh
You may only request a refresh for your MyCompany or a company you've subscribed to using a MySubsidiary license.
To refresh a finding, follow the steps laid out in Requesting a Refresh.
User-requested refreshes not available for select risk vectors. These risk vectors have automated scans that regularly check on findings to see if they are still present. The table below lists these risk vectors, their refresh behavior, and their finding lifetime.
Once a finding is remediated, its Last Seen column will stop updating and it will need to complete its lifetime.
Remediating a finding by taking the asset offline prevents the refresh process from completing successfully. The finding will need to finish its lifetime before it is removed.
2. Review Responses
It takes 3-5 days to complete a findings refresh. Depending on the risk vector, there are four possible outcomes to a successful refresh:
- The old finding is replaced by a new finding.
- A new finding is created and the old one needs to complete its lifetime.
- The old finding stops being updated and needs to complete its lifetime.
- The finding is removed.
See refresh by each risk vector.
3. Troubleshoot Unexpected Responses
Further steps may be necessary if a finding does not update as expected after a refresh. There are three options depending on which part of the result was unexpected:
| Result | Next Steps |
|---|---|
| The finding’s grade did not improve as you thought it would. | Confirm your finding is fixed using the information provided in the article Verifying That a Finding Is Remediated. |
| The refresh status is Asset Not Reached. |
If you are sure the asset is online and nothing is blocking our scans, try the refresh again. If the asset still can't be reached, contact Bitsight Support for further assistance. |
| The finding did not follow the refresh behavior as laid out in the tables above. | Contact Bitsight Support for further assistance. |