# Cloud-agnostic model

CCE separates **neutral entitlement inventory** from **provider-specific policy views**.

## Layers

| Layer | Artifact | Cloud-specific? |
|-------|----------|-----------------|
| Scan | `EntitlementReport` JSON | No — `provider`, `resource`, `operation` per call site |
| Export (default) | E-SBOM `esbom-v1` | No — deduplicated tuples + evidence |
| Export (optional) | IAM/RBAC documents | Yes — `aws-iam`, `gcp-iam`, `azure-rbac` |

## CLI flags

- **`--provider`** — filter entitlements (`AWS`, `GCP`, `AZURE`, …). Omit to include all providers in the report.
- **`--format`** — choose output serializer (`esbom`, `aws-iam`, `gcp-iam`, `azure-rbac`, `entitlement-set`).

Do not use `--provider` to select output format, or `--format` to imply a single cloud.

## Commands

```bash
# Neutral E-SBOM (default)
cce policy export scan.json -o esbom.json

# AWS IAM policy (derived view)
cce policy export scan.json --format aws-iam --provider AWS -o policy.json

# Backward-compatible alias
cce iam export scan.json -o policy.json
```

## Permission mapping confidence

SDK-level tuples are **not** necessarily deployable IAM permission IDs. `-filter cloud` validates the mapper's provider/resource labels, not IAM semantics. Built-in Go GCP rules cover known service packages but may still include local SDK accessors (for example, `bigquery.Client.Dataset` or `bigquery.Query.Read`). Keep the scan JSON or E-SBOM as evidence; do not deploy a role based on raw SDK method names.

The embedded catalog maps reviewed tuples to permissions (`mapping_confidence: catalog` in an enriched E-SBOM). GCP/Azure exports reject uncatalogued tuples by default. `--allow-inferred` explicitly opts in to **unverified guesses** (`sdk_inferred`, formatted from resource and method names); it is for investigation, not deployable least-privilege policy. The current catalog is small, so a strict export may fail until mappings are verified and added.

For example, [cloud-vis run 42690514733](https://github.com/sks/cloud-vis/actions/runs/42690514733) exported `firestore_v1beta1.arrayunion` from a local field transform and `Microsoft.models/models/equals` from a Java SDK model helper when the action's pinned `@v1` passed `--allow-inferred`. Neither string establishes a deployable permission. Strict exports (including current `cce-action` releases) omit a provider's role rather than publishing guesses, but the raw scan can still miss operations on untracked receivers (such as Python `firebase_admin.firestore.client()` and Java `helper.container` fields). A zero-entitlement scan or a successful CI job is **not** evidence that no permissions are required. Review the SDK calls and provider documentation before assigning any role.
