Documentation

Getting Started With Vulnify

Pick the right entry point, run your first workflow, and understand what to do after the first result.

Who This Topic Is For

Security-conscious teams and operators starting with Vulnify for the first time.

Before You Start

Use this checklist to make sure the workflow guidance applies cleanly to your current task.

A public target URL that you own or are authorized to assess.
A decision on whether you need a focused public tool result or a saved account workflow.
Clarity on whether your immediate goal is rapid validation or broader ongoing coverage.

Step-By-Step Guidance

Follow these steps in order for a reliable and repeatable outcome.

Choose your workflow entry point.
Use a focused public tool when you need one category-specific answer, use the Run All Tools workflow when you want a one-domain tool suite result with generated artifacts, and use the dashboard flow when you need saved history, recurring follow-through, and broader account-backed continuity.
Set scan depth based on risk and urgency.
Quick is best for rapid baseline visibility. Standard is the default for production checks.
Deep and Comprehensive are better when higher release risk or stronger validation confidence is required.
Run and review findings with remediation context.
Treat the result as a workflow output, not a score alone. Use finding details and remediation guidance to prioritize what gets fixed first.
Move into repeatable follow-through.
When one-off checks are no longer enough, move into scheduled scans, broader platform workflows, and supporting guides/fix pages so validation remains repeatable.

Validation Checklist

Use this checklist to confirm the workflow was completed correctly.

The selected workflow matches the scope of the question being answered.
Scan depth aligns with release risk and required confidence level.
At least one remediation action is identified from real findings.
A next scan or follow-up review point is defined.

Common Problems And Fixes

If something does not match expectation, check these common failure modes first.

Choosing a depth that is too shallow for the situation

If findings are too limited for launch or audit confidence, move from Quick to Standard or above and rerun for broader coverage.

Treating score output as final decision

Use score direction for trend awareness, but prioritize remediation decisions using the specific findings and their risk context.

No follow-up plan after first scan

Create a repeat cadence with scheduled scans or documented rerun criteria so coverage does not degrade after the first pass.

Use these links to continue your workflow without losing context.