A customer portal holds information your public website does not: invoices, account history, billing settings, and administrative controls. Testing it requires access to the roles and tenants that use those functions. Scope the portal assessment around what each account should be able to read and change.
Why a login screen changes the entire threat model
Test the public login flow and the functions behind it. A compromised customer account should remain limited to that customer’s authorized data and actions. The assessment needs to verify those limits directly.
An unauthenticated scan cannot compare the permissions of signed-in users. Provide test accounts for the relevant roles and tenants so the assessor can examine the portal’s daily workflows.
Scoping the engagement before testing starts
Agree the accounts, environments, integrations, and permitted methods in writing before testing starts.
Provide separate accounts for standard users, billing administrators, owners, and support or reseller roles where relevant. Include lower-privilege accounts; testing only as an administrator can miss restrictions between ordinary roles.
Record which environment is tested and how it differs from production. If testing uses staging, identify production-specific sessions, configuration, and integrations that need separate evidence. Agree any limits before the report is written.
Which integrations are included has to be decided early too. Billing portals commonly hand off to a payment processor, an identity provider, or a support tool. Deciding whether those integration points sit in scope, and what data crosses that boundary, changes both the risk profile and what you're contractually allowed to test.
None of it starts without written authorization covering every account and access level involved. Authenticated testing means someone is deliberately trying to break your access controls using credentials you provided. That needs explicit sign-off on the accounts, the testing window, and the methods permitted, before anyone touches the portal.
Once that scope is set, the engagement can run as a fixed-fee audit for a single application and role, or as a broader engagement covering multiple roles, environments, and the kind of authenticated penetration testing a multi-tenant billing system usually needs.
Session handling: where authenticated attacks start
Check token unpredictability, session lifetime, logout, password changes, and administrative revocation. Define which sessions should stop after each event, then test that behavior from more than one client.
Test password-reset tokens for account binding, expiration, reuse, and concurrent submissions. Confirm that changing an account identifier cannot redirect the reset to another user. Include administrator and support reset routes if the product offers them.
Inspect Secure, HttpOnly, SameSite, and domain scoping on authenticated session cookies. Use a signed-in test account to check the cookies issued after login and the effect of logout. Public-page results may not cover those cookies.
Access restrictions and broken access control
Test horizontal access by requesting another customer’s records with an ordinary account. Test vertical access by attempting a higher-role action with a lower-role account. For example, an invoice endpoint must check who owns the invoice as well as whether the requester is signed in.
Test the API with credentials for each role. A hidden administrator button does not stop a direct request to its endpoint. Verify the server’s role and record-ownership decisions, then inspect the resulting state.
Sensitive information the portal is holding
List the data the portal handles: invoices, payment-related records, personal information, usage history, and internal support notes. Identify the sensitivity and applicable handling requirements for each instead of treating every field alike.
Inspect API responses as well as rendered pages. Check fields the interface hides, generated invoices, exports, and attachments for ownership enforcement. Review error responses for unnecessary internal details and verify downloads with a second customer account.
Exposed interfaces beyond the visible dashboard
Map APIs used by mobile clients, integrations, and the browser, including unused or internal endpoints that remain reachable. For GraphQL, review the available queries and mutations and test their authorization. Schema visibility can help discovery, but hiding it does not enforce permissions.
Admin panels and internal tooling are the other half of this. A support dashboard, an internal admin route, or a staging subdomain that was never meant for customer traffic still counts as part of the portal's attack surface if it's reachable and tied to the same authentication system. Scoping the assessment means mapping every interface that talks to the portal's backend, not only the ones customers are handed a link to.
Tenant isolation: the risk unique to multi-tenant SaaS
Multi-tenant products often share databases, search indexes, and caches. Trace how tenant context reaches each query and background job. A correct check on the dashboard can coexist with a missing check in an export or search path.
Use separate test tenants to vary identifiers in requests and verify server-side enforcement. Include search, exports, reports, jobs, and tenant-specific subdomains. Record which data was reachable in a failed case rather than assuming every isolation flaw exposes every customer.
What an external assessment can see, and where it stops
An unauthenticated review can inspect the login page, TLS, public APIs, exposed subdomains, and controls on repeated login attempts. Keep that coverage in the report, along with the account-dependent functions it did not test.
Add authenticated testing to compare sessions, roles, and tenants. A clean public scan does not establish whether a customer can retrieve another customer’s invoice or invoke an owner-only action.
Vulnerability assessment, pentest, or quarterly audit: matching the method to the portal
Ask which techniques the engagement includes. Identification, validation, and attempted exploitation can require different access and permissions. For portal findings, request evidence showing the role used, target record, action attempted, and observed result.
Repeat the relevant tests when adding endpoints, roles, or integrations. Schedule broader reviews around the portal’s change rate and applicable obligations. Keep the tested version and date visible so an older report is not mistaken for evidence about a new release.
What you get back
The report should identify the tested endpoints, roles, tenants, and exclusions. Each finding needs reproduction evidence, a severity rationale, and remediation guidance. Include a concise risk explanation for leadership and retest criteria for engineering.
Getting started
Start by listing the portal functions and customer roles you need verified. Combine public checks with authenticated tests of account permissions and tenant separation. After remediation, keep a repeatable set of cases for future releases.