Asimily IoMT

This package contains a parser for Asimily anomaly data and an alert dashboard in JSON format.

The parser normalizes data to a common schema based on an OpenTelemetry standard. This schema allows you to search the data without knowing Asimily's data specifically, and just knowing the common schema instead. It also allows you to combine the data more easily with other data sources which conform to the same schema.

Breaking Changes

This update includes parser changes, which means that data ingested after upgrade will not be backwards compatible with logs ingested with the previous version.

Updating to version 1.0.0 or newer will therefore result in issues with existing queries in for example dashboards or alerts created prior to this version.

See CrowdStrike Parsing Standard (CPS) for more details on the new parser schema.

Installing the Asimily IoMT Package in LogScale

Find the repository where you want to send the logs, or create a new one.

  1. Navigate to your repository in the LogScale interface, click Settings and then Packages on the left.

  2. Click Marketplace and install the LogScale package for Asimily (i.e. asimily/iomt).

  3. When the package has finished installing, click Ingest tokens on the left (still under Settings, see Ingest Tokens).

  4. In the right panel, click + Add Token to create a new token. Give the token an appropriate name (e.g. The name of the server the token is ingesting logs for), and assigned the parser asimily-iomt-json.

    Ingest token

    Figure 6. Ingest token


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

    Now that you have a repository set up in LogScale along with an ingest token you're ready to send logs to LogScale.

  5. Go to the Asimily Console and go to Configuration →Connections and paste the ingest token into Access Token and the LogScale URL into URL and save.

    Asimily Console

    Figure 7. Asimily Console


Verify Data is Arriving in LogScale

Once you have completed the above steps the data should be arriving in your LogScale repository.

You can verify this by doing a simple search for #Vendor = "asimily" | event.module = "iomt" to see the events.

Package Contents Explained

If you want to search using the original field names and values, you can access those in the fields whose names are prefixed with the word "Vendor". Fields which are not prefixed with "Vendor" are standard fields which are either based on the schema (e.g. source.ip) or on LogScale conventions (e.g. @rawstring).

Event Categorisation

As part of the schema, events are categorized by four different fields:

  • event.type

  • event.kind

  • event.category

event.category is an array, so needs to be searched like so: 

array:contains("event.category[]", value="info")

This will find events where some event.category[n] field contains the value "info", regardless of what `n` is. Note that not all events will be categorized to this level of detail.

Normalized Fields

Here are some of the normalized fields which are being set by this parser:

  • event.* (e.g. event.kind, event.module, event.type, event.category )

  • ecs* (e.g. ecs.version )

  • Cps* (e.g. Cps.version )