When federation has to run under your control: Ping, FedRAMP High and the cloud-only providers
Reviewed 2026-11-10 · Editorial assessment by the editors
By the editors · Published 2026-09-15 · 3 min read
If your identity federation must run in infrastructure you control, or in a FedRAMP High or DoD IL5 environment, Ping Identity is the provider in this comparison that describes it: PingFederate as a dedicated cloud tenant or as software in containers. Okta and Entra ID are cloud services. A middle path is to keep control of the signing key rather than the whole server.
Why would an organisation need control over federation?
For most companies a cloud identity provider is the right default. Some cannot use one for everything: government agencies and their suppliers that need specific authorizations, defence environments, operators with isolated networks, and organisations whose rules say where identity data and signing keys may live. For them the question is not which cloud identity provider scores highest, but where the federation server runs and who holds its keys. This note draws on vendor pages and announcements from February to September 2026.
What does Ping Identity offer?
Ping describes PingFederate as an enterprise federation server supporting OAuth, OpenID Connect, SAML and WS-Federation. It is offered as a dedicated-tenant cloud service, PingOne Advanced Services, or as PingOne Cloud Software that you deploy in containers. Ping lists Ping Government Identity Cloud as FedRAMP High authorized and DoD IL5 certified.
On 26 February 2026 Ping announced that its Secure Containers were approved for Iron Bank, for IL5-aligned defence deployments, and stated feature parity across its IL5, FedRAMP High and Iron Bank deployments. PingOne for Workforce, Ping's cloud service, lists $3 and $6 per user per month on annual contracts of at least 5,000 users.
This is why Ping wins the deployment control row on both the Okta vs Ping Identity and Entra ID vs Ping Identity ballots.
What do the cloud-only providers offer instead?
The Okta pages we reviewed describe cloud plans only, and Okta states that FastPass meets FedRAMP High and NIST requirements for AAL3 on properly configured devices. Entra ID is a Microsoft cloud service; the on-premises pieces Microsoft documents are sync and provisioning agents, which reach on-premises apps without opening firewalls, not a federation server you run. Google Cloud Identity and JumpCloud are cloud services too.
Where the need is data residency rather than self-hosting, regional hosting may be enough. JumpCloud opened an India region in May 2026 for data residency under India's DPDP Act, and NewCore's trust page lists GDPR with EU data residency options.
Is controlling the signing key a middle path?
Sometimes. The most valuable secret in federation is the key that signs SAML assertions and ID tokens: whoever holds it can create valid sign-ins, the attack known as Golden SAML. NIST IR 8587, final on 15 September 2026, concentrates on key management and token verification for exactly this reason.
Some approaches aim to keep key control without running the whole server. NewCore states that its Secure Split Key distributes signing authority between its cloud and your environment. On the standards side, OpenID Connect Key Binding reached Implementer's Draft on 10 September 2026, for binding cryptographic keys within OpenID Connect flows. Neither replaces a FedRAMP authorization where one is required, and NewCore does not publish a deployment model, so ask.
What should you ask each vendor?
- Where are tokens signed, and who can export the signing keys?
- Which authorizations, such as FedRAMP High or IL5, apply to which product and deployment, and are any features missing from that deployment?
- Can the service run in a region that meets your data residency rules?
- What runs on your infrastructure, and what still depends on the vendor's cloud?
- How do you roll back if the self-hosted or regional deployment fails?