Send data
Vanta can receive multiple types of data. You'll need to choose:
At a minimum, you must send us the
UserAccountresource.
Resources
A resource is a piece of data (formatted as JSON) that describes an asset, such as a computer or user account. Resources power a vast range of product functionality in Vanta, including:
- Automated monitors that verify security and provide compliance evidence (e.g. "every computer is encrypted")
- Product pages such as Computers, Inventory, Access or People
Each resource has a "resource type" that specifies the exact properties Vanta needs to power functionality. Simply send data matching that schema, and Vanta takes care of the rest.
Sending resources not only reduces the amount of work customers have to spend collecting compliance evidence, but also lets them monitor the security of your tool's assets in Vanta.
Supported resource types
You don't have to send us every resource type - just the subset that make sense for your product. For example, if your product is a task tracker, you'd likely only send
UserAccountsandSecurityTasks.
Resource type | Description / functionality powered in Vanta | Recommended for |
|---|---|---|
UserAccount (info) | Accounts of users of your tool. Vanta will:
| All partners |
MacOS | Employee or contractor MacOS computers. Vanta will:
| MDMs |
Windows | Same as MacOsUserComputer | MDMs |
Secret | Secrets used to access applications or infrastructure. Vanta will:
| Secret storage |
SecurityTask | Security-relevant tasks or followups. Vanta will:
|
|
UserSecurity | Evidence of user security trainings. Vanta will:
| Security training providers |
VulnerableComponent | The asset that is vulnerable. A VulnerableComponent must be synced before any of the below vulnerabilities are synced. The vulnerability types below reference their affected component using the uniqueId of the component. | Vulnerability Scanners |
ApiEndpoint | Known vulnerabilities detected in API endpoints. Vanta will:
| Vulnerability Scanners |
PackageVulnerability | Known vulnerabilities detected in package dependencies. Vanta will:
| Vulnerability Scanners |
StaticAnalysisCode | Known vulnerabilities detected from static code analysis. Vanta will:
| Vulnerability Scanners |
BackgroundCheck | Employee background check statuses. Vanta will:
|
|
Documents
A document is a file - such as a PDF or CSV - that you can upload to Vanta on your customers' behalf. Uploading these documents reduces the amount of time customers have to spend gathering compliance evidence from your tool when preparing for an audit.
All documents are associated with an "Evidence request", which defines what the document is providing evidence for. Each evidence request has a list of compliance controls that it is mapped to.
For example:
- If you're an access review tool, you should upload documents to the Proof of completed access reviews evidence request.
- If you're an incident management tool, you should upload documents to the Incident report or root cause analysis evidence request.
- If you're a tool for handling GDPR data deletion requests, you should upload documents to the Deletion requests & responses evidence request.
You are responsible for choosing the evidence requests to upload documents for. The best place to view all evidence requests is on the Documents page. You can also view all compliance controls on the Compliance page, and see which evidence requests are listed under each control.
To decide which evidence requests to upload documents for, visit the Documents page. If you're having trouble figuring out which documents to upload, contact us.
Updated 12 days ago