> ## 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.

# Frequently Asked Questions (FAQ)

> Answers to frequently asked questions regarding deployment, scanning safety, licensing, and compliance.

### General & Architecture

> [accordion] Does Snapsec store sensitive customer vulnerability data in the public cloud?
>
> In our Cloud SaaS edition, tenant data is encrypted at rest with dedicated AES-256 keys and isolated schemas. For organizations with strict data residency requirements, our **On-Premises** and **Air-Gapped** editions keep 100% of data within your network perimeter.

> [accordion] How does Snapsec differ from traditional vulnerability scanners?
>
> Traditional scanners produce noisy, point-in-time lists of CVEs with high false-positive rates. Snapsec combines external discovery (ASM), dynamic asset context (AIM), continuous multi-vector scanning, and autonomous AI pentesting to provide verified, exploitable proof-of-concepts scored by business risk (TrueRisk™).

> [accordion] Will AI Pentesting disrupt our production environments?
>
> Snapsec AI Pentesting includes strict safety guardrails: rate limiting, non-destructive payloads, continuous target health checks, and optional human-in-the-loop approvals before executing state-changing exploit paths.

> [accordion] How often are threat feeds and CVE databases updated?
>
> In Cloud SaaS and connected On-Premises editions, vulnerability feeds (CVE/NVD, EPSS, CISA KEV) update continuously every 6 hours. In Air-Gapped environments, feeds are updated via offline sync packages.


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