Configuring Broadcom Symantec Endpoint Security (SES) Connectors

This connector allows Stellar Cyber to ingest logs from Broadcom SES and add the records to the data lake.

Connector Overview: Broadcom SES

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

Devices

Events

Assets

Syslog

msg_class:

broadcom_devices

broadcom_events

msg_origin.source:

broadcom_ses

msg_origin.vendor:

broadcom

msg_origin.category:

endpoint

Domain

https://<Hostname>

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

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials

  • OAuth credentials

               Let us know if you find the above overview useful.

Adding a Broadcom SES Connector

To add a Broadcom SES connector:

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

Obtaining Broadcom SES Credentials

Follow guidance on Broadcom documentation pages to generate a token used for Stellar Cyber API calls.

  1. Login to your Symantec Endpoint Security console.

  2. Navigate to Integration > Client Applications.

  3. Select Add Client Application.

  4. Enter a Name for the application, then click the Add button.

  5. Within the client application details screen that displays ensure the following minimum privileges are enabled.

    • Devices: View

    • Alerts & Events : View

    • Policies: View

  6. Click Save.

  7. Click the ellipsis and then select Client Secret.

  8. Click the copy icon for the OAuth Credentials value for the Stellar Cyber connector to generate a bearer token.

Adding the Connector in Stellar Cyber

With the access information handy, you can add a Broadcom SES 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 Broadcom Symantec 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 .

  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. In the OAuth Credentials field, enter the value you copied in the previous section.

  13. Enter the Interval (min). This is how often the logs are collected.

    The interval for Devices is always 24 hours.

  14. Choose the Content Type. The logs for Events and Devices are supported.

  15. Click Next. The final confirmation tab appears.

  16. 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 or, for only Devices, select the Assets Index. The table immediately updates to show ingested Interflow records.