AI Enrichment
AI Enrichment adds context to a finding so the person fixing it does not have to research it first: the root cause, step-by-step remediation, a code example and references. It runs automatically on critical and high findings and on request for the rest.
What AI Enrichment adds to a finding
A short explanation of why the vulnerability exists.
Numbered steps to fix it, each with a title and detail.
An example of the fix in the relevant language, where one applies.
Links to OWASP, CWE and NVD material on the issue.
Hints from Spoorder's vulnerability knowledge base for the tech stack detected on your target.
An AI-written summary of a set of findings for people who do not read scanner output.
Enrichment follows the finding
- 1
Finding created
A scan engine records a new finding.
- 2
Automatic for critical and high
Critical and high severity findings are enriched in the background. Lower severities wait until you ask.
- 3
AI writes the context
The model receives the vulnerability type, endpoint, CVE and tech stack, and returns the root cause, steps, example and references.
- 4
Shown on the finding
The enrichment appears on the finding. For a medium or low finding, request it from the finding page.
{
"title": "SQL Injection - /api/orders",
"enrichment": {
"root_cause": "The id parameter is concatenated into a SQL statement.",
"remediation_steps": [
{ "step_number": 1, "title": "Use a parameterised query", "detail": "Pass id as a bound parameter." }
],
"code_language": "typescript",
"references": [{ "title": "SQL Injection", "source": "OWASP" }]
}
}Spoorder AI Enrichment vs manual research
| Criterion | Spoorder | manual research |
|---|---|---|
| Root cause | Written for the specific finding | A generic CVE description |
| Remediation | Numbered steps with a code example | A reference link |
| Timing | Automatic for critical and high findings | When someone has time |
| Stack awareness | Uses the tech stack detected on the target | Generic advice |
Does AI Enrichment run on every finding?
It runs automatically on critical and high severity findings, from any engine. For medium, low and informational findings you request it from the finding page.
What does the AI see?
The vulnerability type, the scanner that found it, the endpoint, the CVE ID if there is one and the tech stack detected on the target.
Can I rely on the output without checking it?
No. It is machine-generated guidance. Treat it as a starting point and review it before you act on it.
How is this different from AI Remediation?
Enrichment adds context to a finding. AI Remediation generates a fix to apply, with a confidence level and a verification command, and counts against your monthly AI fix allowance.
Start scanning
Start with a free health check. AI features are part of the paid plans, which have a 14-day trial on Builder, Pro and Scale.