You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
osbuildRelated in some way to Image Builder.RHELRed Hat Enterprise Linux product related.RHEL8Red Hat Enterprise Linux 8 product related.RHEL9Red Hat Enterprise Linux 9 product related.RHEL10Red Hat Enterprise Linux 10 product related.
on a Secure Boot (UEFI) virtual machine results in
Remediating rule 255/491: 'xccdf_org.ssgproject.content_rule_mount_option_boot_efi_nosuid'
Remediation is not applicable, nothing was done
however a subsequent scan on a booted system fails, so it clearly is applicable there.
Is it possible that the efi partition is being added late in the process, so oscap remediation doesn't see it?
Maybe some other reason?
AFAICT - OSBuild does build an UEFI-capable qcow2 image, so it does work in both legacy BIOS and UEFI modes, but maybe oscap remediation doesn't try to remediate both ... ?
mount_option_boot_efi_nosuid seems to be using the standard mount_option template, nothing super custom.
Build a qcow2 image via OSBuild, using the generated blueprint
Import it via virt-install, but add --boot firmware=efi,loader_secure=yes to the virt-install CLI to make it create an UEFI / Secure Boot VM
Boot and try oscap xccdf eval, the fail should be there
The text was updated successfully, but these errors were encountered:
comps
added
RHEL
Red Hat Enterprise Linux product related.
RHEL9
Red Hat Enterprise Linux 9 product related.
RHEL8
Red Hat Enterprise Linux 8 product related.
RHEL10
Red Hat Enterprise Linux 10 product related.
osbuild
Related in some way to Image Builder.
labels
Oct 17, 2024
osbuildRelated in some way to Image Builder.RHELRed Hat Enterprise Linux product related.RHEL8Red Hat Enterprise Linux 8 product related.RHEL9Red Hat Enterprise Linux 9 product related.RHEL10Red Hat Enterprise Linux 10 product related.
Description of problem:
Remediating ie.
stig
using OSBuild (Image Builder) via an oscap-generated Blueprint, which containson a Secure Boot (UEFI) virtual machine results in
however a subsequent scan on a booted system fails, so it clearly is applicable there.
Is it possible that the efi partition is being added late in the process, so oscap remediation doesn't see it?
Maybe some other reason?
AFAICT - OSBuild does build an UEFI-capable qcow2 image, so it does work in both legacy BIOS and UEFI modes, but maybe
oscap
remediation doesn't try to remediate both ... ?mount_option_boot_efi_nosuid
seems to be using the standardmount_option
template, nothing super custom.SCAP Security Guide Version:
master @ b79ef87
Operating System Version:
RHEL-8, RHEL-9, probably RHEL-10 too
Steps to Reproduce:
oscap xccdf generate --profile stig fix --fix-type blueprint datastream.xml
virt-install
, but add--boot firmware=efi,loader_secure=yes
to thevirt-install
CLI to make it create an UEFI / Secure Boot VMoscap xccdf eval
, the fail should be thereThe text was updated successfully, but these errors were encountered: