From 9cae8e8796444d06236a15e2dd6455268152966d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?An=C5=BEe=20=C5=BDitnik?= <anze.zitnik@xlab.si> Date: Thu, 22 Sep 2022 16:38:25 +0200 Subject: [PATCH] Update README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a771c75..770eee3 100644 --- a/README.md +++ b/README.md @@ -50,7 +50,7 @@ Provisioning existing machines: If you wish to set or remove custom resource ID mapping scheme used by `evidence-collector`, you can change mapped values inside `/environments/full-setup/resource-id-map.json`. - See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/wp3/task_3.2/evidence-collector) for more information. + See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/public/wazuh-vat-evidence-collector) for more information. > Note: neither of these two files has to be changed for `security-monitoring` to work. You can (and should; in case of `.env`) leave them unchanged. @@ -197,7 +197,7 @@ Wazuh manager and Evidence collector should be installed on the same, clean mach `development.env` file includes local development and testing pre-configuration while `production.env` already includes settings for Evidence collector to connect to K8s deployed Clouditor. - See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/wp3/task_3.2/evidence-collector) for more information. + See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/public/wazuh-vat-evidence-collector) for more information. If you're installing both Evidence collector as well as Wazuh manager on the same machine (as intended), you have to set only `clouditor_host`, `elastic_host` & `wazuh_host` variables (where `elastic_host` & `wazuh_host` are the same). -- GitLab