A security assessment goes well when both sides agree, in writing, on what will be looked at and what will not. Most of the preparation is deciding those things before anyone opens a tool. This guide applies whichever provider you choose.
Decide what you want to learn
Start with the question, not the tool. "Are our customer records exposed?" leads to a different scope from "is our cloud account configured sensibly?" Write down the one or two questions that matter most. A good provider will shape the scope around them and tell you what the assessment cannot answer.
Put the scope in writing
List exactly what is in scope:
- Applications, with their URLs and environments.
- Servers, networks and address ranges.
- Cloud accounts and the services inside them.
- Domains and subdomains.
Then list what is out of scope. Systems run by someone else are the usual candidates: a payment provider, a hosted email service, a partner's API. You can only authorise work on systems you own or have written permission to test.
Get authorisation in writing
No reputable provider should begin without signed authorisation, and you should not want them to. A verbal "go ahead" protects nobody. The authorisation should state:
- The systems, addresses and domains in scope.
- The dates and times when work may take place.
- The techniques that are permitted, and those that are prohibited.
- Emergency contacts on both sides.
- How any data seen during the work will be handled.
- What the report must contain.
- The conditions under which work stops immediately.
Check your providers' rules
Hosting companies and cloud platforms publish policies on security testing. Some need advance notice and some restrict particular kinds of testing. Read the policy for each platform in scope before the dates are fixed.
Name your contacts
Choose one person who can answer questions during the work and one who can be reached urgently if something unexpected happens. Tell your own team that an assessment is planned, so that an alert during the window is handled calmly.
Share access safely
If the assessment needs accounts or reviewer access:
- Create dedicated accounts for the work. Do not share a personal login.
- Give the least access the scope needs.
- Send credentials through an agreed secure channel, never by email or through a web form.
- Remove the accounts when the work is finished.
Take a backup first
Assessments are designed to avoid disruption, but confirm that recent backups exist and can be restored before work begins on anything important. If a production system is fragile, say so. The scope can be adjusted, or a test environment used instead.
Plan for the report
Decide who will receive the report, who will own each finding and when you will review progress. A report with no owner does not get fixed. Ask for a walkthrough so your team can question the findings while the detail is fresh.
A short checklist
- The questions you want answered are written down.
- The scope lists what is in and what is out.
- Authorisation is signed by someone entitled to give it.
- Provider testing policies have been checked.
- Contacts are named on both sides.
- Access is dedicated, limited and shared securely.
- Backups have been confirmed.
- The report has an owner and a review date.
This is how we run our own engagements. If you would like us to scope one for you, book a discovery call.
