What a scanner found wrong, and how a finding closes itself once it's fixed.
A finding is a problem on a resource, reported whether or not any framework has an opinion about it — an open database is an open database. Findings map to requirements in the same record a framework reads, but they exist independently of any framework you've selected.
Every finding names the check that failed, the exact resource, and how long it has been open.
How to use it
Filter by severity (critical/high/medium/low) or by which connector reported it, using the chips at the top of the screen.
"Open for" shows how long a problem has existed — a finding open for months is a different conversation from one seen last night.
Nothing here needs to be closed by hand. Fix the underlying problem and the next nightly scan simply stops seeing it — silence is read as "fixed," the same way a clean scan of one bucket doesn't mention buckets that were never a problem.
