Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-102609

fips=1 is not added to the kernel when selecting the DISA STIG security profile during RHEL 9.6 installation

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Can't Do
    • Icon: Undefined Undefined
    • None
    • rhel-9.6
    • scap-security-guide
    • None
    • Yes
    • Low
    • rhel-security-compliance
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • All
    • None

      What were you trying to do that didn't work?

      Whether using the installation media or imagebuilder when selecting the DISA STIG security profile during the RHEL 9.6 installation, fips=1 does not get added to the kernel for first boot.

      What is the impact of this issue to you?

      Customers are using the security profile during installation to do their hardening and have always had fips=1 added to the kernel. Now, without notice, it is no longer being added and is leading to security issues for them.

      How reproducible is this bug?: Repeatable.

      Steps to reproduce

      1. Start installation of RHEL 9.6
      2. Select the "DISA STIG" in the security profile selection.
      3. Continue configuration and installation.
      4. After first boot, check to see if fips is enabled and fips=1 is added to the kernel

      Expected results

      FIPS is completely enabled on first boot.

      Actual results

      FIPS is not enabled in kernel so system is not full FIPS enabled on first boot.

              vpolasek@redhat.com Vojtech Polasek
              rhn-support-mralph Mike Ralph
              Vojtech Polasek Vojtech Polasek
              SSG Security QE SSG Security QE
              Votes:
              2 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: