What this solves
Security scanner reports can contain repeated instances, tool-specific risk labels, and uncertain control mappings that are difficult to manage as client-ready findings.
How voiqq helps
Web Security Auto-populate parses supported OWASP ZAP output as untrusted data, normalizes alerts into ordinary voiqq records, retains technical evidence, and suggests ASVS mappings for professional review.
Before you begin
- An authorized Web Application Security assessment
- A supported ZAP JSON report
- The correct ASVS Library and project scope
- A sanitized report without credentials or unnecessary personal data
Step-by-step
- Open Auto-populate in the Web Security project
- Upload the supported ZAP report
- Review the parsed alerts, instances, and warnings
- Confirm or change requirement mappings
- Accept legitimate candidates into the project
- Validate severity, exploit context, remediation, and retest status
Check your result
- Duplicate alerts are grouped deterministically
- Endpoints and parameters remain attached to the correct record
- Risk and confidence are not mistaken for final professional severity
- Accepted findings use the normal drawer, assignment, and report workflow