Assessment console / A deliberate action, a visible record
One surface.
Many ways to inspect it.
Choose an input, start an assessment, then read the run log and coverage before its findings.
The console shows data from an existing record or an assessment you explicitly request. Opening this page does not start a scan, open a sandbox or invoke a tool.
Server console
Pick a product in the rail and a target to scan. The coverage-aware verdict, the category-to-evidence drill, and the scan replay appear once the scan completes. Open one from the registry.
Point Sentinel at a server
Choose how to provide the target - you get one coverage-aware verdict.
02
Read the result.
Then read what produced it.
The console keeps the selected product lens attached to the server’s available evidence. Method, coverage and failed observations qualify the result. Runtime observations require a worker that first checks filesystem confinement and blocked network egress; a declared surface alone cannot establish runtime behavior.
The portrait is an explanation of the feature. Operational results appear in the console itself.
Follow evidence and provenanceFrom an operation to a report
Keep the answer connected to its source.
Use the canonical server report to inspect findings and their assessment context. Exports and configured signatures carry that record forward without turning a missing observation into a successful check.