Skip to content

charter.md

Latest commit

 

History

History
81 lines (54 loc) · 3.54 KB

charter.md

File metadata and controls

81 lines (54 loc) · 3.54 KB

Compliant Financial Infrastructure Working Group Charter

This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) Compliant Financial Infrastructure Working Group (CFI WG).

Table of Contents

  1. Mission
  2. Approach & Responsibilities
  3. Out of Scope
  4. Governance

Mission

The mission of the Compliant Financial Infrastructure (CFI) Working Group is to support the implementation of CCC standards across various computing environments—including cloud, on-premise, and hybrid infrastructure. This group ensures uniformity, quality, and discoverability of these implementations, and validates their compliance through automated testing procedures.

Approach & Responsibilities

This group will:

  • Define and maintain a standardized approach for implementing CCC standards across infrastructure platforms
  • Ensure that all implementations are discoverable, version-controlled, and testable
  • Establish and maintain automated compliance testing tools and validation frameworks
  • Collaborate with the Delivery WG to publish implementations and testing results
  • Work with the Security WG to ensure consistency and non-overlap of controls
  • Integrate feedback from the community gathered by the Communications WG

Output / Deliverables

Artifacts created by this group will be made publicly available in the project’s GitHub repository and will include:

  • Reference implementations of CCC standards for various infrastructure types
  • Automated test suites for compliance validation
  • Documentation and deployment guides for contributors and adopters
  • Dashboard or reporting tools for compliance visibility

Out of Scope

The following are outside the scope of this working group:

  • Implementation of CCC standards for application-level controls not related to infrastructure
  • Manual validation processes or proprietary/non-open implementations

Governance

This WG will remain compliant with all applicable community policies. Under the guidance of the WG Lead, this group will align with the broader framework set by the Community Structure WG.

Membership

  • WG Lead: @eddie-knight
  • SC Sponsor: [To be appointed]

Sub-Groups

This group is authorized to create sub-groups as necessary. Sub-groups must be documented in this charter and approved via pull request by the WG Lead and one SC member.

The following sub-groups have been created under this WG:

  • None

Meeting & Communications

  • This working group will use the CFI mailing list for official communications.
  • Regular meetings will be held at least once every three (3) weeks, excluding November and December.
  • The WG Lead or delegate must provide verbal or written updates at each public SC meeting.

Changes

Any functional changes to this charter must be approved through a majority vote by the SC. Minor changes (e.g., formatting or grammar) may be approved by any SC member.