How Epiphany Interacts With the Trend Micro Cloud One API
Required API Calls
Call 1: GET List Computers
Resource: https://workload.{region}.cloudone.trendmicro.com/api/computers
Headers: <N/A>
Body: <N/A>
Call 2: GET List IP lists
Resource: https://workload.{region}.cloudone.trendmicro.com/api/iplists
Headers: <N/A>
Body: <N/A>
Call 3: GET MAC Lists
Resource: https://workload.{region}.cloudone.trendmicro.com/api/maclists
Headers: <N/A>
Body: <N/A>
Call 4: GET List Application Types
Resource: https://workload.{region}.cloudone.trendmicro.com/api/applicationtypes
Headers: <N/A>
Body: <N/A>
Call 5: GET List Intrusion Prevention Rules
Resource: https://workload.{region}.cloudone.trendmicro.com/api/intrusionpreventionrules
Headers: <N/A>
Body: <N/A>
Call 6: GET List Software Inventories
Resource: https://workload.{region}.cloudone.trendmicro.com/api/softwareinventories
Headers: <N/A>
Body: <N/A>
Call 7: Get List Software Inventory Items
Resource: https://workload.{region}.cloudone.trendmicro.com/api/softwareinventories/{softwareInventoryID}/items
Headers: <N/A>
Body: <N/A>
Other API Calls
Call 1: GET List device firewall rules
Resource: https://workload.{region}.cloudone.trendmicro.com/api/computers/{computerID}/firewall/rules
Headers: <N/A>
Body : <N/A>
Call 2: GET List firewall rules
Resource: https://workload.{region}.cloudone.trendmicro.com/api/firewallrules
Headers:<N/A>
Body: <N/A>
Call 3: GET List Anti-Malware Configurations
Resource: https://workload.{region}.cloudone.trendmicro.com/api/antimalwareconfigurations
Headers: <N/A>
Body: <N/A>
Export Format
These calls will be stored in a JSON format and transmitted through the rest of the Epiphany workflow to derive endpoint protection data points within the larger data models.
Last updated