> ## Documentation Index
> Fetch the complete documentation index at: https://docs.snapsec.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Remediation Validation Runs

> Re-scan assets post-fix to confirm and verify vulnerability resolution.

> [!TIP]
>
> Fixing a vulnerability is only half the work — verifying the fix is what closes the loop.

***

## Why Remediation Validation Matters

Teams often mark vulnerabilities as *fixed* without confirming whether:

* The patch actually applied
* The vulnerable behavior is fully removed
* The issue has reappeared due to rollback or misconfigurations
* The fix introduced new regressions

Without verification, security risks silently persist.

Snapsec Vulnerability Scanner ensures every fix is validated automatically.

> [!TIP]
>
> Validate fixes instantly after engineering deploys changes

> [!TIP]
>
> Confirm patch effectiveness using targeted re-tests

> [!TIP]
>
> Detect regressions or partial fixes early

> [!TIP]
>
> Provide clear evidence for SLA closure and compliance

***

## How Snapsec Performs Validation Runs

**1. Identify Fixed Issues**

Once a vulnerability is marked as fixed in VM, Snapsec queues the asset for re-testing.

**2. Run Targeted Scans**

Only the affected endpoints, parameters, or assets are re-scanned to speed up validation.

**3. Compare Results**

Snapsec automatically checks whether the vulnerability signature or behavior still exists.

**4. Confirm or Reopen**

If resolved → marked as, Fix Verified.\
If not → the finding automatically reopens with new evidence.

***

## What Problems This Solves

> **False Closure**
>
> Avoid closing vulnerabilities that were never properly fixed.

> **Regression Risks**
>
> Catch issues that reappear after deployments or rollbacks.

> **Slow Manual Validation**
>
> Automate verification instead of spending hours re-testing findings by hand.

***

## Key Benefits for Your Security Team

> **Automated Fix Confirmation**
>
> No more manual verification — Snapsec confirms fixes instantly.

> **Evidence-Based Status Updates**
>
> Each validated fix includes logs, payloads, and signature checks.

> **Faster SLA Closure**
>
> Resolve findings without waiting on slow manual confirmations.

> **Zero Regression Gaps**
>
> Prevent reintroduced vulnerabilities from slipping through.

***

## Example Validation Findings

> [!CAUTION]
>
> A SQLi issue remains exploitable after patch → Snapsec reopens automatically.

> [!CAUTION]
>
> A missing authentication header reappears due to rollback → flagged immediately.

> [!CAUTION]
>
> A fixed XSS signature is fully removed → marked as Fix Verified with proof.

***

## What Happens After Validation

**1. Update VM Status**

Snapsec syncs results back into the VM for lifecycle accuracy.

**2. Notify Teams**

Engineers and security receive instant success or failure alerts.

**3. Generate Validation Evidence**

Full proof-of-fix is attached automatically.

**4. Feed Into Reporting**

SLA charts, compliance evidence, and closure metrics update in real time.

***

## Next Steps

> **Explore Vulnerability Scanner Capabilities**
>
> Learn how Snapsec automates detection, validation, and continuous monitoring.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.