Start with the assets and permission
List the domains, subdomains, applications and environments that are in scope. Include third-party services only when you have permission to test them. A written scope should identify the systems, testing window, excluded areas and a contact who can pause the work if something behaves unexpectedly.
If the site is hosted by a provider or includes payment, identity or marketing integrations, confirm the provider’s testing rules before active checks begin. Ownership of the website does not automatically grant permission to test every connected service.
Review how the site handles real user journeys
A review should follow the actions people actually take: signing in, changing account details, uploading files, placing an order or accessing records. The relevant checks depend on the features and the type of information the site handles.
Automated tools can help identify known patterns and exposed components. Manual review is needed to understand access rules, validation and how different steps work together. A scanner output on its own does not explain whether a finding is reachable or what it means for the business.
Ask for findings your team can act on
A useful report states the affected asset, the steps used to confirm a finding, the evidence collected, the potential consequence and a practical remediation direction. Findings should be prioritized with enough context for the owner to decide what to address first.
Agree on how urgent issues will be raised, how sensitive evidence will be handled and whether a retest is included. A retest checks the agreed fix; it is not a guarantee that every weakness in the application has been removed.
Before the assessment
Prepare a list of URLs and key functions, name the business and technical contacts, and arrange test accounts if authenticated journeys are in scope. Tell the assessor about planned releases or production constraints. Clear preparation helps the work focus on the systems and questions that matter to your team.
