Epic Goal

• Keep OCP4 STIG profile up to date with DISA's releases.

Why is this important?

• Every quarter DISA releases updates to their STIGs and we have 90 days from the publication date to have a profile aligned with the update available for our customers.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. If DISA doesn't release an update, there is no demand for updates, except for bug fixes.
2. Some changes can only be implemented after they are incorporated by DISA into the OCP4 STIG.

Previous Work (Optional):

1. CMP-2076

Open questions::

1. ...

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>