Description

With the release of Logging 5.9 was released the "Multi log forwarder feature"

This feature enables to run different collectors across different namespaces. Even when originally was not created this feature for delegating to normal users the collection of logs, the reality is that:

• this goal is not mentioned in the documentation
• Even, it could understand the opposite to the goal as said `Administrators can control which users are allowed to define log collection and which logs they are allowed to collect.`. As it's mentioned "users", it can be thought about a normal user
• This can be a huge red flag for multi-tenant environments where the specific project/namespaces owners are not expected to have access to application logs from different projects

Added to the previous and also a consequence being the most important here is that when it's delegated to collect logs to an user and this is one of the usages being done, all the logs: infrastructure, audit and application are mounted in the collector as visible in LOG-4482 being a big security risk.

Then, it should be informed in the "Multi log forwarder feature" about this security risk as all the logs are mounted in the collector.