Compliance Integrations / Vanta
Push security findings to Vanta as compliance evidence. OAuth connection, continuous sync every few minutes, Vanta-owned tests.
AttackerView connects to Vanta as a vulnerability scanning integration. Once connected, AttackerView automatically syncs all your security findings to Vanta every few minutes. Vanta receives base vulnerability resources and evaluates its own tests and control associations. Successful resource sync does not guarantee a particular compliance test passes.
The integration is one-directional: AttackerView pushes data to Vanta. Vanta handles SLA tracking, remediation deadlines, and audit evidence from there.
Vanta uses OAuth, so you never share API keys or secrets. A workspace admin must authorize the connection. Members can read its status.
You can also start the connection from Vanta's side:
Both paths end the same way: an OAuth handshake that securely links your accounts.
AttackerView syncs three resource types to Vanta:
Detected package facts and request methods come from structured scan observations. Historical unknown methods use GET as a compatibility value, including DNS and TLS findings with no HTTP request. Unknown package versions are empty. Unverified domains have these details redacted. Secret-containing finding details are withheld from compliance exports; open the finding in AttackerView to review them.
A newly connected workspace with no domains sends an empty full state. Later scans populate the same resources without requiring a reconnect.
One per domain. Represents the asset being scanned.
| Field | Value |
|---|---|
| Display name | Your domain (e.g., example.com) |
| Component version | Latest completed scan timestamp, or empty if unknown |
| Collected timestamp | Timestamp when the resource state was collected |
| Severity | Highest severity across open findings for this domain |
| Link | Deep link to the domain in AttackerView |
One per non-CVE finding. Open non-CVE security findings, such as exposed files or confirmed application weaknesses. Posture-only security-header checks are excluded.
| Field | Value |
|---|---|
| Title | Finding title (e.g., "Exposed configuration file") |
| Severity | Numeric score (0-10) mapped from AttackerView’s assessed severity |
| HTTP method | Observed request method, or GET compatibility fallback if unknown |
| URL | The affected endpoint or domain URL |
| Description | Technical evidence from the scan |
| Remediation | Platform-specific fix steps when available (e.g., Cloudflare, Nginx, Apache), with a link to full guidance |
| Link | Deep link to the specific finding in AttackerView |
One per CVE finding. Known software vulnerabilities with CVE identifiers detected in your tech stack.
| Field | Value |
|---|---|
| Package name | The affected software (e.g., "Apache HTTP Server") |
| Package version | Detected version, or empty if unknown or redacted |
| CVE ID | CVE identifier (e.g., CVE-2021-41773) |
| Severity | Same severity mapping as endpoint vulnerabilities (see below) |
| CVSS score | Published CVSS score when available (from NVD, or from Wordfence for WordPress plugins) |
| Resolvable | Whether a fix version exists |
| Reachable | Whether the vulnerability was actively confirmed exploitable (verified CVEs only) |
| Link | Deep link to the specific finding in AttackerView |
Domains with zero open findings are still synced as components (severity 0). This keeps your asset inventory accurate in Vanta even when everything is clean.
A sync is recorded as successful only after all three resource types complete. Settings shows the last completed sync, any error, and the next scheduled attempt.
AttackerView sends numeric severity on a 0-10 scale. Published CVSS scores are used when available; the categorical fallback is:
| AttackerView severity | Fallback severity sent | Vanta classification |
|---|---|---|
| Critical | 9.5 | Critical |
| High | 7.5 | High |
| Medium | 5.0 | Medium |
| Low | 2.5 | Low |
| Info | 0.5 | Low |
For CVE findings with a published CVSS score (from NVD or Wordfence), the score is also sent in the separate CVSS field. A categorical fallback is not a calculated CVSS score.
Vanta calculates its own remediation SLAs. You don't need to configure anything on the AttackerView side.
Vanta stores the synced components and endpoint/package vulnerabilities. Vanta owns the tests, control associations, remediation timelines, and audit exports built from these resources.
Our acceptance sandbox shows AttackerView connected with a Vulnerabilities capability and at least four custom severity tests linked to SOC 2. The built-in scanner-link test still reports that no scanner is connected. Public Vanta documentation does not explain that custom mapping, so we do not promise a test count or that resource sync passes the scanner-link test.
Each vulnerability links back to AttackerView for the finding detail and remediation guidance. Review the relevant Vanta tests with your Vanta admin before relying on them as compliance evidence.
For what auditors expect from vulnerability scanning under CC7.1, see what SOC 2 auditors ask for.
You can disconnect from either side:
Vulnerability data already in Vanta is retained per Vanta's data retention policies. Reconnecting starts a fresh sync of your current state.
When Vanta reports a permanent grant failure, automatic grant retries stop. A workspace admin can click "Reconnect" to re-authorize. A successful authorization clears the prior sync health and schedules a new attempt.
The sync runs every few minutes. Check the "Last synced" timestamp in Settings. If there's an error message, the sync may have failed. Common causes: expired tokens (reconnect), or no open findings to sync (expected if everything is clean).
Only findings with open status are synced. Risk-accepted findings and fixed findings are excluded. If a finding was recently fixed, it will disappear from Vanta on the next sync.
Vanta maps the severity score we send into its own severity buckets. The boundaries may differ slightly from our label-based severity. For CVE findings, Vanta also receives the published CVSS score (from NVD, or from Wordfence for WordPress plugins) in a separate field, which may differ from AttackerView's categorical label.
Yes. Each integration operates independently. The same findings appear in both platforms.
Exports require Hunter for the effective workspace, including paid members or a billing parent. If that eligibility expires, syncing pauses and your enabled preference is preserved. Members can still read status and admins can disconnect. Restored eligibility resumes enabled connectors; user-disabled connectors stay disabled.
No. The integration is one-directional. AttackerView pushes findings to Vanta. Vanta does not send webhooks or data back.
Check Settings for the last sync timestamp and any error messages. In Vanta, you can verify by checking the Vulnerabilities page or the relevant test evidence configured in your Vanta workspace.