stig scan mistakenly concludes parameters have not been persisted to kernel because it looks at /etc/default/grub

[longdistancevoyager]

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.

[vojtapolasek]

Hello,
thank you for filling the issue. However, there is quite significant amount of information we are missing. Could you please fill the issue according to the template?
Or at least provide operating system, content version, profile etc.