Thomas Legris

@dmdhrumilmistry thanks for reporting this issue. The agent needs root permission to access some system information, hence we never looked into rootless mode. If we do that, we might lose...

A server restart does not change self signed certificate. Server is fully http based, the TLS layer comes from router (haproxy) In practice, router image is cached and rarely rebuilt...

Using the Rule is not the right solution, Rules are too generic and we cannot rely on them for comparison. For instance, a rule that matches all .passwd files, it...

This is caused by the linking task which extracts and attaches cloud providers asynchronously. To prevent that, we need to filter out the internet Node directly from the cronjob job...

Hello @lumideez, thanks for reaching out. We don't support Windows console at the moment, we invite you to use GNU/Linux if possible.

Can you please describe your entire setup? The recommended way to use ThreatMapper is to host the console on a linux system (ARM64 or AMD64) and have agents deployed on...

PR to add a way to deploy the cloud formation script across multiple accounts: https://github.com/deepfence/ThreatMapper/pull/768 Note this solution is not ideal since it will deploy 1 cloud-scanner per account. Ideally...

Hello @danielocfb As a newcomer, the main pain point for me was to find a working example that I could play with. I have put the XDP example (from bootstrap...

The proposition is: - We need a global configuration that tells the frequency of each type of scans (`cve`, `secret`, `compliance`) - Every time a `sensor` starts, it fetches its...

I was able to run `go install github.com/zsa/wally-cli@latest` with go1.22 - worked like a charm