Ping Identity Security Review
Ping Identity federates trust to every application that relies on it, exactly as your PingOne or PingFederate configuration allows. We test the connections, tokens, MFA policies and admin roles you actually configured. CREST-certified testers, fixed price from £3,290 for a 2-day single-tenant scope, quoted within 24 hours.
- Unlimited retesting
- Unlimited pre-retesting
- No hidden fees
“I would highly recommend EJN Labs to any organisation seeking reliable, detailed, and well-managed penetration testing services, particularly for government or enterprise-level projects.”
“There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.”
Every PingOne connection, token and admin role is trusted exactly as far as your own configuration allows, and your team decides how far that is.
A Ping Identity deployment is only as secure as the connections, tokens and roles your team configured
PingOne administrator roles are built for least privilege: an Environment Admin manages environments and their resources, an Identity Data Admin manages user identities, and an Application Owner is limited to the applications they are assigned, with each role assignable at the organisation, environment, population, group or application level. That range of scope is also the risk: a role built to sound narrow can still be assigned wider than the job it was meant for, and a worker application or PingFederate gateway can hold the same roles as a person.
Federation trust is set connection by connection. A SAML connection is defined by its PingOne entity ID, assertion consumer service endpoint and signing certificate, an OIDC connection by its issuer, JWKS endpoint and discovery document, and a redirect URI that PingOne matches exactly unless a wildcard or loopback entry widens it. None of that is checked by Ping Identity on your behalf: a stale signing certificate, an over-broad redirect pattern or an access token left on its one-hour default lifetime is a decision your own configuration made.
We test the PingOne environment or PingFederate and PingAccess deployment you actually run: the connections, token lifetimes, MFA policies and admin roles configured within it. We never test Ping Identity’s own infrastructure, in the same way we test client configuration on Okta tenants rather than Okta’s platform.
SCOPE
What we review in a Ping Identity deployment
SAML Connection Configuration and Signing Certificates
Each SAML connection is defined by a PingOne (SP) Entity ID used as the issuer PingOne sends to the external identity provider, an Assertion Consumer Service endpoint that receives the SSO token, and a signing certificate confirming the request came from PingOne. We test whether the signature, issuer and audience on an incoming assertion are actually validated, and whether an expired or swapped signing certificate would still be accepted.
OIDC Connection Discovery, Issuer and JWKS Trust
An OIDC connection is built from a client ID and secret, an issuer, authorization endpoint and JWKS endpoint, either entered manually or pulled from a discovery document, plus a population that can override the authentication policy’s registration population and enable just-in-time account creation. We test whether tokens are verified against the issuer and keys you actually configured, and whether just-in-time registration creates accounts with more access than intended.
Redirect URI and Audience Matching
PingOne rejects a redirect URI that does not exactly match what an application has configured, though a wildcard entry or a loopback address can widen that match beyond a single path or port. We test every redirect URI and resource audience configured against what each application actually needs, and whether a wildcard or loopback entry left over from development still validates in production.
Access Token and ID Token Lifetimes
Access token lifetime is set per custom resource and defaults to one hour if nobody changes it, so a token issued for a short-lived task can outlive the session that requested it. We test the lifetime configured for every resource against how the application that consumes it actually behaves, and whether a captured token stays valid longer than the risk justifies.
Resource Scopes and Claims Delivered to Applications
OIDC scopes are defined once on the global OpenID Connect resource and inherited by every application, though an individual application can override those attributes with its own custom claims delivered through the ID token, the UserInfo endpoint, or both. We test what claims each application actually receives against what it needs to make an access decision, and whether an override hands an application a claim it should never see.
MFA Policy Methods and Lockout Settings
An MFA policy sets which authentication methods an authentication policy can call on, plus method-specific settings such as how many failed passcodes are allowed and how long a user is locked out after too many failures. We test which methods are actually enabled for each population, whether a weaker method can be selected in place of a stronger one, and whether the failure and lockout settings hold up under a credential-stuffing style attempt.
Administrator MFA Enforcement on the Admin Console
PingOne administrators who sign in to the admin console through a native PingOne sign-on policy are required to have a second authentication method registered, following a default sign-on policy change applied across environments that had not already enabled admin MFA. We test whether that enforcement actually covers every environment in scope, and where admin access instead runs through a federated external identity provider, whether that separate path carries an equivalent MFA requirement.
Administrator Role Scope and Assignment Level
A built-in role such as Organization Admin, Environment Admin, Identity Data Admin or Application Owner can be assigned to a user, group, worker application or PingFederate gateway, and depending on the role, that assignment can sit at the organisation, environment, population, group or application level. We test what each admin, worker application and PingFederate gateway is actually assigned against the job it does, and whether a role scoped to sound narrow, such as Application Owner, still reaches more applications than the job requires.
Worker Application Roles and API Access
A worker application holds no administrator roles by default, and once an admin adds roles to it, that worker application can act at any level and with any permission its own admin is entitled to grant, since a token issued to it authenticates its API requests under those roles. We test the roles held by every worker application against what its integration actually calls, and whether a worker application built for one task can now reach organisation-wide administration through roles nobody has reviewed since.
PingFederate and PingAccess Configuration for Self-Managed Deployments
Where PingFederate runs self-managed rather than as part of PingOne, whether installed on your own infrastructure or deployed as PingOne Cloud Software containers, it bridges an identity provider to a service provider through IdP and SP connections, authentication policy contracts and adapter mappings, while PingAccess sits in front of the resulting applications and APIs and applies its own application- and resource-level policy before a request reaches the backend. We test the connections, contracts and PingAccess policies your team has configured, never the PingFederate or PingAccess software itself.
OUR PROCESS
Ping Identity Security Review: From Scope to Attestation
Scope and Access
We agree which PingOne environments, PingFederate or PingAccess instances and admin accounts are in scope, plus at least one login for each distinct role and privilege tier you use.
Configuration and Connection Mapping
We map every SAML and OIDC connection, resource scope, token lifetime and administrator role assignment against what each one is actually meant to allow.
Manual Testing
A CREST-certified tester manually tests federation trust, token handling, MFA enforcement and admin role boundaries, chaining findings where they compound.
Attestation and Retest
You get a technical report with CVSS scores and reproduction steps, a walkthrough call, a free retest once fixes are deployed, and an attestation letter for auditors.
CREDENTIALS
Verified Accreditations Auditors Accept
Every credential below is independently verifiable. UK procurement teams, FCA supervisors, ISO 27001 / SOC 2 auditors, and cyber insurance underwriters all recognise these standards.
GET YOUR QUOTE
Get a CREST Ping Identity pen test quote in 24 hours
A fixed-price quote back in one business day, from a named CREST assessor. No sales pipeline, no chasing.
- CREST and IASME accredited. Testing your auditors and clients already recognise.
- Fast-track testing within 24 hours where required. Free retest of every fix included.
- Live findings via your client portal, not a four-week PDF.
- Fixed price from £3,500 for a single-role, single-app scope, agreed up front. Most engagements run £5,000 and up. No day-rate surprises.
Dan WilcocksonFounder, CelloriUnder NDA Further named references available on a scoping call.
- We reply within one business day with a fixed-price quote from a named CREST assessor.
- You approve the scope and we book a start date, usually within 24 hours.
- Live findings land in your client portal as we test, with a free retest of every fix.
Get your fixed pen test quote in 24 hours
Quote request received
We will reply within one business day with your fixed-price quote from a named CREST assessor.
Your data stays with us. No newsletter signup.
or book a 20-min scoping call first
We reply within one business day. Your data stays with us. No newsletter signup.
COMPLIANCE READY
Reports Mapped to Every Framework
Findings are written so your team can reference the report against each framework without translation work.
ISO 27001:2022
Annex A.8.8 management of technical vulnerabilities plus A.5.15-5.18 and A.8.2-8.5 access control validation.
SOC 2 Type I & II
CC6 logical access, CC7 system operations, CC8 change management evidence.
PCI DSS
Requirement 11.4 application penetration testing across cardholder data environments, including ecommerce penetration testing for online retail platforms.
FCA SYSC
SYSC 4.1.1R, 6.1.1R, 13 mapped to each finding for FCA-regulated firms.
UK GDPR
Article 32 effectiveness testing, customer-data security controls, ICO-acceptable evidence.
Cyber Essentials Plus
Direct certification through our IASME body status, single-vendor delivery.
PRICING
Transparent Ping Identity Security Review Pricing
Pricing depends on the number of roles, integrations and environments in scope. See our pricing page for how we quote.
2 to 3 testing days
Single user role, basic CRUD application, marketing website with auth. Around 5 working days from kickoff to report.
Get a fixed quote3 to 5 testing days
Multi-role SaaS, business application with payment integration. Around 8 to 12 working days from kickoff to report.
Get a fixed quote5 to 7 testing days
Multi-tenant platform, complex authorisation matrix, integration-heavy applications. Around 15 to 20 working days from kickoff to report.
Get a fixed quoteSECTORS
Sectors We Test Ping Identity For
Sector-specific scoping for regulated UK organisations.
Fintech & FCA-Regulated
FCA SYSC, Open Banking FAPI 1.0, PSD2 SCA, payment-flow scrutiny, KYC/AML testing.
Fintech sector pageSaaS Companies
SOC 2 Type I & II evidence, multi-tenant boundaries, role escalation, customer-tenant isolation.
SaaS sector pageLaw Firms
SRA Cyber Standard, privileged data, conveyancing fraud defence, partner-tier procurement.
Law firm sector pageHealthcare
NHS DTAC, DSP Toolkit v6, UK GDPR Article 32, EHR systems, telehealth platforms.
Healthcare sector pageInsurance
FCA / PRA Operational Resilience, cyber underwriting, claims data, broker portals.
Insurance sector pagePublic Sector
CCS / G-Cloud framework, NCSC-aligned, citizen-facing services, PSN-compliance scrutiny.
Public sector pageWHY EJN LABS
What You Get From Ping Identity Security Review
Six concrete differentiators competitors don’t all match.
CREST-Certified Testers, Verifiable
Every test by a CREST-certified pen tester (CRT, CCT APP, CCT INF where applicable). Verify our company status at crest-approved.org.
24-Hour Startup, Where Required
From signed scope to active testing in a single business day for incident response, audit deadlines, or regulator-driven timelines.
Live Findings, Not 4-Week PDFs
Critical issues reported during testing through your client portal. Your team remediates while testing continues.
Audit-Ready Reports
Executive summary plus full technical report with CVSS scores and explicit framework mappings (ISO 27001, SOC 2, PCI DSS, FCA SYSC).
Free Retests, Standard
Verify remediation of every finding before close-out. Letter of attestation for audit submission included. Most competitors charge £1,500-£3,000 per retest.
UK-Based CREST Testers
Every engagement performed by vetted, UK-based CREST-certified testers, matched to your needs, security clearance, and compliance scope.
FAQ
Frequently Asked
What access do you need to test our Ping Identity deployment?
We need at least one account for each distinct role you use in PingOne or PingFederate, including an environment or organisation admin login, plus standard user accounts for each population or application you want tested. Read access to your current SAML and OIDC connection settings speeds up several checks but is not required to start.
Will testing touch our live data?
Testing focuses on connections, tokens, MFA policies and admin roles rather than the content of user records. Where proving a finding needs a real sign-in or a test account, we agree the exact test data with you first and remove anything we create once testing is complete.
Is this hosted on our infrastructure or Ping Identity’s?
PingOne runs on Ping Identity’s infrastructure, so there is nothing for you to host for that part of the review. Where you run PingFederate or PingAccess self-managed, we test the server and its configuration on whichever infrastructure you have deployed it to, cloud or on-premises.
How long does a Ping Identity security review take?
A single PingOne environment or PingFederate deployment with a typical number of connections and applications sits in our 2-day single-tenant scope, with a report usually landing around 5 working days after kickoff. More SAML and OIDC connections, additional populations, or a combined PingOne and self-managed PingFederate or PingAccess estate extends that scope.
What is out of scope for a single-tenant review?
Testing Ping Identity’s own PingOne infrastructure or data centres is never in scope, and we do not run denial-of-service testing against any Ping Identity service. A separate application that only happens to authenticate through your Ping Identity deployment is scoped and quoted as its own engagement.
Does Ping Identity have a customer penetration-testing policy we need to follow?
Ping Identity publishes a penetration and load-testing policy for PingOne Advanced Identity Cloud, which limits customers to testing their own staging and UAT environments and caps each test plan at two weeks; that policy is written for Advanced Identity Cloud specifically, a different product line from the PingOne platform and self-managed PingFederate or PingAccess deployment covered by this review. We confirm Ping Identity’s current terms and any account-specific conditions for your deployment during scoping.
Do you need our source code or standing admin access?
No. There is no application source code to review in a standard PingOne environment, and PingFederate or PingAccess configuration is reviewed through the admin console rather than the underlying code. We test with the role accounts and access you provide, and do not need standing admin access beyond what is needed to verify a specific finding during the engagement.
Are your testers CREST certified?
Yes. Every Ping Identity engagement is carried out by UK-based, CREST-certified testers, and your report and attestation letter are recognised by auditors and insurers accordingly.
20+ CREST-accredited testing services in one place
Web, mobile, API, cloud, AI, infrastructure, red team. Pick the test that fits your environment.
Get a fixed price for your Ping Identity deployment
Ping Identity federates trust to every application that relies on it, exactly as your PingOne or PingFederate configuration allows. We test the connections, tokens, MFA policies and admin roles you actually configured. CREST-certified testers, fixed price from £3,290 for a 2-day single-tenant scope, quoted within 24 hours.
