To skip all of the details and get setup with endpoint detection and response capability you can follow our quick start instructions.
The LimaCharlie sensor is a cross platform endpoint sensor (agent). It is a low-level, light-weight sensor that executes detection and response functionality in real-time.
The sensor provides a wide range of advanced capability. Flight Data Recorder (FDR) type functionality like Processes, Network Connections, Domain Name requests etc. Host isolation, automated response rules, intelligent local caching of events for in depth Incident Response (IR) as well as some forensic features like dumping memory.
Full commands list is in the Sensor Commands section.
Installer Keys are used to install a sensor. By specifying a key during installation the sensor can cryptographically be tied to your account. Get more detaisl in the Installation Keys section.
Sensors can have Tags associated with them. Tags are added during creation or dynamically through the UI, API or Detection & Response Rules. Get more information in the Tagging section.
Detection & Response Rules¶
The Detection & Response Rules act as an automation engine. The Detection component is a rule that either matches an event or not. If the Detection component matches, the Response component of the rule is actioned. This can be used to automatically investigate, mitigate or apply Tags.
Detailed explanation in the Detection & Response section.
Since LimaCharlie Enterprise doesn't store data itself, it needs to relay the data somewhere for longer term storage and analysis. Where that data is sent depends on which Outputs are activated. You can have as many Output modules active, so you can send it to two different syslog destinations using the Syslog Output module and then send it two some cold storage over an Scp Output module.
Output is also split between two categories: "event", "detect" and "audit". Event will be a stream containing the all raw data from
all the sensors, so it tends to be a large amount of data. Detect is a stream of detections generated through the
function of the Detection & Response rules. This means you can send your bulk "event" data to a cheap cold storage and
send all the important "detect" data to a Splunk instance or a Slack channel (using the Slack Output). The "audit" stream
receives all auditing events produced by LCE and is useful for compliance.
Exaction configuration possibilities in the Output section.
The API keys are represented as UUIDs. They are linked to your specific organization and enable you to programatically acquire authorization tokens that can be used on our REST API. See the API Key section for more details.
- Manage Installation Keys
- Manage Tags
- Manage Detection & Response Rules
- Sensor Commands
- Output Configuration
- Deploying Sensors
- Exploring Data