Keycloak Penetration Testing for Self-Hosted Identity
Running Keycloak yourself means the configuration, the patching and the exposure are all yours. We pen test the realm you built and the server you built it on, because an admin console reachable from the internet undoes everything else. CREST-certified testers, fixed price from £2,970, scoped in 24 hours.
- Unlimited retesting
- No rescheduling or cancellation fees
- Fixed quote within 24 hours
“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.”
Imran SaghirProject Lead, SquareOne“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.”
Dan WilcocksonCo-Founder, CelloriWith a hosted identity provider you inherit someone else’s patching and exposure. With Keycloak you inherit neither, and the questions that follow are yours alone: which version are you on, is the admin console reachable, and what is the master realm’s exposure.
Why self-hosting identity changes the question
The realm configuration then behaves much like any identity platform. Client settings decide which grant types are permitted and whether redirect URIs are properly constrained, and protocol mappers decide what ends up in a token. A mapper that copies a user attribute into a roles claim is a privilege escalation waiting to be found.
Keycloak is one of several identity platforms we publish pages for, and the approach is the same whether you host it yourself or not: pen test what the configuration actually permits rather than what it appears to say.
ISO 27001, SOC 2, PCI DSS and Cyber Essentials Plus audits accept manual penetration test evidence. Scan-only evidence is generally insufficient.
REALMS, CLIENTS + MAPPERS
What we actually pen test on a Keycloak deployment
Manual pen testing across realm and client configuration, token mappers and scopes, the admin console, identity brokering and the server underneath it.
Admin console and master realm
Whether the admin console is reachable from the internet, master realm separation, default and weak administrative credentials, and what a realm administrator can do beyond their own realm.
Client configuration
Grant types enabled per client, redirect URI validation and wildcards, public versus confidential client handling, PKCE enforcement, and client secrets that have never been rotated.
Protocol mappers and scopes
Every mapper examined for user-controlled attributes reaching role or permission claims, default and optional client scopes, and whether a token can be made to carry more authority than the user holds.
Token and session handling
Access and refresh token lifetimes, offline tokens, session invalidation on logout and password change, token exchange configuration, and signature and audience validation at the resource server.
Identity brokering and federation
External identity providers, LDAP and Active Directory federation, whether brokered accounts can link to existing local accounts, and first broker login flows that skip verification.
Server and deployment hardening
Keycloak version against known vulnerabilities, TLS configuration, database and credential storage, container and reverse proxy configuration, and whether management endpoints are exposed.
METHODOLOGY
Keycloak Penetration Testing: From Scope to Attestation
CREST-aligned methodology built on OWASP Web Security Testing Guide, OWASP ASVS, NIST SP 800-115, and PTES. Each finding maps to all four standards plus your specific compliance regime.
Reconnaissance
Application mapping, technology fingerprinting, content discovery, parameter enumeration, authentication-flow analysis, role-matrix construction.
Vulnerability Assessment
Authenticated and unauthenticated automated scanning across every user role, plus targeted manual checks for known weakness patterns.
Manual Exploitation
Hands-on testing by a CREST-certified pentester. Business-logic exploitation, chained vulnerabilities, privilege escalation, impact validation.
Reporting + Retest
Executive summary, technical report with CVSS scores and reproduction steps, walkthrough call, free retest after remediation, attestation letter.
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 Keycloak 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 WilcocksonCo-Founder, 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 explicitly tagged to the relevant control reference. Your audit team submits the report directly 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 Keycloak Penetration Testing Pricing
Pricing depends on app complexity, user-role count, business-logic depth, and integration surface. The day count flexes; the included deliverables stay the same across all engagements.
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 quotePart of Technologies We Pen Test. These are examples of the stacks we publish pages for, not a complete list. If yours is not here we still test it. Related pages:
BY SECTOR
Keycloak Penetration Testing for Your Sector
Sector-specialist scoping for UK businesses with sector-specific compliance regimes and threat models.
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 Keycloak Penetration Testing
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
Which Keycloak versions do you test?
All current and recent versions, including legacy WildFly-based deployments still in production. Version matters here more than with a hosted platform, so we establish it from behaviour and check it against known vulnerabilities.
Do you need admin access to the realm?
Read access to the realm configuration makes the test considerably more useful, since mappers and client settings are where most findings live. We also want two standard accounts in different roles.
Is the underlying server in scope?
By default we cover the Keycloak deployment: version, TLS, exposure and the reverse proxy in front of it. Full infrastructure testing of the host and network is our internal or external infrastructure service and we can scope it alongside.
What if we use Keycloak only for internal applications?
Still worth testing, and the emphasis shifts. Internal deployments tend to have weaker admin console protection precisely because they are assumed unreachable, and assumed unreachable is a claim worth verifying.
Do you offer a retest?
Unlimited free retesting until every finding closes, with no time limit and no fee, plus a walkthrough call when the report lands.
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 Keycloak deployment
Tell us the version, how many realms and clients you run, and whether the host is in scope. Fixed-price quote from a named CREST assessor within one business day.
