YiscahLevySilas1

Hi @jeffmou787, thanks for raising this issue. It was a conscious decision not to include some controls in the allcontrols framework such as the CIS controls and those of the...

Hi, we recently added the ability to configure allowed sensitive key names and values in [this PR ](https://github.com/kubescape/regolibrary/pull/581)in regolibrary, @dwertent - I believe it solves #1588 .

Hi @jankoh , AFAIU, the `runAsNonRoot` field affects the UID but not the GID, so even if `runAsNonRoot` is true it would still be best practice to define `runAsGroup` explicitly....

Great - thanks for reporting, I'll update the remediation

Resolved in [regolibrary PR #585](https://github.com/kubescape/regolibrary/pull/585)

This issue was resolved in [this PR](https://github.com/kubescape/regolibrary/pull/581) in regolibrary. We now have `sensitiveValuesAllowed` and `sensitiveKeyNamesAllowed` that allow excluding values and key names from failing, respectively. In the example above of...

Hi @SubhadeepSen , in order to use see the print messages from your rego you need to enable it, we don't do so in kubescape to avoid "noisy" debug messages,...

@slashben what do you think?

Hi, sorry for the delay on this - I opened a [PR](https://github.com/kubescape/regolibrary/pull/599), it will be available in the next regolibrary release, I will update here

Hi @gnd Thanks for reporting this issue. I understand the inconvienence of these false positives.. However, to check only `latest` tags as you suggested will lead to false negatives (like...