You'll need to create a new repository in LogScale to hold the Corelight data. If you're not sure how to do this, see the Create a Repository documentation page.

Once you've created a repository, from that target repository in the LogScale Interface, select the Settings tab and then Packages on the left. From there, choose Marketplace and install the LogScale Package for Corelight (i.e. corelight/sensor), as shown in the screenshot in Figure 26, “Preparations in LogScale”.

Figure 26. Preparations in LogScale

When you select the Corelight package, it will describe what the package provides and other related information. Of most interest is that it will install the required corelight parser. And it will install some overview dashboards that you can edit later to suit your needs.

When it's finished installing, from the Corelight repository, go to the Settings tab. In the Ingest section, click API Tokens on the left (see Figure 27, “Corelight Ingest Tokens”).

In the right panel, click + Create Token to create a new token. Be sure to assign it the corelight parser. You can see the results of doing this in Figure 27, “Corelight Ingest Tokens”.

Figure 27. Corelight Ingest Tokens

Before leaving this page, view the Corelight token and copy it to your clipboard — or to save it temporarily elsewhere.

Now that you have a repository set up in LogScale to receive data from Corelight, you're ready to configure Corelight.

To configure Corelight to send data to LogScale, to the repository created in the previous section, you'll have to log into the Corelight management interface. Navigate to the Sensor menu and choose Export. From there, select Export to Splunk HEC. Despite the label, this is the preferred option for sending logs from Corelight to LogScale.

You'll be presented with a screen asking for several setting values similar to the screenshot shown below in Figure 28, “Configure Corelight”.

Figure 28. Configure Corelight

For the first box, the HEC URL, enter your LogScale service URL appended with /api/v1/ingest/hec. For example, if you're using the LogScale EU Cloud, you would enter, https://cloud.humio.com/api/v1/ingest/hec.

In the box labeled, HEC Token, paste in the ingest token you copied earlier from the target repository above (see Figure 27, “Corelight Ingest Tokens”). Then set the Sourcetype Template to $LOG, as shown in the screenshot above.

For the rest of the settings you can probably accept the defaults, initially. However, you may want to check those settings to ensure all of the logs you need are being sent to LogScale — and that you're excluding what you don't want to send.

After a bit, the Corelight logs should be ingested into your LogScale repository. Navigate to the LogScale repository and view the Corelight dashboards to check data is coming in and is displayed as expected.

Corelight and LogScale's integrated solution helps customers manage security threats and gain visibility across an organization's entire network. LogScale and Corelight have a long established partnership. The LogScale service is used for the Corelight@home program, which provides an easy way to use Corelight with a Raspberry Pi based software sensor.

For Corelight customers wishing to use LogScale purely for their Corelight data, we have a unique pricing offer that provides unlimited ingest. Pricing is based on the size of Corelight sensor.

For more information on using Corelight with LogScale, review these resources: