From 8a41d4ece3c16a9864f3da2e497e058e9b3ed6c3 Mon Sep 17 00:00:00 2001 From: Jared Lambert <116378154+jared-lambert@users.noreply.github.com> Date: Tue, 2 Jul 2024 07:41:52 -0700 Subject: [PATCH] Create Duplication Reduction Charter (#163) Signed-off-by: Eddie Knight Co-authored-by: Eddie Knight --- .../duplication-reduction/charter.md | 78 ++++++++++++++++++- 1 file changed, 77 insertions(+), 1 deletion(-) diff --git a/docs/governance/working-groups/duplication-reduction/charter.md b/docs/governance/working-groups/duplication-reduction/charter.md index 782aedde..59486ba4 100644 --- a/docs/governance/working-groups/duplication-reduction/charter.md +++ b/docs/governance/working-groups/duplication-reduction/charter.md @@ -1 +1,77 @@ -Approved by the Steering Committee, but pending merge. Please see [here](https://github.com/finos/common-cloud-controls/blob/83573b755d75676e55438a19cb4f93ab447252df/docs/governance/working-groups/duplication-reduction/charter.md) +# Duplication Reduction Working Group Charter + +This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) Duplication Reduction [WG]. + +## Table of Contents + +1. [Mission](#mission) +2. [Approach & Responsibilities](#approach--responsibilities) + - [Output / Deliverables](#output--deliverables) +3. [Out of Scope](#out-of-scope) +4. [Meeting Cadence](#meeting-cadence) +5. [Governance](#governance) + - [Membership](#membership) + - [Changes](#changes) + - [Meeting Cadence](#meeting-cadence) + - [Changes](#changes) + +## Mission + +This [WG] facilitates the research of existing frameworks for the Common Cloud Controls project community through evaluation of tools, assets, and partners that exist in the cloud controls space that can help reduce the effort required to meet the overall CCC goals for the CCC contributors and consumers. + +Efforts from this group will ensure that the CCC efforts do not duplicate pre-existing standards, and instead are net new contributions to the broader ecosystem aligned to the specific needs of the financial services industry. + +## Approach + +This group will: + +- Identify existing resources that we should investigate for use toward various CCC [WG] goals, including tools, approaches, or frameworks. +- Develop a set of principles and goals to consider for evaluating resources +- Evaluate each resource's ability to meet project goals +- Idenitfy how each resource can help achieve a goal, in a way that can serve as a starting point or reference for other [WG]s +- Document research that has been done on each resource +- Provide a clear set of what's missing from existing frameworks such as NIST, ISO, OSCAL, and MITRE, with how the work being done in CCC augments or improves these systems +- Collaborate with the [Community Structure WG] to create new [recommendations] or policies regarding the use of specific resources, with links to documented research and reasoning +- Provide advice and support related to duplicative efforts to all [WG]s + +### Output / Deliverables + +The following items will be maintained by this [WG] in the project repository: + +- Resource Overview Document +- Featured Resources Guides +- Resource Evaluation Guide + +## Out of Scope + +The following activities will not be performed by this group: + +- Integrating resources into project workflows or outputs +- Ensuring compliance with [recommendations] or [policies] + +## Governance + +This [WG] will remain compliant with all applicable community [policies]. At the guidance of the WG Lead, this group will seek to implement [recommendations] approved by the [Community Structure WG]. + +### Membership + +The membership structure of this working group: + +- WG Lead: Jared Lambert +- SC Sponsor: Eddie Knight +- This group is not authorized to create independent sub-groups + +### Meeting Cadence + +* This working group will use the mail group for regular communications. +* A group member should represent this [WG] on any calls scheduled by the [SC] for participation by the full CCC project community. + +### Changes + +Any functional changes to this charter must be approved through a majority vote by the [SC]. Minor changes such as formatting may be merged upon approval from any [SC] member. + +[WG]: <../../community-groups.md#working-groups> +[SC]: <../../community-groups.md#steering-committee> +[Community Structure WG]: <../community-structure/charter.md> +[policies]: <../../community-policies/README.md> +[recommendations]: <../../community-recommendations/README.md>