Epic Goal

• Expand Compliance Operator Profile Support - FedRAMP NERC-CIP

Why is this important?

• IBM Power has offerings to regulated industries.

• - Add FedRAMP High profiles `ocp4-high` `ocp4-high-node` `rhcos4-high`
  - Add FedRAMP Moderate profiles `rhcos-moderate`
  - Add NERC CIP support [link](https://www.ibm.com/docs/en/powersc-standard/2.2?topic=automation-security-compliance-concepts)

Scenarios
1. …

Acceptance Criteria

• (Enter a list of Acceptance Criteria unique to the Epic)
• …

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.