Skip to content

Framework brief · Authorization

FedRAMP 20x is how a cloud service becomes eligible.

Federal agencies do not invent a one-off security review for every cloud product. FedRAMP is the shared bar. 20x is the path that replaces a stale narrative package with evidence a machine can keep checking.

Current as of November 2026. Operator brief, not legal advice. Paths and deadlines move — confirm them with the program and your sponsoring agency before you plan a year around them.

All six frameworks

What it is

An authorization to handle federal information. Not a logo.

FedRAMP is the US government’s program for authorizing cloud services that handle federal information. Without an authorization, an agency generally cannot put that information in your cloud service. The commercial fact is blunt: no authorization, no federal cloud sale.

FedRAMP 20x is the newer, automation-first path. The proof is machine-readable. Key security indicators are validated continuously, rather than written once into a narrative security package and left to rot. The older Rev5 path still exists for some use cases. They are not interchangeable just because both say FedRAMP on the cover. Do not start a multi-year Rev5 effort without asking which path the agency will actually accept.

A SOC 2 will not get you onto the Marketplace.

Who signs

Automation does not remove the signature.

An agency authorizing official can authorize the service for that agency’s use. The FedRAMP program can authorize it for broader reuse, so other agencies are not starting from a blank page. Either way, a person with authority accepts the risk. A dashboard does not.

In practice, a sponsoring agency still matters. “We will get FedRAMP” with no agency who wants the service is a brochure, not a plan.

This is a cloud-service problem. A federal contract for software that never runs as a cloud offering is a different authorization conversation. Do not drag a team into 20x because the logo showed up in a proposal template.

What done looks like

An authorization an agency can reuse, then evidence that keeps flowing. It is not a PDF you email once and archive.

20x changes how you prove the service more than it changes who is allowed to buy. The direction of travel is machine-readable packages and continuous validation. A longer Word document is not the strategy. Impact level — how sensitive the information is, and what the agency will accept — still decides how high the bar sits. Confirm the current class or baseline with the program. Do not inherit a 2024 org chart of Low, Moderate, and High and assume it is the only vocabulary left.

What it is not

It is not SOC 2 for government. A commercial attestation can inform the story. It does not put you on the FedRAMP Marketplace, and it does not let an agency inherit your package.

It is not HIPAA, even if the agency handles health data. It is not GDPR. It is not ISO 42001. An AI feature inside a federal cloud service can owe 42001’s buyer question and FedRAMP’s authorization at the same time. Governing the model does not authorize the service. Authorizing the service does not govern the model.

State and local buyers often speak a related but separate program. Do not promise a governor’s office that a federal authorization answers their questionnaire.

What the company has to be able to show

The boundary of the cloud service offering. Where federal information would sit. How identity, logging, encryption, change, and incident response actually run — as indicators someone can recheck, not as a paragraph. Who operates the service, and from where. How a customer agency would inherit the package instead of rebuilding it.

Data location will come up in the first meeting. Carbon has no SaaS path for the documentation work: it installs in your environment, on your LLM. That does not authorize you. It does mean the package itself is not a reason to move federal information onto someone else’s cloud.

Where Carbon stops

We do not grant the authorization.

FedRAMP is a framework cue. Carbon generates the documentation package shaped to it — requirements, threat model, evidence narrative, traceability — signed and hash-chained, in your environment. An authorizing official still accepts the risk. A 3PAO, where the path requires one, still assesses. HardStack is not FedRAMP authorized by virtue of writing about the program.

Request a trial