SCS Security Guide

[fkr]

From @osism the idea of a SCS Security Guide was raised. The idea is to document the various ways, reasons and decisions that can be taken for a SCS environment. For example: while confidential computing is a very good idea for certain situations / scenarios for others situations other knobs might be more suited to turn on.

Important is that while we document security concepts in the scs security guide that we update the OpenStack Security guide alongside.

Definition of Ready:

• [ ] User Story is small enough to be finished within one sprint
• [ ] User Story is clear and understood by the whole team
• [ ] Acceptance criteria are defined
• [ ] Acceptance criteria are clear and understood by the whole team

Definition of Done:

• [ ] All acceptance criteria are met
• [ ] Changes have been reviewed
• [ ] CI tests have run successfully
• [ ] Documentation has been updated
• [ ] Release Notes have been updated

[fkr]

Looping in @bitkeks

[bitkeks]

Put onto next week's IAM/sec call meeting