Skip to content
Solvex Space
Cloud / DevSecOpsFrom $1,999 · quoted to scopeSigned authorization

Identity, Authentication & Passkey Review

Credentials are the front door of every breach statistic. We review how your organisation and products actually authenticate — SSO, MFA, session handling, recovery flows — and build your migration path to phishing-resistant passkeys done right.

Verified Solvex Specialist

Verified by Solvex

Direct specialist contact for Solvex engagements

What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.

Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.

Signed authorization required. This engagement is performed only against systems you own or are contractually authorized to have tested, under an agreed scope. See the responsible testing policy.

What's covered

  • Authentication architecture review across workforce and customer identity
  • SSO and federation configuration: SAML/OIDC flows, token handling, trust relationships
  • MFA implementation strength: method quality, coverage gaps, fatigue-attack resistance
  • Account recovery and helpdesk reset flows — the classic MFA bypass
  • Session management: lifetime, revocation, concurrent-session handling
  • Passkey/WebAuthn readiness and phased rollout design

What you receive

  • Identity risk report: authentication weaknesses ranked by exploitability
  • Attack-path analysis for credential-based compromise of your estate
  • Passkey migration roadmap: platform support, user segments, fallback strategy
  • Recovery-flow hardening recommendations
  • Free retest of remediated authentication findings

Evidence and reporting

How the work is kept honest
  • Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
  • A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
  • Signed scope firstTesting starts only after written scope and signed authorization for systems you own or are entitled to have tested.

Anyone holding a Solvex report can verify it publicly without seeing its contents.

Our boundaries

What this engagement does not do, stated before it starts.

  • Testing only against identity systems you own or are authorised to assess
  • No social engineering of your helpdesk unless explicitly scoped
  • No access to production user credential stores — testing uses dedicated accounts
  • Identity platform licensing and procurement decisions remain yours

How this engagement runs

  1. 01

    Intake

    Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.

  2. 02

    Scope and authorization

    Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.

  3. 03

    Investigation or build

    Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.

  4. 04

    Evidence

    Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.

  5. 05

    Delivery

    A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.

  6. 06

    Verification and retest

    Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.

Questions we are asked

Are passkeys actually ready for real-world rollout?
Yes — platform support across Apple, Google and Microsoft ecosystems is now mature, and passkeys eliminate the phishing channel that defeats most MFA. The hard parts are rollout sequencing, fallback design and account recovery, which is exactly what the roadmap in this engagement covers.
We already have MFA everywhere. What would this find?
Usually the bypasses: recovery flows that reset MFA with a phone call, legacy protocols that skip it entirely, push-fatigue-prone methods, and sessions that outlive the credentials that created them. Attackers don't beat MFA head-on — they walk around it, and so do we.
Does this cover customer-facing login as well as employee identity?
Both, and they're assessed differently: workforce identity centres on SSO, federation and privileged access; customer identity centres on registration abuse, credential stuffing resistance, session handling and a passkey experience users will actually adopt. Scope can cover either or both.