GRC Oversight

VirusTotal

Collect file-hash, URL, and IP-reputation lookup results as read-only malware-analysis compliance evidence through the VirusTotal API v3.

Malware · File Analysis
Tier 2 generic template — runs on the HTTP / REST endpoint connector
Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

  • Read-only API inventory endpoint checks
  • Evidence assets generated through the generic HTTP connector
Read-only calls

Endpoints this template queries

The exact VirusTotal API endpoints called once connected. All read-only GET requests unless noted.

  • GET/files/<sha256-hash>
  • GET/ip_addresses/8.8.8.8
Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

  • Base URL(prefilled: https://www.virustotal.com/api/v3)
  • Endpoints (JSON)(prefilled: [ { "id": "file-report", "name": "File hash report (example lookup)", "path": "/files/<sha256-hash>" }, { "id": "ip-report", "name": "IP address report (example lookup)", "path": "/ip_addresses/8.8.8.8" } ])

Optional

  • Auth header name(prefilled: Authorization)
  • Auth header value(secret credential)
Where this evidence goes

Which frameworks this evidence supports

VirusTotal evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in VirusTotal evidence

Get a guided demo, or start by scanning any domain for free.