Working with findings
Statuses, ownership, accepted risks and automatic confirmation of fixes.
A finding is an issue Värn has observed on an asset. Every finding contains:
- Why it matters – explained for a non-specialist
- Recommended fix – numbered steps an IT consultant can follow
- Technical evidence – exactly what was observed, when and where
- Limitations – what the check cannot determine
- Activity log – everything that has happened to the finding
Statuses
| Status | Meaning |
|---|---|
| Open | The issue has been observed and nobody has started fixing it. |
| In progress | Someone is working on the fix. |
| Resolved | The issue is no longer observed, or has been marked as resolved. |
| Accepted risk | The organisation has deliberately chosen not to fix it. Requires a reason. |
| False positive | The finding does not apply to your environment. Requires a reason. |
Accepted risk and False positive are decisions that require the administrator or owner role and a written reason, which is stored in the activity log.
Automatic confirmation of fixes
You do not need to close findings by hand. When a check runs without observing the issue, the finding is marked as Resolved automatically. If the issue comes back, the same finding is reopened – with its full history kept.
Findings are only closed automatically if the check could actually be carried out. A server that did not respond never counts as a fixed issue.
No duplicates
The same issue on the same asset is always the same finding, however many scans run. That keeps the history understandable and saves you from cleaning up lists.
Ownership and comments
Assign the finding to a member of the organisation and use comments to record what has been done – for example the ticket number at your IT partner. Everything is kept in the activity log and can be shown in an audit.