> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudgeni.ai/llms.txt > Use this file to discover all available pages before exploring further. # Compliance Frameworks > Understand which cloud providers are mapped to which active frameworks in the current product and how those mappings should be interpreted. # Compliance Frameworks Cloudgeni does not expose one universal framework matrix for every provider. The active framework set is provider-specific in the current codebase, and the docs should reflect that directly. ## Active Framework Coverage | Provider | Active framework coverage in current code | | -------- | ----------------------------------------- | | AWS | SOC 2, ISO 27001:2022, NIS2 | | Azure | SOC 2, ISO 27001:2022, NIS2 | | GCP | SOC 2, ISO 27001:2022, NIS2 | | OCI | CIS OCI 3.0 | ## Why This Matters Framework pages in the UI are only as strong as the mapping data behind the scan results. That means you should read framework output as: * A structured mapping of findings to requirements * A prioritization tool for remediation * A way to organize evidence and reporting You should not read it as a substitute for a full audit process. ## A Practical Reading Of The Results Use framework views to answer questions like: * Which controls are failing most often in this account? * Which findings affect multiple requirements? * Which areas are worth remediating first before the next review cycle? Use raw monitor findings when you need provider-native detail, and use repository scans when you need file-level code detail. ## Related Framework Pages Operational guidance for reading SOC 2 mappings in Cloudgeni. Operational guidance for ISO 27001:2022 mappings. Notes on the CIS benchmark coverage that is actively surfaced today.