Enable remediations for sensitive rules #10815
Conversation
|
Start a new ephemeral environment with changes proposed in this pull request: Fedora Environment Oracle Linux 8 Environment |
|
This is basically what was done in this PR: https://github.com/ComplianceAsCode/content/pull/10669/files#diff-45dc2873a403f22be32049fc6a805f2d0d0a8bbff4d48031432674c1f04b0edc The remaining issue there is that these remediations don't make the rules passing on Centos Stream 9 STIG testing that was also added in that PR: https://github.com/ComplianceAsCode/content/pull/10669/files#diff-18c900d4a3ba90888d23b3f649723d13cd6c03ded228fabab9b9a35598c15d29 |
|
Code Climate has analyzed commit 772642c and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 53.5%. View more on Code Climate. |
|
Thanks, this PR is therefore misguided, closing. |
Description:
Rules that configure SSH ciphers/MACs have very tight remediations - they had a per-product granularity of prodtype. I have flipped the
multi_platform_rhelon - those remediations are consistent with checks, and it doesn't make sense to have one, but not the another.Rationale:
Review Hints: