Value Statement

This is an internal story only, and does not involve any code. It needs to be delivered in the ACM 2.7 timeframe.

We need to create a GRC Runbook to be used by Service Delivery (SD), DevOps (ACM), and our GRC Engineering team when an incident (either GRC is down in SD or applicable alerts that need immediate attention) occurs.  The initial GA of GRC in the SD environment is in support of Hypershift GA in April 2023.

This Runbook provides the necessary steps to help determine and isolate potential problems, along with corresponding actions to resolve such problems.

Definition of Done for Engineering Story Owner (Checklist)

• The Runbook should be sufficiently detailed such that anyone outside of the GRC Squad, who may have limited GRC knowledge, can follow and execute it.

Development Complete

• N/A

Tests Automated

• N/A

Secure Design

• [N/A] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [N/A] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [N/A] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [N/A] The must-gather script has been updated.