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.
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: 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 |
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:
- Obtain Broadcom SES credentials
- Add the connector in Stellar Cyber
- Test the connector
- Verify ingestion
Obtaining Broadcom SES Credentials
Follow guidance on Broadcom documentation pages to generate a token used for Stellar Cyber API calls.
-
Login to your Symantec Endpoint Security console.
-
Navigate to Integration > Client Applications.
-
Select Add Client Application.
-
Enter a Name for the application, then click the Add button.
-
Within the client application details screen that displays ensure the following minimum privileges are enabled.
-
Devices: View
-
Alerts & Events : View
-
Policies: View
-
-
Click Save.
-
Click the ellipsis and then select Client Secret.
-
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:
-
Log in to Stellar Cyber.
-
Click System | Integration | Connectors. The Connector Overview appears.
-
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.
-
Choose Endpoint Security from the Category drop-down.
-
Choose Broadcom Symantec Endpoint Security from the Type drop-down.
-
For this connector, the supported Function is Collect, which is enabled already.
-
Enter a Name.
This field does not accept multibyte characters.
-
Choose a Tenant Name. This identifies which tenant is allowed to use the connector.
-
Choose the device on which to run the connector .
-
(Optional) When the Function is Collect, you can create Log Filters. For information, see Managing Log Filters.
-
Click Next. The Configuration tab appears.
The asterisk (*) indicates a required field.
-
In the OAuth Credentials field, enter the value you copied in the previous section.
-
Enter the Interval (min). This is how often the logs are collected.
The interval for Devices is always 24 hours.
-
Choose the Content Type. The logs for Events and Devices are supported.
-
Click Next. The final confirmation tab appears.
-
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.
-
Click System | Integrations | Connectors. The Connector Overview appears.
-
Locate the connector that you added, or modified, or that you want to test.
-
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.
Verifying Ingestion
To verify ingestion:
- Click Investigate | Threat Hunting. The Interflow Search tab appears.
- Change the Indices to Syslog or, for only Devices, select the Assets Index. The table immediately updates to show ingested Interflow records.