The creation of a Common Cloud Controls 30, 60, 90 day plan

[mcleo-d]

Description

Target date for first draft - 14th September 2023

The creation of the 30, 60, 90 day plan was requested to include the project announcement at the end of October.

• [ ] The plan should be coordinated across all CCC working groups
• [ ] What can be achieved by CCC leading to the live project announcement around Nov 1st?
• [ ] Includes FINOS announcement and conference milestones.

First Major Milestone

• Project live announcement on 1st November in NYC - https://www.finos.org/hosted-events/2023-11-01-open-source-in-finance-forum-new-york

Incremental Milestones

• To be defined

[mcleo-d]

First Iteration NIST / OSCAL Working Group Roadmap

cc @jonmuk

Edits to plan made on 12th October at #54

1. https://github.com/finos/common-cloud-controls/issues/65
2. https://github.com/finos/common-cloud-controls/issues/42
3. https://github.com/finos/common-cloud-controls/issues/43
4. https://github.com/finos/common-cloud-controls/issues/75
5. https://github.com/finos/common-cloud-controls/issues/44
6. https://github.com/finos/common-cloud-controls/issues/45
7. https://github.com/finos/common-cloud-controls/issues/46

[mcleo-d]

First Iteration of Taxonomy Working Group Roadmap

cc @mark-rushing and @moematar

August 24th

• Present initial problem statement and objectives.
• Reference FinOps Foundation and ARC work
• Agree to objectives and timelines.
• Identify volunteer leads.
  • Propose priority services
  • Propose taxonomy of first common service
  • Propose top level of Taxonomy

September 28th

• Agree to priority services (Kubernetes, Object Storage, etc…)
• Discuss taxonomy of first common service
• Discuss top level of Taxonomy
• Identify volunteer leads
  • Finalize priority services
  • Finalize taxonomy of first common service
  • Finalize top level taxonomy
  • Propose second level taxonomy

October 26th

• Approve priority services
• Approve taxonomy of first common service
• Approve top level taxonomy
• Discuss second level taxonomy
• Identify volunteer leads
  • Finalise second level taxonomy
  • Define common capability qualifiers for priority services

Example Taxonomy

Data-At-Rest -> Database -> Relational

Capability Qualifiers

• Field level encryption
• Regional Replication
• Scalability
• Transactions per second

[mcleo-d]

@jonmuk, @mark-rushing and @moematar - I have added your working group roadmaps to this GitHub issue following #23 and #7. Please cast your eyes over as it would be good to break actionable items into GitHub Issues.

@git-hub-forwork1 - It would be great if you could add your expected 30, 60, 90 day outcomes to the comments, as I'd like to combine all three working groups into one combined mapping for the next iteration.

Thanks in advance.

James.

cc @rhyddian

[mcleo-d]

Please see @iMichaela's comments on the following PR with regards to the OSCAL working group roadmap.

• https://github.com/finos/common-cloud-controls/pull/52#pullrequestreview-1675509356

[mcleo-d]

@jonmuk, @iMichaela, @rachkim00 👋🏻

I have added due dates to the OSCAL Roadmap Items following meeting #54 and have updated the PR below to reflect the changes.

• https://github.com/finos/common-cloud-controls/pull/52

I hope this helps with the working group planning.

Speak soon,

James.