Uploaded image for project: 'Cloud Infrastructure Security & Compliance'
  1. Cloud Infrastructure Security & Compliance
  2. CMP-1334

Support Compliance Operator CIS benchmark for IBM Power & System Z Architectures

XMLWordPrintable

    •  Compliance Operator for IBM Power & System Z Architectures
    • False
    • False
    • To Do
    • OCPPLAN-7514 - Securing IBM Power & System Z Architectures
    • OCPPLAN-7514Securing IBM Power & System Z Architectures
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • The goal of this enhancement is to update the OpenSCAP operator to allow for compliance profile scan and remediation of CIS Benchmark on IBM Power & Z architectures and then enable the downstream compliance operator for Power & Z customers.

      Why is this important?

      • The fits into the Secure Computation feature for Power & Z (see links)

      Scenarios

      1. ...

      Acceptance Criteria

      • Pass CI and QE Testing - all CI and QE Testing to be running successfully with tests automated on Z an Power
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • Validation that CIS profile running on both Z and power

      Dependencies (internal and external)

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              Unassigned Unassigned
              dcaspin@redhat.com Doron Caspin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: