Every finding comes with evidence and a fix path.

A finding without context is noise. Every issue Deepinfo surfaces includes evidence (the raw scan data that detected it), reproduction steps your team can follow, and a clear remediation path. Issues flow through a nine-state lifecycle so the audit trail is always exportable.

WHAT THIS DOES

Findings your team can actually act on.

Each detected issue carries a structured payload: severity, evidence (the raw observable that triggered detection), reproduction steps where applicable, suggested remediation actions, and links to relevant compliance framework controls. The goal is that whoever picks up the issue can act without needing to re-investigate it.

Issues flow through a nine-state lifecycle: Newly Detected → Reappeared → Unresolved → Marked as Resolved → Verified Resolved, plus side states for Risk Accepted, Ignored, Marked as False Positive, and Not Applicable. Every state transition is logged with user, timestamp, and optional comment. The audit trail is exportable for compliance audits, reviews, and incident retrospectives.

HOW IT WORKS

Three mechanics that make remediation actionable.

Evidence travels with the issue. Reproduction steps are issue-type-specific. State transitions are tracked.

Evidence with every finding.

The raw scan data that triggered detection is attached to the issue. SSL configuration output, HTTP response headers, port scan results, web technology fingerprints. Your team doesn't have to re-run scans to verify; the evidence is already there.

Reproduction steps and fix guidance.

For known issue patterns (misconfigured TLS, missing security headers, exposed services, common CVEs), each issue carries reproduction steps your team can follow and suggested remediation actions. Not boilerplate. Issue-type-specific.

Nine-state issue lifecycle.

Newly Detected, Reappeared, Unresolved, Marked as Resolved, Verified Resolved, Risk Accepted, Ignored, Marked as False Positive, Not Applicable. Binary "open / closed" loses critical information; the nine-state lifecycle preserves the full story per issue.

WHAT IT SURFACES

What you'll find in each issue's detail view.

Severity

Critical / High / Medium / Low / Info.

Detection evidence

Raw scan output that triggered the finding.

Asset

The asset the issue was found on, with link to asset detail.

Issue type

E.g., "Weak TLS cipher suite", "Expired SSL certificate", "CVE-YYYY-NNNNN detected".

Compliance mappings

OWASP, PCI, HIPAA, CWE, CAPEC, WASC frameworks.

State

Position in the nine-state lifecycle, with full transition history.

Suggested remediation

Issue-type-specific, where applicable.

EPSS + CISA KEV signal

For CVE-class issues.

PART OF EASM

Remediation closes the loop the rest of EASM opens.

Smart Asset Discovery finds the assets. Continuous Scanning surfaces the data. Comprehensive Risk Detection classifies issues. Remediation with Actionable Insights closes the loop, turning detected risk into work your team can prioritize, do, and prove was done. Complete Risk Scoring rolls everything up. The five capabilities are one workflow.

← Back to EASM

“Findings without evidence used to bounce back from engineering with we couldn't reproduce this. Every Deepinfo finding includes the raw scan data, the reproduction steps, and a remediation path. Tickets close faster because there's nothing to argue about.”

— Vulnerability Manager, Industrial Conglomerate
SEE THE WORKFLOW

See how findings flow from detected to verified resolved.

Book a demo. We'll walk through the nine-state lifecycle with real findings on your domain.

Request a demo