From 59e546e995344455fc06e7e2231df4466b63c757 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?F=C3=A9lix=20Aim=C3=A9?= Date: Wed, 25 Nov 2020 17:32:07 +0100 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f0e1261..1120074 100644 --- a/README.md +++ b/README.md @@ -125,12 +125,12 @@ In order to keep IOCs and whitelist updated constantly, TinyCheck integrates som If you have seen something very suspicious and/or needs to be investigated/integrated in one of these two lists, don't hesitate to ping us. You can also do you own watcher. Remember, sharing is caring. -### Q&A with the developper +### Q&As **Your project seem very cool, does it send data to Kaspersky or any telemetry server?**
No, at all. You can look to the sources, the only data sent by TinyCheck is an HTTP GET request to a website that you can specify in the config, as well as the watchers URLs. Kaspersky don't - and will not - receive any telemetry from your TinyCheck device.

**I'm not very confortable with the concept of "watchers" as the IOCs downloaded are public. Do you plan to develop a server to centralize AMBER/RED IOCs?**
-Yes, if the demand is felt by NGOs (contact us!). Is it possible to develop this kind of thing, allowing you to centralize your IOCs and managing your fleet of TinyCheck instances. The server can also embed better detection rules thanks to the telemetry that it will receive.


+Yes, if the demand is felt by NGOs (contact us!). Is it possible to develop this kind of thing, allowing you to centralize your IOCs and managing your fleet of TinyCheck instances. The server can also embed better detection rules thanks to the telemetry that it will receive.
### Possible updates for next releases