Configuring Malwarebytes OneView Connectors

This connector allows Stellar Cyber to ingest logs from Malwarebytes OneView and add the records to the data lake. This connector integrates with the OneView API to query detections and endpoints. It collects assets and detections (endpoint IDs and IP events) from all sites that the API client ID and API Secret have permissions to access.

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: Malwarebytes OneView

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

Detections

Endpoints

Syslog

Assets (for Endpoints)

msg_class:

malwarebytes_oneview_detection

malwarebytes_oneview_endpoint

msg_origin.source:

malwarebytes_oneview

msg_origin.vendor:

malwarebytes

msg_origin.category:

endpoint

If there is asset information in the logs for Endpoints, the detected assets are reported in the Assets Index.

Domain

<Base URL>

where <Base URL> is a variable from the configuration of this connector

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials and Configurations

  • Base URL, Client ID, and Client Secret

Adding a Malwarebytes OneView Connector

To add a Malwarebytes OneView connector:

  1. Obtain credentials
  2. Add the connector in Stellar Cyber
  3. Test the connector
  4. Verify ingestion

Obtaining Malwarebytes OneView Credentials

Before you configure the connector in Stellar Cyber, you must obtain the following Malwarebytes OneView credentials:

Generating the Client ID and Client Secret

To generate the Client ID and Client Secret:

  1. Log in as a Global Administrator or Site Administrator to the OneView Console.

  2. Click Integrate on the navigation menu on the left.

  3. Click Add + in the upper right-hand corner.

  4. In the Create OAuth Client ID window:

    1. Enter an Application Name.

    2. Select read, write, and/or execute.

    3. Click Submit.

    4. Copy the client ID and client secret.

      Store the client secret in a safe location. It cannot be retrieved later although it can be regenerated.

  5. Click OK.

Locating the Account ID

To locate the Account ID:

  • If you are logged into the Nebula site, locate the Account ID in the URL:

    https://cloud.malwarebytes.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/dashboard

  • You can also locate the Account ID in the local activity log:

    C:\ProgramData\Malwarebytes Endpoint Agent\logs\EndpointAgent.txt

Adding the Connector in Stellar Cyber

To add a Malwarebytes OneView connector in Stellar Cyber:

  1. Log in to Stellar Cyber.

  2. Click System | Connectors (under Integrations). 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.

    The asterisk (*) indicates a required field.

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

  5. Choose Malwarebytes OneView from the Type drop-down.

  6. For this connector, the supported Function is Collect, which is enabled already.

  7. Enter a Name.

    Notes:
    • This field does not accept multibyte characters.
    • It is recommended that you follow a naming convention such as tenantname-connectortype.

  8. Choose a Tenant Name. The Interflow records created by this connector include this tenant name.

  9. Choose the device on which to run the connector.

  10. (Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.

  11. Click Next. The Configuration tab appears.

    The asterisk (*) indicates a required field.

  12. Enter the Base URL you noted above in Obtaining Malwarebytes OneView Credentials.

  13. Enter the Client ID you noted above.

  14. Enter the Client Secret

  15. (Optional) Enter the Account ID you noted above. This is for data associated with only one account under a Tenant Name.

    To retrieve endpoints and detections across all accounts, leave this field blank.

  16. Choose the Interval (min). This is how often the logs are collected.

  17. Choose the Content Type you would like to collect. The logs for Endpoints and Detections are supported.

    The Endpoints content type is always selected and cannot be removed from the configuration as it is required for host information.

  18. Click Next. The final confirmation tab appears.

  19. Click Submit.

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 authentication and connectivity).

For connectors running on a sensor, Stellar Cyber recommends that you allow 30-60 seconds for new or modified configuration details to be propagated to the sensor before performing a test.

  1. Click System | Connectors (under Integrations). The Connector Overview appears.

  2. Locate the connector by name 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.

ClosedDisplay sample messages...

Success !

Failure with summary of issue:

Show More example detail:

If the test fails, the common HTTP status error codes are as follows:

HTTP Error Code HTTP Standard Error Name Explanation Recommendation
400 Bad Request This error occurs when there is an error in the connector configuration.

Did you configure the connector correctly?
401 Unauthorized

This error occurs when an authentication credential is invalid or when a user does not have sufficient privileges to access a specific API.

Did you enter your credentials correctly?

Are your credentials expired?

Are your credentials entitled or licensed for that specific resource?
403 Forbidden This error occurs when the permission or scope is not correct in a valid credential.

Did you enter your credentials correctly?

Do you have the required role or permissions for that credential?

404 Not Found This error occurs when a URL path does not resolve to an entity. Did you enter your API URL correctly?
429 Too Many Requests

This error occurs when the API server receives too much traffic or if a user’s license or entitlement quota is exceeded.

The server or user license/quota will eventually recover. The connector will periodically retry the query.

If this occurs unexpectedly or too often, work with your API provider to investigate the server limits, user licensing, or quotas.

For a full list of codes, refer to HTTP response status codes.

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 Detections and Endpoints, change the Indices to Syslog.

    • For Endpoints only, change the Indices to Assets.

    The table immediately updates to show ingested Interflow records.