You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2022. It is now read-only.
When users run a security scan of their setup (often after upgrades), they tend to find rather old results from the last time their host was scanned. The small greyed out testing date can be easily missed and people start to doubt about their setups.
There was a discussion on the forum, if you can't just remove old scan results and redo new scans? There isn't any sense in showing such old result (up to a year) or is there?
The text was updated successfully, but these errors were encountered:
scan results should be invalidated after reasonable time (is there any advantage to keep them for long time?)
.. and ideally existing results dynamically change with software development e.g. system using version X with some rating degrades once X+1 is shipped (if dynamic change is too much simple invalidation of the scan DB on every release does the job too - by forcing new scan..)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When users run a security scan of their setup (often after upgrades), they tend to find rather old results from the last time their host was scanned. The small greyed out testing date can be easily missed and people start to doubt about their setups.
There was a discussion on the forum, if you can't just remove old scan results and redo new scans? There isn't any sense in showing such old result (up to a year) or is there?
The text was updated successfully, but these errors were encountered: