|
| 1 | +--- |
| 2 | +title: Users |
| 3 | +description: FINOS CCC Use Cases and User Journeys |
| 4 | +hide_table_of_contents: true |
| 5 | +--- |
| 6 | + |
| 7 | +import ContentPage from '@site/src/components/ContentPage'; |
| 8 | +import styles from '@site/src/components/AdvanceAutomatedGovernence/styles.module.css'; |
| 9 | +import MonoIcon from "../components/MonoIcon"; |
| 10 | + |
| 11 | +<ContentPage subtitle="Use Cases" title="Who should use FINOS CCC?" toc={toc}> |
| 12 | + |
| 13 | +{/*Image source: https://www.pexels.com/photo/engineer-holding-laptop-1181316/ */} |
| 14 | +<img src="/img/pexels-divinetechygirl-1181316.jpg" alt="woman with laptop in servers"/> |
| 15 | +<div className={styles.footerImage}> |
| 16 | + <MonoIcon /> |
| 17 | +</div> |
| 18 | +### Financial Institutions |
| 19 | +**Use Case 1:** A bank or large financial institution operates multiple cloud platforms and has a dedicated team responsible for cloud security, architecture, compliance, and control assurance. |
| 20 | + |
| 21 | +The organization already maintains internal policies and control requirements but needs a consistent way to assess cloud services, identify relevant threats, and map technical controls across cloud providers. |
| 22 | + |
| 23 | +#### How FINOS CCC Can Be Used |
| 24 | + |
| 25 | +The cloud security team can use the FINOS CCC catalogs as a common reference when reviewing new cloud services and architectures. |
| 26 | + |
| 27 | +A typical workflow could include: |
| 28 | + * *Identify* the cloud services and capabilities used by the proposed architecture. |
| 29 | + * *Review* the threats associated with those capabilities. |
| 30 | + * *Select* the relevant FINOS CCC controls. |
| 31 | + * *Map* the controls to the organization's internal policies, regulatory requirements, and risk framework. |
| 32 | + * *Review* the available test results to understand which controls can be technically validated. |
| 33 | + * *Identify* gaps where additional evidence, compensating controls, or risk acceptance may be required. |
| 34 | + * *Integrate* applicable tests into continuous compliance or policy-as-code pipelines. |
| 35 | + |
| 36 | +**Example:** A development team proposes a new application using managed Kubernetes, cloud storage, and a managed database. |
| 37 | +The cloud security team uses the catalogs to: |
| 38 | + |
| 39 | + * Identify threats related to public exposure, identity, encryption, logging, and data protection; |
| 40 | + * Retrieve applicable controls for each cloud capability; |
| 41 | + * Map those controls to internal cloud security requirements; |
| 42 | + * Determine which controls can be automatically tested; |
| 43 | + * Request evidence for controls that cannot be validated automatically; |
| 44 | + * Document any remaining risks before the architecture is approved. |
| 45 | + |
| 46 | +**Outcomes:** the organization gains: |
| 47 | + * A consistent cloud security review process; |
| 48 | + * Reusable mappings between FINOS CCC and internal controls; |
| 49 | + * Better traceability between threats, controls, tests, and evidence; |
| 50 | + * Reduced duplication across cloud platforms and security teams; |
| 51 | + * Opportunities to automate control validation. |
| 52 | + |
| 53 | +<div className={styles.footerImage}> |
| 54 | + <MonoIcon /> |
| 55 | +</div> |
| 56 | + |
| 57 | +### Smaller Organizations |
| 58 | +**Use Case 2:** A smaller organization may not have a dedicated cloud security team. Responsibility for cloud controls may belong to one security engineer, cloud architect, platform engineer, or compliance specialist. |
| 59 | + |
| 60 | +The organization needs a practical way to understand which controls matter without creating a complete cloud control framework from the beginning. |
| 61 | + |
| 62 | +#### How FINOS CCC Can Be Used |
| 63 | +The person responsible for cloud security can use the catalogs as a structured checklist and learning resource. |
| 64 | + |
| 65 | +A typical workflow could include: |
| 66 | + |
| 67 | + * Identify the cloud services used by the organization. |
| 68 | + * Find the corresponding service capabilities in the catalogs. |
| 69 | + * Review the associated threats to understand the main risks. |
| 70 | + * Select the controls that are relevant to the organization's environment. |
| 71 | + * Review available tests to determine whether the controls are implemented correctly. |
| 72 | + * Prioritize controls based on risk, starting with identity, network exposure, encryption, logging, and data protection. |
| 73 | + * Record controls that require manual verification or future improvement. |
| 74 | + |
| 75 | +**Example:** A small financial technology company runs an application using cloud storage, serverless functions, and a managed database. |
| 76 | + |
| 77 | +The person responsible for security uses FINOS CCC to: |
| 78 | + |
| 79 | + * Understand the main threats affecting each service; |
| 80 | + * Create an initial cloud security baseline; |
| 81 | + * Identify configuration checks that can be automated; |
| 82 | + * Verify existing cloud configurations using available tests; |
| 83 | + * Create a prioritized remediation backlog; |
| 84 | + * Provide evidence to customers, auditors, or business stakeholders. |
| 85 | + |
| 86 | +**Outcomes:** the organization gains: |
| 87 | + |
| 88 | + * A consistent cloud security review process; |
| 89 | + * Reusable mappings between FINOS CCC and internal controls; |
| 90 | + * Better traceability between threats, controls, tests, and evidence; |
| 91 | + * Reduced duplication across cloud platforms and security teams; |
| 92 | + * Opportunities to automate control validation. |
| 93 | + |
| 94 | +<div className={styles.footerImage}> |
| 95 | + <MonoIcon /> |
| 96 | +</div> |
| 97 | +</ContentPage> |
0 commit comments