Triage
Confirm the finding, exposure, asset owner, exploit context, and business relevance.
SolrSunrise workflow
Vulnerability remediation workflow from signal to verified closure.
A remediation workflow turns a vulnerability signal into owned work with evidence, recommended action, status, retest request, and closure proof.
What this page covers
Remediation
Assign owners and track notes, due dates, blockers, and decision rationale.
Retest
Verify closure or document accepted risk so the issue does not disappear into a queue.
Workflow steps
Triage exposure
Confirm the affected asset, scope, severity, exploitability, and evidence quality.
Assign owner
Route work to the person or team that can make the change.
Preserve evidence
Keep screenshots, scanner references, URLs, timestamps, and decision notes.
Verify closure
Request retest, capture result, and mark closure only when risk is actually resolved or accepted.
Frequently asked questions
How is SolrSunrise different from scanner-only tools?
Scanner-only tools often stop at detection and reporting. SolrSunrise emphasizes the execution layer after detection: priority, owner, evidence, remediation state, retest request, and verified closure.
Who is this for?
SolrSunrise is for small security teams, IT operators, and MSSPs that need practical exposure monitoring and remediation workflow without enterprise-platform drag.
Does SolrSunrise require authorized scope?
Yes. SolrSunrise is framed for authorized defensive monitoring. Asset scope, ownership, and customer authorization should be clear before monitoring or scanning activity.
Request early access
Use SolrSunrise to move from exposed signal to prioritized, assigned, evidenced, and verified remediation work.
Request early access