Why doesn't Aftra automatically resolve opportunities that are no longer detected?
It feels efficient to have issues disappear automatically, but we believe it is better to be certain than to rely on assumptions. Our scanners can only report on what they see, they cannot definitively confirm if an opportunity has been resolved.
To avoid a false sense of security, Aftra requires you to manually resolve opportunities. This ensures a human has verified the fix, your security history remains accurate, and you stay in total control of your risks.
-
Confirmation is key / Trust but verify
Aftra cannot definitively confirm that an opportunity has been "fixed", only that we can no longer see it.
An issue might stop appearing because:
- Security patches were successfully applied
- Network traffic was redirected or blocked, hindering us from detecting the opportunity
To help you manage this, Aftra provides a "Possibly Resolved" filter. This highlights opportunities that have not been detected by our scanners for at least 45 days. While this often indicates an opportunity has been resolved, we still require you to confirm it to ensure no blind spots are being ignored.
-
Preserving your security history
We never delete vulnerability data because the "lifecycle" of a risk is vital for your long-term security posture.
- For Resolved Issues: Maintaining the timeline helps you track "time to remediate" and understand which internal steps were most effective
- For False Positives: Marking a finding as a false positive provides us with important feedback to improve our detection logic
-
You manage your risks
Aftra is designed to provide visibility and insight, but security decisions belong to the company. Automatically closing issues could lead to a false sense of security. We believe it is in your best interest that an authorised user makes the final call on whether a risk has been appropriately addressed.
Are there any exceptions?
On rare occasions, if our system identifies a recurring false positive affecting multiple customers, we may issue a system-wide correction. In this case, we aren't "resolving" your specific instance, but rather updating our system logic to ensure more accurate results.