Know which services accept SAML
Identity platforms often expose several protocols and realms. List each SAML endpoint, the applications that use it and whether it must accept requests from the public internet. A sign-in endpoint can be important even when the administration console is private.
Keycloak CVE-2026-107602 involved SAML 1.1 parsing and an unauthenticated denial-of-service path. The precise product and build status must come from the vendor that supplies your Keycloak distribution.
Keep identity dependencies visible
Record the identity service version, cluster nodes, Java runtime, reverse proxy and authentication dependencies. Assign an owner to each component and subscribe to the supplier’s security notices.
Monitor authentication latency, worker use and CPU. A sudden change may affect many applications at once. Preserve logs and follow the incident process before restarting a service if evidence may be needed.
Patch and test sign-in flows
Install the vendor-confirmed fixed release and test SAML login, logout, session expiry and identity-provider connections. Confirm all cluster nodes run the same supported build.
Keep a recovery plan for identity outages. Document application owners and emergency contacts so teams can restore access without disabling security checks.
