A customer portal can require a login and still expose the wrong records. For a UAE distributor serving several companies, the important question is whether every invoice, attachment and update belongs to an account that the signed-in person may access. Hiding another customer’s invoice in the menu does not establish that boundary.

Write the access rule in business language

Start with a small permission matrix. A customer buyer might view invoices for one company, an accounts manager might cover several approved branches, and an internal employee might manage a defined portfolio. Record which actions each person can perform: view, download, edit or approve. Treat an invoice PDF as a protected resource in its own right.

Resolve ambiguous relationships before development. If a staff member leaves a customer company, who removes their access? If a buyer moves between branches, should their previous branch remain visible? Give each exception an owner and an expiry or review point rather than adding permanent broad access.

Enforce permissions where records are retrieved

The OWASP authorization guidance distinguishes identity verification from permission to use a resource. It recommends denying access by default and validating permissions on every request. A long or unpredictable invoice identifier can reduce guessing; it does not replace the permission check.

Ask the development team how the server checks the current user, customer relationship, requested record and action. Include direct downloads, exports, search results and background tasks in that discussion. The browser’s selected company should not be trusted as proof that the person belongs to it. Apply the same boundary when an attachment is stored outside the application server.

Test allowed and denied cases with safe records

  1. Create two synthetic customer companies in an authorised test environment. Give each an invoice and an attachment with distinct harmless content.
  2. Verify that each customer can complete the permitted tasks, then have the developer exercise the other customer’s record and download routes. The response must disclose no protected content and make no unauthorised change.
  3. Repeat for reassigned staff, expired access, exports and mobile views. Check that cached pages or files do not reveal a previous user’s data after sign-out.
  4. Keep these cases in release checks. A newly added invoice endpoint needs the same protection as the original page.

OWASP’s authorization testing matrix approach helps turn roles, resources and expected outcomes into repeatable tests. Such checks support a wider security review; they do not prove the whole portal is secure.

Make the review useful to the business

Keep an appropriate record of access failures and administrative changes without copying private invoice content into logs. The application audit trail guide covers investigation evidence, while the CRM ownership guide helps define responsibility for customer records.

ITZ’s custom software development service can help map portal roles and record boundaries. Describe the customer and branch relationships your portal must respect.

Review your portal access rules

Bring a role list, a redacted invoice workflow and examples of permitted sharing. Discuss the checks and test cases needed before adding more customers. Review Your Portal Access Rules