XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      LVMS is now designed for FIPS. When installed and running on OpenShift / RHCOS in FIPS mode, LVMS uses the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-3 Validation on the x86_64 architecture.
      Show
      LVMS is now designed for FIPS. When installed and running on OpenShift / RHCOS in FIPS mode, LVMS uses the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-3 Validation on the x86_64 architecture.
    • Feature
    • Proposed
    • 0
    • Program Call

      Feature Overview (aka. Goal Summary)  

      Ensure LVM Storage is fully fips compliance and declare as such in the meta data.

      Goals (aka. expected user outcomes)

       

      LVMS currently is not declaring FIPS compliance. In the light of the 07/23 OpenShift FIPS CVE topic, we want to make sure LVMS operator is fully FIPS compliant and declare as such.

      Requirements (aka. Acceptance Criteria):

      Use only FIPS compliant base images

      Ensure all OpenShift FIPS required practises are adhered to.

      Documentation Considerations

      No special docs needed, as no special config settings are expected. Declaring FIPS compliance in the operator meta data is enough.

      Interoperability Considerations

      None

       

              dfroehli42rh Daniel Fröhlich
              dfroehli42rh Daniel Fröhlich
              Gregory Giguashvili
              Jakob Moeller Jakob Moeller (Inactive)
              Mike Fiedler Mike Fiedler
              Daniel Macpherson Daniel Macpherson
              Chad Scribner Chad Scribner
              Daniel Fröhlich Daniel Fröhlich
              Jon Thomas Jon Thomas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: