Configuring LimaCharlie Connectors

This connector allows Stellar Cyber to ingest logs from LimaCharlie and add the records to the data lake. It integrates with the LimaCharlie API to query for alerts.

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: LimaCharlie

Capabilities

Collect: Yes
Respond: No
Native Alerts Mapped: Yes
Runs on: DP
Interval: Configurable

Collected Data

Content Type	Index	Locating Records
Alerts Sensors (not configurable; logs are automatically collected every 24 hours)	Syslog Assets (for Sensors)	msg_class: limacharlie_alert limacharlie_sensor msg_origin.source: limacharlie msg_origin.vendor: limacharlie msg_origin.category: endpoint

Content Type

Index

Locating Records

Alerts

Sensors (not configurable; logs are automatically collected every 24 hours)

Syslog

Assets (for Sensors)

msg_class:

limacharlie_alert

limacharlie_sensor

msg_origin.source:

limacharlie

msg_origin.vendor:

limacharlie

msg_origin.category:

endpoint

Domain

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

Response Actions

N/A

Third Party Native Alert Integration Details

This connector ingests logs from LimaCharlie to get the raw alerts that are stored in the Syslog index.

Stellar Cyber maps LimaCharlie alerts. The alerts are read from the Syslog index, enriched with Stellar Cyber fields, and mapped (with deduplication) to the Alerts index.

The following types of events for alerts collected by LimaCharlie's EDR sensors are supported: Process Events, Logon Events, and FIM Events.

Deduplication is by tenantid and limacharlie.routing.event_id.

Tactic and Technique are provided by the LimaCharlie raw alerts field limacharlie.detect_mtd.tags.

For details, see Integration of Third Party Native Alerts.

Required Credentials

Host URL, OID, and API Key

Locating Records

To search the alerts in the Alerts index, use the query: msg_class: limacharlie_alert AND _exists_: limacharlie.routing.sid. The _exists_: limacharlie.routing.sid is added to identify the alerts generated by LimaCharlie's EDR sensors.

To search the Original Records in the Syslog index, use the query: msg_class: limacharlie_alert

Let us know if you find the above overview useful.

Adding a LimaCharlie Connector

To add a LimaCharlie connector:

Obtain credentials
Add the connector in Stellar Cyber
Test the connector
Verify ingestion

Obtaining LimaCharlie Credentials

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

OID
API Key

Log in to LimaCharlie as an administrative user.
Select your organization.
Expand Access Management, choose REST API, and locate the OID.
Click Create API Key.
Enable the following permissions: sensor.get, sensor.list, and sensor.task.
Enter a name for the API key and click Create.
Copy the API key.

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

Adding the Connector in Stellar Cyber

To add a LimaCharlie 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 LimaCharlie from the Type drop-down.
For this connector, the supported Function is Collect, which is enabled already.
Enter a Name.
Notes:
- This field does not accept multibyte characters.
- It is recommended that you follow a naming convention such as tenantname-connectortype.
Choose a Tenant Name. The Interflow records created by this connector include this tenant name.
Choose the device on which to run the connector.
(Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.
Click Next. The Configuration tab appears.

The asterisk (*) indicates a required field.
Enter the Host URL for the API server, for example: https://api.limacharlie.io/v1.
Enter the OID you noted above in Obtaining LimaCharlie Credentials.
Enter the API Key you noted above in Obtaining LimaCharlie Credentials.
Choose the Interval (min). This is how often the logs are collected. The default interval is 5 minutes.

The logs for LimaCharlie sensors are queried every 24 hours.
Choose the Content Type you would like to collect. The logs for Alerts and Sensors are supported.

The Sensors content type is always selected and cannot be removed from the configuration as it is required for host information. LimaCharlie sensors are not configurable and are automatically pulled.
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.

Display sample messages...

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:

Click Investigate | Threat Hunting. The Interflow Search tab appears.
Change the Indices for the type of content you collected:
- For Alerts, change the Indices to Syslog.
- For LimaCharlie Sensors only, change the Indices to Assets.
The table immediately updates to show ingested Interflow records.