Configuring Stellar Cyber Connectors

This connector allows Stellar Cyber to ingest logs from Stellar Cyber and add the records to the data lake. It integrates with the Stellar Cyber API to ingest User Activity data. This helps you quickly search for security events, view the data in Threat Hunting, and create Automated Threat Hunting (ATH) rules.

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: Stellar Cyber

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

User Activity

Syslog

msg_class:

stellar_cyber_user_activity

msg_origin.source:

stellar_cyber

msg_origin.vendor:

stellar_cyber

msg_origin.category:

xdr

Domain

<Platform URL>

where <Platform 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

  • Platform URL and API Token

Adding a Stellar Cyber Connector

To add a Stellar Cyber connector:

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

Obtaining Stellar Cyber Credentials

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

  • Platform URL—The platform base URL for API access. This is the URL you use to access Stellar Cyber, for example: https://sample-url.stellarcyber.cloud

  • API Token—The authentication credentials for API access. To get the Stellar Cyber API token, follow the guidance for generating Scoped API Keys in Configuring API Authentication.

Adding the Connector in Stellar Cyber

To add a Stellar Cyber connector in Stellar Cyber:

  1. Log in to Stellar Cyber.

  2. Click System | INTEGRATIONS | Connectors. The Connector Overview appears.

  3. Click Create and select Connector.

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

  4. Choose Extended Detection & Response from the Category dropdown.

  5. Choose Stellar Cyber from the Type dropdown.

    The asterisk (*) indicates a required field.

  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. Select the Platform URL you noted above in Obtaining Stellar Cyber Credentials.

  13. Enter the API Token you noted above.

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

  15. (Optional) Click Disable SSL Certificate Verification if you want to disable SSL certificate verification. Only disable SSL certificates if you have a reason to, otherwise, it is not a good security practice.

  16. Choose the Content Type you would like to collect. The logs for User Activity are supported.

  17. Click Next. The final confirmation tab appears.

  18. Click Submit.

The new connector is immediately active.

Testing the Connector

In addition to testing for connectivity, the Test button for the Stellar Cyber connector tests that the Platform URL and API Token are correct and data requests for the requested content type returns successful responses.

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 | INTEGRATIONS | Connectors. 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. Select Threat Hunting.

    The Interflow Search tab appears.

  2. Change the Indices to Syslog.

    The table immediately updates to show ingested Interflow records.