Compliance Integrations / Vanta

Vanta integration: SOC 2 vulnerability scanning evidence

Push security findings to Vanta as compliance evidence. OAuth connection, continuous sync every few minutes, Vanta-owned tests.

Overview

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.

Prerequisites

  • An AttackerView account. The 14-day trial includes the Vanta sync. To keep it after the trial you need the Hunter plan
  • A Vanta account in the US, EU, or Australia region with permission to connect integrations. Vanta Government is not supported.

Setup

Vanta uses OAuth, so you never share API keys or secrets. A workspace admin must authorize the connection. Members can read its status.

Connect from AttackerView

  1. Go to Settings in your AttackerView dashboard
  2. Under Compliance Integrations, select the region you use to sign in to Vanta, then click Connect
  3. You'll be redirected to Vanta's authorization page
  4. Review the permissions and click Allow
  5. You'll be redirected back to AttackerView. Authorization is saved and the first background sync is scheduled.

Connect from Vanta

You can also start the connection from Vanta's side:

  1. In Vanta, go to Integrations
  2. Search for AttackerView under the Vulnerability Scanner category
  3. Click Connect and follow the authorization flow

Both paths end the same way: an OAuth handshake that securely links your accounts.

What gets synced

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.

Vulnerable Components

One per domain. Represents the asset being scanned.

FieldValue
Display nameYour domain (e.g., example.com)
Component versionLatest completed scan timestamp, or empty if unknown
Collected timestampTimestamp when the resource state was collected
SeverityHighest severity across open findings for this domain
LinkDeep link to the domain in AttackerView

API Endpoint Vulnerabilities

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.

FieldValue
TitleFinding title (e.g., "Exposed configuration file")
SeverityNumeric score (0-10) mapped from AttackerView’s assessed severity
HTTP methodObserved request method, or GET compatibility fallback if unknown
URLThe affected endpoint or domain URL
DescriptionTechnical evidence from the scan
RemediationPlatform-specific fix steps when available (e.g., Cloudflare, Nginx, Apache), with a link to full guidance
LinkDeep link to the specific finding in AttackerView

Package Vulnerabilities

One per CVE finding. Known software vulnerabilities with CVE identifiers detected in your tech stack.

FieldValue
Package nameThe affected software (e.g., "Apache HTTP Server")
Package versionDetected version, or empty if unknown or redacted
CVE IDCVE identifier (e.g., CVE-2021-41773)
SeveritySame severity mapping as endpoint vulnerabilities (see below)
CVSS scorePublished CVSS score when available (from NVD, or from Wordfence for WordPress plugins)
ResolvableWhether a fix version exists
ReachableWhether the vulnerability was actively confirmed exploitable (verified CVEs only)
LinkDeep 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.

Sync behavior

  • An independent worker checks due work after each cycle, with a 30-second delay. The normal next attempt is scheduled three minutes after completion; provider backoff, worker availability, and retries can extend this.
  • Each sync sends the complete state of all your domains and all open findings. Vanta replaces its previous data entirely.
  • When a finding is fixed and no longer in the sync, Vanta automatically marks it as remediated
  • Risk-accepted findings are excluded (they represent acknowledged risks, not open vulnerabilities)
  • The sync is tenant-wide: all domains across your account are included in every sync, regardless of which domain was scanned most recently

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.

Severity mapping

AttackerView sends numeric severity on a 0-10 scale. Published CVSS scores are used when available; the categorical fallback is:

AttackerView severityFallback severity sentVanta classification
Critical9.5Critical
High7.5High
Medium5.0Medium
Low2.5Low
Info0.5Low

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.

SLA tracking

Vanta calculates its own remediation SLAs. You don't need to configure anything on the AttackerView side.

  • The SLA clock starts when Vanta first sees a vulnerability (the first sync that includes it)
  • Deadlines depend on your Vanta vulnerability settings. Your Vanta admin owns the SLA configuration.
  • When AttackerView stops sending a finding (because it's been fixed), Vanta marks it as remediated and records whether it met the SLA deadline
  • Vanta sends email alerts as SLA deadlines approach

What your auditor sees

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.

Disconnecting

You can disconnect from either side:

  • From AttackerView: Go to Settings and click "Disconnect" next to the Vanta integration. This immediately removes the local connector and stops syncing. Remote token revocation is queued; Settings shows pending work until Vanta confirms completion.
  • From Vanta: Remove AttackerView from Vanta's Integrations page. AttackerView attempts token recovery on the next sync. A supported permanent grant failure shows Reconnect required; your enabled preference is preserved.

Vulnerability data already in Vanta is retained per Vanta's data retention policies. Reconnecting starts a fresh sync of your current state.

Troubleshooting

"Connection expired. Please reconnect."

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.

Findings aren't appearing in Vanta

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

Some findings are missing

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 shows different severity than AttackerView

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.

FAQ

Can I use Vanta and Drata at the same time?

Yes. Each integration operates independently. The same findings appear in both platforms.

What happens if I downgrade from Hunter?

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.

Does Vanta send data back to AttackerView?

No. The integration is one-directional. AttackerView pushes findings to Vanta. Vanta does not send webhooks or data back.

How do I know the sync is working?

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.

See also