Cloud Service Certification Project


This page is now found on the Cloud Service Certification Wiki on GitHub

Project Charter


The mission of the Cloud Service Certification Working Group is to accelerate the development, deployment, and adoption of a common set of controls and tests for cloud services.

Business Problem and Opportunity

Cloud services controls and tests are used to demonstrate adherence with regulatory and internal compliance requirements mandated for financial institutions when using cloud services. The majority of cloud security incidents are due to misconfiguration; services are not secure by default, configuration is often complex, nuanced and difficult to validate. To some degree or another all financial institutions are re-inventing the wheel – institutions have similar control frameworks and each is trying to secure and stand up the same providers and services within the same regulatory frameworks.

Having robust controls and tests developed and in place removes a barrier to faster adoption of cloud services such as those provided by Amazon/AWS, Microsoft/Azure and Google/GCP, among others. Addressing this barrier will benefit both financial services IT departments, many of whom are looking to move more quickly to the cloud, and the providers themselves, who wish to sell more cloud services into financial institutions. 

Controls for cloud service compliance afford banks no particular strategic or competitive advantage while also representing a task something all banks who look to deploy more applications onto the cloud needs to do, and as such are conducive to being developed together as part of the "public commons". The focused project and collaboration with other banks will increase the amount of controls produced and, it's expected, help increase the rate of adoption of cloud services.

Approach and Proposed Solution

The working group will produce multiple Cloud Service Certification artifacts (together forming one or multiple accelerators) that provide functional code that implements regulatory compliant configurations of cloud services with BDD tests to validate efficacy.  The group review the artifacts for an accelerator and then gather feedback on process and content before iterating on additional services. A key part of the working group's approach will be to set quality standards across artifacts; members of all tiers can contribute to the project and ensure a common high level of quality is delivered and in less time. The group will also work with cloud service providers to produce more industry specific content and solutions. 


  • Kick off meeting to review existing artifacts and state outcomes and expectations which will include assignments of tasks.
  • Hold biweekly (2 week interval) meetings to do show 'n tell and determine fitness.  We will have this mailing list to communicate more frequently as well.
  • Within 1 month (2 meetings) we will determine fitness of work and begin peer review if enough content is complete.

Group Information

Participation Requirements


Cloud Controls Certification Proposal from Jason Nelson, JPMorgan Chase, January 24th, 2019 (.pdf)

Open Volunteer Roles

Project Participants

NameOrganizationRoleGithub ID
Jason NelsonJPMC**Chairgit-hub-forwork1
Jonathan MeadowsJPMC**Participant
Gavin ManningDB**Participant
Colin MayCredit Suisse**Participant
Astha MalikMicrosoftParticipant
Abdullah GarciaJPMC**Participant
Tais O'DwyerGoogleParticipant
Jonathan HodgsonMorgan Stanley **Participant
Stuart BucklandUBS**Participant
Jonathan AltmanCapitalOne**Participant

(**) indicates FINOS member

The Working Group was approved by the PMC on 2019/02/26.

Need help? Email we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.