Wazuh visibility #32
Description
In its past form the box4security was meant to have different modules that could be activated separately. Wazuh was one of the services that was not activated by default. To activate Wazuh you currently have to set a value in a modules config file.
The target for now is not to change the visibility. Wazuh should still not start always with the box4security. A new switch in the webapp should be created to toggle the visibility.
Currently only the Wazuh container itself is not started. The Kibana plugin is always present with the Wazuh plugin. A rather large performance penalty is introduced by that inclusion (startup of Kibana app in roughly 5 minutes). Without this plugin the Kibana plugin was able to launch in under a minute.
Evaluation if we can get better performance by having two separate containers should also be done here (And if the performance increases as expected there should be a separate Kibana container that is used when Wazuh is active)