Findings and remediation

Read the complete finding

Start with severity, classification, and confidence, then inspect the evidence and recommendation. A title or HTTP status alone is not enough to establish a vulnerability.

Focus the review

Filter findings by audit, severity, module, status, or search text. Group related occurrences by rule and use the stable fingerprint to distinguish a repeated issue from a new location.

Fix and verify

• Address the root cause rather than only the displayed symptom.
• Mark the finding solved when the change is ready for verification.
• Rerun comparable coverage and confirm that the evidence no longer appears.

Use AI Fix as a handoff

AI Fix prepares a structured remediation prompt for supported coding tools. The prompt carries the rule, evidence, affected area, and safe constraints so the coding assistant can start with the right context.

Review the proposed patch and rerun VICE. A generated fix is not proof that the vulnerability is resolved.

Protect sensitive evidence

VICE masks secrets and sensitive response values in reports and logs. If a finding indicates that a secret was exposed, rotate it. Redaction protects the report, not the original system.