Mabille Raphaël

report n°005 | 2026‐01‐26

We have a need to visualize raw data that we collect from our pluggins to be able to make reports about them and their evolution, we chosed to explore Metabase as an option for its presumed ease of use and Grafana for its precise control of how to make data looks.

The pipeline we work with is:

• plugins pump out data in json
• a script put everything in a sqlite database
• the visualisation tool (Metabase or Grafana) is used to extract relevant charts
• a performance report is written

Pre checks done :

• is open source and free to use | both AGPL-3.0 license

report n°004 | 2026-01-04

Overview​

In this post we will talk about what metrics we use and why we chose them to measure the performance and health of our software through each update.

1. Shared metrics

2. Module specific metrics

3. User specific metrics

report n°003 | 2025‐11‐11

context​

This research was done when faced with the following question:

• Should we triage files depending on their types (file extension) to run specific yara rules on them ?

This question triggered two necessary research topics :

1. is there specific YARA rules for specific files format ?
2. if there is, is it interesting to use a triage method on those files ?

report n°002 | 2025-10-23

What has been implemented​

1. A GitHub project with different views to track work to be done, work in progress, and each person's individual workload.

2. Two-week sprint periods with corresponding milestones in the GitHub project and scheduled meetings in Discord.

3. A workflow for managing pushes to the GitHub repository.

report n°001 | 2025-10-22

Context​

The yara library is a library written in C that allows pattern matching YARA rules on text in a file.

It is at the heart of our static detection module and is the most computationally intensive part of the module. It is therefore crucial that it be as efficient as possible.