ComplianceAsCode / ComplianceAsCode/content
stig scan mistakenly concludes parameters have not been persisted to kernel because it looks at /etc/default/grub
Open
- Dominant language
- Shell
- Stars
- 2.8k
- Forks
- 828
- Avg merge
- 3d 8m
- Merged PRs (30d)
- 80
Description
#### Description of problem:
rule-detail-id35092
rule-detail-id35093
rule-detail-id35094
when running the remediation playbook these settings are persisted directly to the kernel (i.e. they are not in /etc/default/grub)
however on re-scanning these tasks fail _because_ they are not in /etc/default/grub, which is not strictly necessary for persistence. The scan should ignore /etc/default/grub.
Contributor guide
Assessment
This issue has not been assessed yet.