Value Statement

It is very important to help the secure engineering team focus pennetration testing on the right aspects of the product. The threat model is also used as a source of truth on the security aspects of the product

Definition of Done for Engineering Story Owner (Checklist)

• Update the thread mode for the global hub in https://github.com/stolostron/acm-threat-model

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [n/a] Unit/function tests have been automated and incorporated into the
  build.
• [n/a] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] 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.