scm.cc / FedRAMP 20x KSIs

How scm.cc handles trust

Plain statements of what the product does, taken from its documented behavior. This page makes no certification, authorization or compliance claim.

Read-only connections

Source connections (cloud, code and database security tools) are read-only. Credentials are validated before anything is stored and encrypted at rest (AES-256-GCM).

Auditor access

An organization owner or admin can mint a read-only Auditor API token. Only a hash of the token is stored, every read is access-logged and visible to members, and a revoked token stops working immediately.

Evidence you can check

Monthly continuous-monitoring runs pin their inputs with tamper-evident hashes and can be replayed. Evidence coverage is reported as coverage, not as a compliance verdict.

Sourced references

The FedRAMP 20x indicator list is pinned to the official page and checked weekly for changes. Every indicator has its own page: all 46 Key Security Indicators.

Security overview

Architecture, tenancy and row-level security, encryption, MFA and SSO, logging, backups and restore drills, hosting regions, subprocessors and vulnerability disclosure: read the security overview or download the PDF.

Hosting & data handling

Where scm.cc runs. The application is hosted in the United States on Vercel (application/edge) and Supabase (Postgres database and storage). Data is encrypted at rest (AES-256-GCM) and in transit (TLS). Neither Vercel nor Supabase is itself a FedRAMP-authorized environment today.

Subprocessors that may touch service data:

What leaves your boundary. scm.cc ingests findings and configuration metadata from read-only source connections — not raw Controlled Unclassified Information. For example, it stores that a storage bucket is public, a KSI's pass/fail status, a resource identifier, or a POA&M line item; it does not store the contents of your documents, datasets, or regulated records. Data minimization is a design boundary, not an add-on.

Authorization status. scm.cc is not itself FedRAMP-authorized and makes no such claim. The plan for in-boundary / GovCloud hosting is tracked publicly on our roadmap (#1049); it is an owner-gated decision and no date is promised here.

Sources: docs/FEATURE-COMPLETENESS.md, docs/product-discovery.md (data-minimization boundary), docs/claims-policy.md. Last reviewed 2026-10-18.

Per-organization trust pages are published by each organization from its own account and are opt-in.