Authentication
TrendAI Vision One™ uses token-based authentication to ensure that only legitimate accounts can use the APIs. Each authentication token is associated with a role that determines the actions the user can perform.
To access resources, requests must contain an authorization header with an authentication token. The following is an example of a request with a valid authorization header.
GET /v3.0/workbench/alerts HTTP/1.1
Authorization: Bearer <your authentication token>
For more information about bearer token usage, see https://tools.ietf.org/html/rfc6750 .
Account Role Permissions
Each API method requires a specific set of access permissions. Access permissions are enabled on the TrendAI Vision One™ console.
The following table outlines the access permissions to apps and features needed to use the TrendAI Vision One™ public API.
|
API category |
Account role permissions required |
|
|---|---|---|
|
App |
Permissions |
|
|
Accounts |
User Accounts |
|
|
User Roles |
|
|
|
Alerts / Workbench |
Workbench |
|
|
Detection Model Management |
|
|
|
Audit Logs |
Audit Logs |
|
|
Connected Products |
Product Connector |
|
|
Notifications |
Alert Notifications |
|
|
Observed Attack Techniques |
Observed Attack Techniques |
|
|
Response Actions |
Response Management |
|
|
Suspicious Object Management |
|
|
|
Single Sign-On |
Single Sign-On |
|
|
Search |
Search |
|
|
Endpoint Inventory |
|
|
|
SIEM |
Third-party Integration |
|
|
Threat Intelligence |
Suspicious Object Management |
|
|
Intelligence Feeds |
|
|
|
Sandbox Analysis |
|
|
|
Risk Insights |
Reports |
|
For the complete TrendAI Vision One™ API documentation, visit the TrendAI Vision One™ Automation Center.
