I’ve been working on a technical presentation to help people understand how Matrix works. Since there have been some updates since I last wrote about it on this blog, I decided to write this post to update some of the content that is no longer current.
Let’s start with a diagram illustrating how the systems work together within the solution.

The list below summarizes the systems that make up Matrix. Many of these are described in previous articles.
- Zefiro produces an Newly Registered Domains (NRDs) feed by integrating DNS providers (zone files, replicas, other feeds).
- Scirocco produces a feed containing domain names present in the CTL.
- Libeccio produces an NRDs feed based on the Scirocco feed.
- Maestrale collect DNS information related to NRDs.
- Miniluv analyzes the various feeds and generates a feed for the subscribers.
- Matrix analyzes the NRDs looking for threats.
- Hammer monitors the domains that Matrix has analyzed without finding suspicious content but which are considered interesting for the future.
- EdJedi is the platform used by the systems to orchestrate the processing of large amounts of data.
- Tramontana integrates the systems so that they are autonomous and separate from each other.
In the table below, I have listed some figures relating to performance.
| Time to detect | Number | Description | |
| Zefiro | Avg 12 hours Max 24 hours | 4-500K | NRDs detected |
| Scirocco | Avg 2 minutes Max 5 minutes | 110-150M | FQDNs collected |
| Libeccio | Avg 50 minutes Max 120 minutes | 2-300K | NRDs collected using 50 processors |
| Maestrale | Avg 40 minutes Max 90 minutes | 1.5-2M | DNS records collected using 30 processors |
| Miniluv | Avg 1 minute Max 5 minutes | 3000 average | Notifications sent |
| Matrix | Avg 7 hours Max 12 hours | 2.5-3M | Analyses performed using 26 processors |
| Hammer | Avg 40 minutes Max 3 hours | 3-500K (average) | Domains monitored using 1 processors |

Leave a Reply