Trellix MVISION Connector https://sisapcert.stellarcyber.cloud/prod-docs/4.3.x/Configure/Connector...

Configuring Trellix MVISION Connectors

This connector allows Stellar Cyber to ingest logs from Trellix MVISION and add the records to the data lake. It
Prin
integrates with the Trellix MVISION EDR API to query for Insight events and devices. t
topi
c
 Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion
volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the
collector is exceeded.

Connector Overview: Trellix MVISION

Capabilities
• Collect: Yes
• Respond: No
• Native Alerts Mapped: No
• Runs on: DP
• Interval: Configurable

Collected Data
Content Type Index Locating Records

Devices Syslog msg_class:

Insight Events Assets (for Devices) trellix_mvision_insight_d
evices
trellix_mvision_insight_e
vents

msg_origin.source:
trellix_mvision

msg_origin.vendor:
trellix_mvision

msg_origin.category:
endpoint

Domain
N/A

Response Actions
N/A

Third Party Native Alert Integration Details

N/A

Required Credentials
• API Key, Client ID, and Client Secret

 Let us know if you find the above overview useful.

Adding a Trellix MVISION Connector

To add a Trellix MVISION connector:
1. Obtain credentials
2. Add the connector in Stellar Cyber
3. Test the connector
4. Verify ingestion

Obtaining Trellix MVISION Credentials

Before you configure the connector in Stellar Cyber, you must obtain the following Trellix MVISION credentials:
• API key
• Client ID
• Client secret
The client credentials are available in your Trellix on-boarding email. However, you can follow these steps to generate
credentials again:
1. Log in to Trellix Developer Portal  as an administrative user.
2. Navigate to Self Service | API Access Management.

3. Copy the API key, which you will need when configuring the connector in Stellar Cyber.

 Store the API key in a safe location. It cannot be retrieved later although it can be regenerated.

1 de 3 23/01/2024, 3:42 p. m.
Trellix MVISION Connector https://sisapcert.stellarcyber.cloud/prod-docs/4.3.x/Configure/Connector...

4. In the Credential Configurations section, enter your Client Type, select the required APIs and Method
Types.

5. Click Request. When the request is approved, the Create Client Credentials section appears on the page.

6. Click Generate Again to generate the client credentials.

7. Copy the Client ID and Client Secret, which you will need when configuring the connector in Stellar Cyber.

Adding the Connector in Stellar Cyber

To add a Trellix MVISION connector in Stellar Cyber:
1. Log in to Stellar Cyber.
2. Click System | Integrations | Connectors. The Connector Overview appears.

3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot
be changed after you add the connector.

4. Choose Endpoint Security from the Category drop-down.

5. Choose Trellix MVISION Endpoint Security from the Type drop-down.
6. For this connector, the supported Function is Collect, which is enabled already.
7. Enter a Name.

 This field does not accept multibyte characters.

8. Choose a Tenant Name. This identifies which tenant is allowed to use the connector.
9. Choose the device on which to run the connector.

 • Certain connectors can be run on either a Sensor or a Data Processor. The available devices
are displayed in the Run On menu. If you want to associate your collector with a sensor, you
must have configured that sensor prior to configuring the connector or you will not be able to
select it during initial configuration. If you select Data Processor, you will need to associate
the connector with a Data Analyzer profile as a separate step. That step is not required for a
sensor, which is configured with only one possible profile.
• If the device you're connecting to is on premises, we recommend you run on the local sensor.
If you're connecting to a cloud service, we recommend you run on the DP.

10. (Optional) When the Function is Collect, you can create Log Filters. For information, see Managing Log
Filters.
11. Click Next. The Configuration tab appears.

12. Enter the API Key you noted above in Obtaining Trellix MVISION Credentials.
13. Enter the Client ID you noted above.
14. Enter the Client Secret you noted above.
15. Choose the Interval (min). This is how often the logs are collected.
16. Choose the Content Type you would like to collect. The logs for Devices and Insight Events are
supported.

 The Devices content type is always required.

17. Click Next. The final confirmation tab appears.

18. Click Submit.

2 de 3 23/01/2024, 3:42 p. m.
Trellix MVISION Connector https://sisapcert.stellarcyber.cloud/prod-docs/4.3.x/Configure/Connector...

 To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data
Processor.

19. If you are adding rather than editing a connector with the Collect function enabled and you specified for it to
run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer
profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.

 • This prompt only occurs during the initial create connector process when Collect is enabled.
• Certain connectors can be run on either a Sensor or a Data Processor, and some are best run
on one versus the other. In any case, when the connector is run on a Data Processor, that
connector must be included in a Data Analyzer profile. If you leave it out of the default profile,
you must add it to another profile. You need the Administrator Root scope to add the
connector to the Data Analyzer profile. If you do not have privileges to configure Data
Analyzer profiles, a dialog displays recommending you ask your administrator to add it for
you.
• The first time you add a Collect connector to a profile, it pulls data immediately and then not
again until the scheduled interval has elapsed. If the connector configuration dialog did not
offer an option to set a specific interval, it is run every five minutes. Exceptions to this default
interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub
(continuously pulls data) connectors. The intervals for each connector are listed in the
Connector Types & Functions topic.

The Connector Overview appears.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you
entered. (The test validates only the authentication / connectivity; it does not validate data flow).
1. Click System | Integrations | Connectors. The Connector Overview appears.

2. Locate the connector that you added, or modified, or that you want to test.
3. Click Test at the right side of that row. The test runs immediately.

 Note that you may run only one test at a time.

Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful
test indicates that you entered all of the connector information correctly.
To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the
test fails, you can select the  button from the same row to review and correct issues.

 The connector status is updated every five (5) minutes. A successful test clears the connector status, but if
issues persist, the status reverts to failed after a minute.

Repeat the test as needed.

Display sample messages...

Verifying Ingestion
To verify ingestion:
1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
2. Change the Indices for the type of content you collected:
• For Insight Events, change the Indices to Syslog.
• For Devices, change the Indices to Assets.
The table immediately updates to show ingested Interflow records.

Stellar Cyber version 4.3.7 © 2023 Stellar Cyber . All rights reserved.

Support | Contact Us |   

3 de 3 23/01/2024, 3:42 p. m.