Why PKCE must bind the authorization request, code, and verifier
Binding authorization codes and PKCE verifiers to one transaction without weakening downgrade checks.
Tag archive
Binding authorization codes and PKCE verifiers to one transaction without weakening downgrade checks.

A forthcoming webinar examines how a compromised identity can be used to gain broader privileges, and how AI can speed target identification, weakness expl
Scepticism about passkey onboarding is understandable. It is not a reason to evaluate today's...
🔐 Microsoft 365 Security: Revoking Sessions Is Not the Same as Blocking User Access An employee...
ShinyHunters claimed it used voice phishing against McKesson employees to take over Okta single sign-on accounts, then pulled roughly a terabyte from Salesforce and Snowflake environments. No exploit was required.

I was mapping out access for a mid-sized engineering org a while back, and we hit a wall almost...

Your organization has MFA. Your users have strong passwords. Conditional access is enabled. So how is...

Security teams have spent years adding more layers to authentication. Passwords were followed by...
Employees approve pushes that aren't theirs because tapping "Approve" has become a reflex, not a...

Your security team knows how many employees have access to your systems. But do you know how many AI...
Block device-code phishing in 2026: the Entra ID, Okta, GitHub and Google Workspace...

Originally published at norvik.tech Introduction An in-depth analysis of Okta's...