Officially Naming the Common Cloud Controls Project

[mcleo-d]

Officially Naming the Common Cloud Controls Project

Now Common Cloud Controls is up and running, we'd like to get your names, thoughts and feedback on the Official Live Name of the CCC Project as discussed during the project kick off here #1.

We're targeting 1st September 2023 for the official project name change, so please use this GitHub issue to add your ideas over the next few days so we can also engage legal checks.

All names and ideas are welcome and remember to +1 positive suggestions 😸

[eddie-knight]

Financial Infrastructure Standards and Taxonomy (FIST)

[mcleo-d]

Please find below a few more ideas that have been suggested by @mindthegab ...

• FinRAMP - Could be too similar to FedRAMP, but it would be easy to understand / self-discover.
• C3FS - Similar to FSC3, but in a different order
• FS(O)CC - Financial Services (Open) Cloud Controls
• FIOCC - Financial Industry Open Cloud Controls
• FISCO - Financial Industry Secure Cloud Operations
• SCOPE - Secure Cloud Operations for the Financial Ecosystem

[rgriffiths-scottlogic]

FactoCore - you could backronym to Financial services Agnostic Common Taxonomy Of COntrols and REgulations if you really wanted to but it's more to do with the core/central/common nature of the project and the "facts" that are trying to be defined

[rgriffiths-scottlogic]

CONCORDE - Common Open-source Nomenclature for Cloud Operations and Regulatory Definitions

[rgriffiths-scottlogic]

CONCORDE - Common Open-source Nomenclature for Cloud Operations and Regulatory Definitions

We could also drop the last E and go with CONCORD because that has the added bonus of its dictionary definition: "agreement or harmony between people or groups"

[AdrianHammond]

Any reason why we don't keep CCC?

[vicenteherrera]

I see the goal of this project is very generic, can go beyond just helping financial institutions. Of course these organizations always have very complex environment where security is always paramont, so the need is obvious in this use case. But if there would already be a common taxonomy well defined by NIST, MITRE, CIS or any other one, we would have embraced it already. What I want to suggest is to have a name that is more or less neutral so any kind of organization can be drawn into using it, and not making Finos or the letter F the first thing on it. It could be something like "Commond Cloud Control, by Finos", if neccessary, and just abbreviated "CCC".

[ianmiell]

I'm also keen for this project not to identify itself too closely with financial services. We work with customers in much less regulated sectors and they are increasingly self-imposing controls that looks similar to ones we are likely to discuss.

On that basis I like acronymic names which don't commit to an industry, like C3 or CCC. I quite like Concord as it's much more memorable than 'Common Cloud Controls' (which is a mouthful, and I keep having to 'unpack' from my mental mnemonic of C3).

[mcleo-d]

Hi @l1ttlej1m,

I thought you'd like to feedback on the CCC names suggested in this GitHub issue.

Kind regards,

James.

[mcleo-d]

Hi 👋🏻

I'd like to inform the CCC project community that The Linux Foundation trademark council has given us the go-ahead to use "FINOS Common Cloud Controls" and "FINOS CCC" as the official name(s) of this project 💯

After researching "Common Cloud Controls" and "CCC", both versions of this name are fairly common across horizontal industries which means the "FINOS" brand has been added as prefix to make the project distinctive.

Thank you everyone for your input on this task. This issue will be added to the #53 agenda where it will be announced and closed. Feel free to feedback in the comments in the meantime.

Kind regards,

James.

[jonmuk]

now moving forward with FINOS-CCC as the formal name