Compliance Integrations

Automatically push security findings to your compliance platform. No manual evidence collection.

How it works

AttackerView integrates with compliance platforms to automatically deliver vulnerability scan results as compliance evidence. Vanta receives the complete workspace state in its background sync. Drata receives evidence after scans and during its initial sync.

Your SOC 2, ISO 27001, PCI DSS (supporting evidence), and HIPAA evidence stays current without anyone copying screenshots or uploading PDFs. Vanta owns the tests, control associations, and audit outcomes evaluated from received resources. These exports support compliance reviews; they are not certification.

You can connect integrations in Settings. The 14-day trial includes them. After it they need Hunter.

What gets synced

Both integrations send the same core data, formatted for each platform:

  • Open findings with title, severity, evidence, and remediation links
  • Severity levels (critical, high, medium, low) — Vanta receives numeric severity on a 0-10 scale
  • Evidence for compliance review. Drata receives control mappings; Vanta evaluates its own tests from the synced base resources.
  • Deep links back to AttackerView for each finding's full detail and remediation guidance

When a finding is fixed, Vanta drops it on the next sync. Drata gets a new evidence file listing only the findings still open after the next scan, and files already in Drata stay there. If a domain has no open findings left, no new file is uploaded.

Supported frameworks

AttackerView maps findings to relevant controls in supported compliance frameworks:

FrameworkExample controls
SOC 2CC6.1, CC6.3, CC6.6, CC6.7, CC6.8, CC7.1
ISO 27001A.5.14, A.8.8, A.8.9, A.8.24
PCI DSS4.2.1, 6.2.4, 6.3.3
HIPAA164.312(a)(1), 164.312(e)(1)

AttackerView reports include these mappings. Drata receives mapped evidence; Vanta owns its test and control associations. The Vanta payload does not carry control tags.

Available integrations

Quick comparison

VantaDrata
Auth methodOAuth (no keys to manage)API key
Sync frequencyEvery few minutes (background)Initial sync on connect, then on scan completion
Sync scopeAll domains + findings (full state)Per domain (after each scan)
SLA trackingBuilt-in (Vanta calculates)Via Drata's control monitoring
Regional supportGlobal (single endpoint)US, EU, APAC

You can connect both at the same time. Each operates independently.

Tips

  • Enable continuous monitoring on your domains so compliance evidence stays fresh between manual scans.
  • Use the compliance evidence report for a point-in-time snapshot that's useful alongside live integrations.
  • If your plan no longer includes integrations, syncing pauses and saved connections remain visible. Workspace admins can disable or disconnect them on every plan. Restored access resumes enabled connections; disabled connections stay disabled.
  • Integration errors are shown in Settings. If a sync fails, AttackerView retries on the next cycle.