Skip to main content

Trellix mVision ePO Source


Trellix is a cybersecurity company that provides cloud-based security solutions for cybersecurity attacks. It provides hardware, software, and services to investigate cybersecurity attacks, protects against malicious software, and analyzes IT security risks.

mVision ePO is a key component of the Trellix security management platform, which provides unified management of endpoint, network, and data security. This can reduce incident response time, strengthen protection, simplify and automate risk and security management, and provide end-to-end network visibility and security.


This source is available in all deployments, including the Fed deployment.

Data collected

Polling IntervalData
5 minEvent ogs


Vendor configuration

The Trellix mVision ePO source requires you to provide a Client ID, Client Secret, and API key. To obtain these, follow the steps below.

  1. Log in to the Trellix Developer Portal.
  2. Go to the Self service menu and click API Access Management option.
    1. Copy API key from the API Access Management section.
    2. In the Credential Configuration section, select Events as the scope in APIs for a given Client Type.
    3. Click Request for IAM Client type approval.
    4. Once your IAM Client type is approved, generate the Client ID and Client Secret.

Source configuration

When you create a Trellix mVision ePO Source, you add it to a Hosted Collector. Before creating the source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector.

To configure a Trellix mVision ePO Source, follow the steps below:

  1. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
  2. On the Collection page, click Add Source next to a Hosted Collector.
  3. Search for and select Trellix mVision ePO.
  4. Enter a Name for the Source. The description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. (Optional) Fields. Click the +Add button to define the fields you want to associate. Each field needs a name (key) and value.
    • green check circle.png A green circle with a check mark is shown when the field exists in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored, known as dropped.
  7. Enter the Client ID of your Trellix platform.
  8. Enter the Client Secret of your Trellix platform.
  9. Enter the API Key for authorization collected from the Trellix platform.
  10. (Optional) The Polling Interval is set for 5 minutes by default. You can adjust it based on your needs. This sets how often the Source checks for new data.
  11. When you are finished configuring the Source, click Save.

Metadata field

_siemParser/Parsers/System/Trellix/Trellix MVision EPOSet when Forward To SIEM is checked.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for more details.

schemaRefJSON Object{"type":"Trellix mVision ePO"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Configuration Object

nameStringYesnullType a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source."mySource"
descriptionStringNonullType a description of the source."Testing source"
categoryStringNonullType a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details."mySource/test"
fieldsJSON ObjectNonullJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.{"_siemForward": false, "fieldA": "valueA"}
apiKeyStringYesnullAPI key used for Authorization.
clientIDStringYesnullClient ID of your account.
clientSecretStringYesnullClient Secret of your account.
pollingIntervalIntegerNo5 minutesChoose how often the Source checks for new data (In minutes).

JSON example

"api.version": "v1",
"source": {
"config": {
"name": "Trellix",
"clientID": "xxxxxxxxxxxxxx",
"clientSecret": "******",
"apiKey": "*******",
"pollingInterval": 5
"type": "Trellix mVision ePO"
"sourceType": "Universal"

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "trellix_source" {
collector_id =
schema_ref = {
type = "Trellix"
config = jsonencode({
"name": "Trellix",
"clientID": "xxxxxxxxxxxxxx",
"clientSecret": "******",
"apiKey": "*******",
"pollingInterval": 5
resource "sumologic_collector" "collector" {
name = "my-collector"
description = "Just testing this"

Download example



Click here for more information about Cloud-to-Cloud sources.

Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.