LimaCharlie releases a new version of the sensor frequently (generally, every few weeks). LimaCharlie gives you full control over what sensor version is running in your organization; we do not update sensors in your tenant by default.
There are two ways to update all sensors in your tenant to the new version:
Upgrading sensors is done transparently for you once you click the button. You do not need to re-download installers (in fact the installer stays the same). The new version should be in effect across the organization within about 20 minutes.
You can also configure sensors in your tenant to auto-update to the new version when it's released. To do it, tag all sensors in your fleet with the
This will ensure that when a new sensor version is released, it will be in effect across the organization within about 20 minutes.
Tags can be applied on-demand or by using automation. Learn more about ways to apply tags: How can I use tags?
Testing New Sensor Version
It is recommended to test the new sensor version before updating all sensors to confirm that there will be no negative effects.
To test a new sensor version and ensure everything works as intended, you can leverage LimaCharlie's tags functionality.
When you tag a sensor with
lc:latest, the sensor version currently assigned to the Organization will be ignored for that specific sensor, and the latest version of the sensor will be used instead. This means you can tag a representative set of computers in the Organization with the latest tag in order to test-deploy the latest version and confirm no negative effects.
Alternatively, you can tag a sensor with
lc:stable. The sensor version currently assigned to the Organization will be ignored for that specific sensor, and the stable version of the sensor will be used instead.
You can tag the EDR sensor by opening the sensors list, selecting a sensor you would like to test, and navigating to the
tags field on the sensor
lc:stable and click
It will take up to 10 minutes to update the sensor to the stable version.