-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
ACM 2.8.0
-
False
-
None
-
False
-
-
-
-
No
Value Statement
We can create a gatekeeper Policy/policyset to check on ACM deployments to determine if best practices are followed according to secure-engineering
Definition of Done for Engineering Story Owner (Checklist)
- Gatekeeper best practice for ACM which should apply to other products too.
- consider if OPP products (maybe not ACS?) fit in nicely too
Development Complete
- Deploy the PolicySet and ideally it should be compliant
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 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
- [ ] 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. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.