-
When I click on MENU / Manage Correlation Rules (in web interface of UTMStackServer) I do not see there any rules. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
Hi, @lacak-sk. All versions and variants of UTMStack have the correlation rules preinstalled, but you can see the system rules folder only in the latest versions because we moved the project to open source. If you can't see the folder, you're using an old version. Best regards |
Beta Was this translation helpful? Give feedback.
-
Thanks, but I downloaded "ISO Image" from https://utmstack.com/install/ so I think that it is current version (https://cdn.utmstack.com/iso/utmstack-v10-1-0-autoinstall.iso) ... does is it not? |
Beta Was this translation helpful? Give feedback.
-
Hi @lacak-sk, rules are on a public git repository, please check if you have something blocking connections to git repositories. Best regards |
Beta Was this translation helpful? Give feedback.
-
Thanks. I have deployed UTMStackServer behind corporate firewall, but I do not think that firewall block outbound connection to git repository. I can successfully do (from Ubuntu console) for example "sudo apt update", "sudo apt upgrade", "wget http://github.com/utmstack/UTMStack/releases/latest/download/installer". |
Beta Was this translation helpful? Give feedback.
-
I can confirm, that there is logged error message: "Could not update ruleset ...":
But root of problem was same as in #599. After I apply steps suggested in https://github.com/orgs/utmstack/discussions/599#discussioncomment-9260240, the directory "system" was created with the rules. |
Beta Was this translation helpful? Give feedback.
I can confirm, that there is logged error message: "Could not update ruleset ...":
(docker service logs utmstack_correlation 2>&1 | grep "Could not update ruleset")
But root of problem was same as in #599. After I apply steps suggested in https://github.com/orgs/utmstack/discussions/599#discussioncomment-9260240, the directory "system" was created with the rules.
So basically it was a docker network issue.