finding-interpreter

To translate raw security scan output into plain language findings, process structured JSON from network and web scanners to generate interpreted-findings.json. This output file maps technical details like CVSS and CVE severities into clear business impact statements and actionable remediation steps.

Mapping CVSS and CVE severities to business impact involves analyzing raw security scan JSON and converting technical vulnerabilities into clear statements of what is wrong and what it means for the business. This translation removes jargon and focuses on safe, actionable next steps.

Yes, you can generate tier-aware remediation guidance by producing different output levels based on client support tiers. This includes Watchman explanations for awareness and Sentinel outputs with specific remediation steps, while recommending who should fix the issues.

Detecting recurring vulnerabilities uses client memory integration to consult client history files during scan interpretation. This mechanism identifies repeated findings across scans and automatically escalates the language used in the plain-language findings to highlight persistent issues.

Yes, interpreting security scans requires structured JSON input. The process consumes raw-output.json files generated by network and web scanners, along with client memory files, to accurately map technical severities to business impact and produce verifiable remediation guidance.

Low-confidence vulnerabilities are handled during scan interpretation by applying safety-first recommendations that bound remediation to generic, verifiable steps. The interpreted-findings.json output explicitly flags these items with a needs_human_review status for manual verification.