Understanding Results

Anatomy of a finding

Each finding in a scan result contains the following fields:

Status values

The status field tells you how certain the finding is:

• vulnerable — evidence clearly confirms the vulnerability
• warning — suspicious behavior detected, manual review recommended
• info — informational observation, not necessarily a risk
• secure — check passed, no issue found

Reading the evidence

The Evidence block is the most important field when triaging. It shows the exact request/response data that triggered the finding. For example:

Response headers received:
  Content-Type: text/html; charset=utf-8
  Server: nginx/1.24.0

Missing headers:
  X-Frame-Options
  X-Content-Type-Options
  Content-Security-Policy

Endpoint: GET https://example.com/search
Parameter: q
Payload: ' OR '1'='1' --
Matched SQL error pattern: you have an error in your sql syntax

Confidence levels

• confirmed — unambiguous evidence (e.g. SQL error in response)
• possible — strong indicator but not 100% certain (e.g. timing anomaly)
• tentative — heuristic match, manual verification needed

CVSS scores

Where available, findings include a CVSS 3.1 base score from 0.0 to 10.0. Use this to prioritize remediation:

Prioritizing remediation

Recommended order of action:

1. Fix all CRITICAL findings immediately
2. Schedule HIGH fixes within the current sprint
3. Address MEDIUM in the next planned release
4. Track LOW and INFO in your backlog

Triage queue

The Triage tab shows all unreviewed findings across your scans. For each finding you can: mark it as a False Positive (permanently dismiss it from the active count), accept it as a Known Risk (acknowledge without fixing), or add a Note for your team. Bulk-select to process multiple findings at once.

Accepted and false-positive findings are excluded from the risk score but remain visible in the scan history for audit trail purposes.

MTTR (Mean Time to Remediate)

Shieldome tracks when each finding was first detected and when it was resolved. The MTTR widget in the scan summary shows your average remediation time across all fixed vulnerabilities. Use this to measure the effectiveness of your security program over time.

Global search

Press g (or click the Search icon in the navigation) to open the global search panel. Search across all your completed scans by finding title, target URL, or severity. Results link directly to the scan and finding. Use the severity filter to narrow results to Critical or High findings only.

Notes & annotations

Every finding supports free-text notes. Add context for your team — "already tracked in Jira", "fixed in next release", "client accepted this risk". Notes appear in PDF reports and are visible to all team members in your organization.