Vulnerability Assessment · Service

Authentication and access review.

Who can log in, how they prove it, and what they can reach once inside. We test each of these and show you where the boundaries do not hold.

Overview

What this covers

Many breaches do not begin with a sophisticated technical flaw. They begin with a login: a reused password, a reset process that can be misused, a session that never expires, or an account that can do more than it should. Once inside, an attacker looks for ways to reach other users' data or to gain administrator rights.

This review focuses on that path. We examine your login and registration flows, password reset and account recovery, multi-factor authentication and how it can be bypassed or downgraded, session management, and the boundaries between user roles. The aim is to confirm that each user can only do what their role allows, and that moving from one role to a more powerful one is not possible without proper authorisation.

The review can cover a single application or several systems that share a login, such as a customer portal and an internal admin tool. Findings come with specific fixes and, where useful, policy recommendations for passwords, MFA and access reviews.

Deliverables

What you get

Scope and role map

A signed scope listing the systems and roles in the review, and a map of what each role is meant to be able to do.

Findings report

Every issue in login, recovery, MFA, sessions and role boundaries, rated by severity with evidence and steps to reproduce.

Fix guidance

Specific changes for developers and administrators, with references to the relevant OWASP guidance.

Policy recommendations

Practical suggestions for password, MFA and access review policies, based on what we found rather than a generic template.

Retest and confirmation

We retest the fixed issues and confirm in writing which are closed.

Approach

How we run it

  1. 01

    Agree the scope

    We confirm the systems, roles and test accounts involved, and any limits such as avoiding account lockouts on production.

  2. 02

    Map the roles

    We document what each role should and should not be able to do, with your team's input.

  3. 03

    Test

    We work through login, recovery, MFA, sessions and every role boundary in scope.

  4. 04

    Report and walk through

    Findings are written up and explained to your team, with an agreed order for fixing.

  5. 05

    Retest

    We check the fixes and confirm the result in writing.

Questions

Before you ask.

Will testing lock out real users?

No. We test with dedicated test accounts, and any checks on lockout or rate limiting are carried out carefully and only on accounts agreed in the scope.

Do you review our identity provider, such as Microsoft Entra ID or Okta?

We can review how your applications use an identity provider and, with read-only access, how relevant policies are configured. The details are agreed in the scope.

How many test accounts do you need?

Typically two accounts for each role in scope, so we can check both what a role can do and whether one user can reach another user's data.

How are timelines and prices agreed?

They depend on the number of systems and roles. Both are set out in the scope and quote before we begin.

Talk to us about authentication & access

Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.