Configuring VMware Workspace ONE Connectors

This connector allows Stellar Cyber to ingest logs from VMware Workspace ONE and add the records to the data lake.

Connector Overview: VMware Workspace ONE

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

Launch

Login

Syslog

msg_class:

vmware_workspaceone_launch

vmware_workspaceone_login

msg_origin.source:

vmware_workspaceone

msg_origin.vendor

vmware

msg_origin.category:

endpoint

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

  • Base URL: https://<your organization id>.workspaceoneaccess.com

  • Client Secret

               Let us know if you find the above overview useful.

Adding a VMware Workspace ONE Connector

To add a VMware Workspace ONE connector:

  1. Obtain your VMware Workspace ONE Client ID
  2. Add the connector in Stellar Cyber
  3. Test the connector
  4. Verify ingestion

Obtaining your VMware Workspace ONE Client Secret

Follow guidance on the VMware documentation portal to generate your Client Secret.

Adding the Connector in Stellar Cyber

With the access information handy, you can add a VMware Workspace ONE connector in Stellar Cyber:

  1. Log in to Stellar Cyber.

  2. Click System | Integration | 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.

    The asterisk (*) indicates a required field.

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

  5. Choose VMware Workspace ONE 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.

  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.

    The asterisk (*) indicates a required field.

  12. Enter the Base URL using the information you noted above.

  13. Enter the Client Secret you noted above.

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

  15. Choose the Content Type. The logs for Launch and Login are supported.

  16. Click Next. The final confirmation tab appears.

  17. Click Submit.

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

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).

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 | 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.

ClosedDisplay sample messages...

Success !

Failure with summary of issue:

Show More example detail:

 

Verifying Ingestion

To verify ingestion:

  1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
  2. Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.