At the moment, installing a scanner will also install its cascading scan rules by default. Anecdotally, I can say that this has led to confusion from some users I talked to, and it can also lead to undesireable / unexpected outcomes ("Why does my nmap suddenly start running ncrack if I only wanted to cascade to $otherScanner?").
I would propose to not ship cascading rules by default. The solution causing the least amount of work would be to disable the installation of cascading rules by default, but allow re-enabling it using the helm values during install (basically invert the current behavior). This would be a breaking change, as it would lead to existing cascading rules being uninstalled by Helm on the next update, according to @J12934. Hence, it would be a candidate for SCBv4.
At the moment, installing a scanner will also install its cascading scan rules by default. Anecdotally, I can say that this has led to confusion from some users I talked to, and it can also lead to undesireable / unexpected outcomes ("Why does my nmap suddenly start running ncrack if I only wanted to cascade to $otherScanner?").
I would propose to not ship cascading rules by default. The solution causing the least amount of work would be to disable the installation of cascading rules by default, but allow re-enabling it using the helm values during install (basically invert the current behavior). This would be a breaking change, as it would lead to existing cascading rules being uninstalled by Helm on the next update, according to @J12934. Hence, it would be a candidate for SCBv4.