FedRAMP and Air-Gapped Deployment Patterns for Customer Engagement Systems

A FedRAMP compliant CRM is a cloud service that a FedRAMP-recognised process has certified at the impact level your data needs, and FedRAMP covers cloud services that handle federal information on behalf of an agency. Software an agency runs itself, such as a customer data platform (CDP) deployed in GovCloud or an air-gapped enclave, is authorised through the agency's own authority to operate (ATO) under NIST's Risk Management Framework, inheriting controls from the certified infrastructure beneath it.

Who this is for: agency system owners, authorising officials and contractors choosing between a certified SaaS product and a customer-operated deployment for citizen or beneficiary communications. It is part of the government industry hub.

How FedRAMP works, and what changed in 2026

The programme has been changing quickly, and older articles use outdated terms:

• Terminology. On 4 May 2026 FedRAMP changed "authorization" designations to "certification", and impact levels became certification classes A to D 2. Class A is a pilot class, Class B corresponds to Low, Class C to Moderate, and Class D (High) is still to be developed 3.
• 20x. FedRAMP describes 20x as a newer approach based on measured outcomes, against the Rev5 approach based mainly on documented plans 4. The Moderate pilot began on 18 November 2025 with first authorisations on 6 March 2026; the programme says it is in Phase 3, wide-scale adoption 3.
• Rev5 end date. FedRAMP states it will stop accepting new Rev5 certifications on 11 June 2027 3.
• Consolidated Rules. The Consolidated Rules for 2026 (CR26) were released on 24 June 2026, and Rev5 and 20x pilot documentation moved to a legacy area 2.
• High. A Class D (High) cloud-hosted pilot requirements RFC (RFC-0036) was published on 15 October 2026 2.
• Marketplace. The FedRAMP home page showed 544 certified services, 32 of them 20x, on 17 October 2026 5.

If a vendor's collateral still says "FedRAMP Authorized", it is likely using the pre-May 2026 label; the Marketplace is the source of truth.

SaaS versus software you deploy

The question that decides your path is who operates the system that touches federal information.

Both routes end in an agency decision. Under NIST SP 800-37, the authorisation step is where an official accepts the residual risk of operating a system 6. A certified SaaS product shortens the evidence you must produce; it does not remove the decision.

Moderate versus High data

NIST SP 800-53 control families that matter for customer data

NIST SP 800-53 Rev. 5 has 20 control families, and release 5.2.0 (27 August 2025) added SA-15(13), SA-24 and SI-02(07) 8. For a system holding consent, preferences and messages, these families carry most of the weight:

Control identifiers are from the Rev. 5 catalogue 8. Use the agency's tailored baseline for the exact set.

Who lists FedRAMP-certified engagement tooling

The FedRAMP Marketplace web application is script-driven, so we read the published Marketplace data file (last changed 17 October 2026) and the vendors' own pages 9. Names and levels below should be re-checked on marketplace.fedramp.gov before any procurement use. The data file still labels statuses "FedRAMP Authorized".

| Granicus GovDelivery Communications Cloud | SaaS | Moderate | Email, SMS and subscription communication with constituents 10 | | Adobe Campaign | SaaS | LI-SaaS | Campaign management; low-impact SaaS baseline | | Adobe Experience Manager Managed Services | SaaS | Moderate | Content management | | Oracle Service Cloud; Oracle Fusion Cloud (includes CX) | SaaS | Moderate | Customer service and CX | | Genesys Cloud CX | SaaS | Moderate | Contact centre | | Sprinklr CXM for Government | SaaS | LI-SaaS | Social and digital engagement | | ServiceNow Government Community Cloud | PaaS, SaaS | High | Workflow platform |

Two practical cautions. First, certification attaches to a specific offering and boundary: a vendor can hold FedRAMP certification for one product while the product you want sits outside it. Second, certified SaaS products are built for generic multi-agency use; the eligibility-messaging and audit requirements in our explainable eligibility communications article often need configuration the product does not ship.

Deployment patterns, from GovCloud to air-gapped

Offline update channel

An air-gapped system still needs patches. Design the channel before procurement:

1. Signed artefacts only. Releases are signed by the vendor; the enclave verifies signatures against a locally held public key (CM-14, SI-7 above).
2. Provenance and inventory. Ask for a software bill of materials, which CISA describes as a nested inventory of software components and a building block of supply-chain risk management 12, and for build provenance in the SLSA sense, tamper-resistant evidence of how an artefact was built 13.
3. Controlled import. Artefacts arrive via scanned media or a one-way transfer, are hashed and verified, staged in a quarantine registry, then promoted.
4. Rollback. Keep the previous release and a tested restore, because you cannot call the vendor during an incident.

Model weights stay local

AI features are the usual place an "isolated" design leaks, because a hosted model API is an outbound call. In an air-gapped pattern the models run locally: open-weight models served on in-enclave GPUs, loaded by the same signed-import process as code. Signing model files is supported by the OpenSSF model-signing project, which produces a signature over file hashes and allows key-based verification with a local public key; whether its transparency-log checks work offline is not stated, so plan on key-based verification 14. Our articles on agents inside your boundary and on-premise LLM deployment cover serving and cost.

Decision table

For a qualitative example, our federal health agency case used a hybrid deployment, consolidated six vendor systems into one audit ledger, and produced explainable eligibility messaging; see cases. PrivyCDP is customer-owned software, so the authorisation boundary is the agency's own; it is not a hosted service that carries its own certification.

Procurement and ATO checklist

1. Write down the data's FIPS 199 category before looking at products.
2. Ask whether the requirement is a cloud service (FedRAMP) or an agency-operated system (ATO), using the scope language in M-24-15 1.
3. Check the Marketplace for the exact offering name, class and status, and read the boundary.
4. Confirm that the features you need are inside the certified boundary.
5. For deployed software, request SSP-ready control implementation statements mapped to your baseline.
6. Require signed releases, an SBOM and provenance evidence.
7. Define the offline update and rollback procedure and test it.
8. Keep keys in agency-controlled hardware security modules.
9. Prove egress is closed: allow-list outbound traffic and test it.
10. Identify every model and where it runs.
11. Plan for the 2027 Rev5 intake end and Class D if you need High certified SaaS.
12. Record the authorising official's risk acceptance.

---

It does not describe any agency's authorisation decision.