Skip to main content
When you retest a finding, Tolmo’s agents try to exploit it again on your live authorized target. If the exploit does not work, the finding becomes Resolved.

​
Retest a finding

  1. Ship the fix to the environment that the agent tested.
  2. Retest the finding.
  3. Tolmo starts a verification run and tells you which agent runs.
Tolmo runs only one retest for each finding at a time. If a retest is already in progress, Tolmo tells you.

​
The agent that runs

Tolmo selects the agent from what it knows about the finding. You can see the run in the run history of that agent and in Mission Control.

​
Retest results

If the target of a finding is outside your authorized domains, the finding waits with the state No permitted domain. Enable offensive testing on the domain, then retest.

​
Findings that you cannot retest

You cannot retest these findings:
  • A draft finding. Publish the draft first.
  • A CVE finding, such as a vulnerable package version from a dependency scanner. To fix a CVE finding, upgrade the package. The scanner then reports the change.
  • An older exploited finding that has no stored exploit. Tolmo exploited these findings before it started to store exploits that it can replay.

​
Testing hours

You can set testing hours. If you request a retest outside these hours, the retest waits until the testing hours start. Tolmo tells you when the retest will start.

​
Closed findings stay closed

You can close a finding or mark it as a false positive. The next run does not show that finding as new again.

​
Next steps

Validate the findings you already have

Let Blue prove or disprove alerts from your scanners.

Mission Control

See all agent runs in one place.