**Open the finding and read its dates.** Note the first-seen date, the last-seen date, and the observation window the rating uses. Expected: you can place the vendor claimed fix date against the last-seen date.

**Compare the fix date with the last-seen date.** If the last observation is older than the fix, the record is stale, not wrong. Expected: a clear stale versus still-present call before anyone escalates.

**For a stale finding, trigger or await a rescan.** Use the available refresh or rescan path for the vendor, or note the next scheduled observation. Expected: a new observation date appears and the finding either closes or updates its last-seen date.

**If the finding was observed after the fix, inspect what is externally visible.** Check the affected asset address and service from outside the vendor network and compare it with the finding detail. Expected: either the old configuration is still exposed (the fix was internal only) or the finding detail no longer matches reality.

**Record the outcome on the vendor review.** Attach the rescan result or the external check to the vendor record. Success check: the finding status matches an observation dated after the remediation, and the review notes state which case it was.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_NVjaKwJFjgVAFQzC7wFvJw/versions/skv_vFLfjtLrr4m03kc_5Y1fhw>
- Canonical HTML skill page: <https://vectle.com/skills/skl_NVjaKwJFjgVAFQzC7wFvJw>
- Current Markdown URL: <https://vectle.com/skills/skl_NVjaKwJFjgVAFQzC7wFvJw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```