Penetration testing scope: a web application template to fill in before you ask for quotes
A scope schedule you can copy and complete for any provider: exact URLs and API paths, environments, roles and route counts, test accounts, third-party services, source addresses, data limits, exclusions and the retest boundary.
A completed example for an invented two-role software product shows every part filled in.
On this page
Web application scope schedule, blank and completed
Copy the blank schedule into a document and fill in all twelve parts before you ask any provider for a quote. Write exact hostnames, paths, counts and names rather than descriptions, and write "none" where a line does not apply.
How to use itHide the instructions
Below it, the same schedule is filled in for an invented two-role software product, as an illustration rather than a client, so you can see the level of detail each line needs.
penetration-test-scope-template.txt
Introduction2 lines
Part 1. The test and who owns it7 lines
Part 2. Targets in scope8 lines
Part 3. Environments6 lines
Part 4. Roles, organisations and records5 lines
Part 5. Test accounts and access6 lines
Part 6. Third-party services and hosting10 lines
Part 7. Source addresses and monitoring3 lines
Part 8. Data limits7 lines
Part 9. Exclusions4 lines
Part 10. Changes during testing3 lines
Part 11. Retest boundary5 lines
Part 12. Attachments and sign-off4 lines
Completed example: an invented two-role software product83 lines
Whole template180 lines
WEB APPLICATION PENETRATION TEST SCOPE SCHEDULE
Fill in one schedule for each application. Write exact values rather than descriptions: a hostname, not "the portal"; a count, not "a few". Where a line does not apply, write "none" so the provider can see it was considered. Send the same completed schedule to every provider you ask to quote, and attach the signed authorisation letter and the rules of engagement before testing starts.
PART 1. THE TEST AND WHO OWNS IT
1.1 Business name: ____
1.2 Person who owns this scope (name, role, phone): ____
1.3 Application name and what it does, in one sentence: ____
1.4 Why it is being tested, and who asked (paste their exact wording): ____
1.5 Who will read the report (developers / a customer / an insurer / an auditor / a tender panel): ____
1.6 Date the report is needed by: ____ (testing dates are set in the statement of work)
1.7 Built by: ____ Hosted by: ____ (a provider that built or hosts the application is not independent of it)
PART 2. TARGETS IN SCOPE
2.1 Web front ends, the full URL of each (list the bare domain and www separately if both answer): ____
2.2 API base URLs and paths, with the version of each: ____
2.3 Older API versions or paths still deployed (write "none" only after checking): ____
2.4 Other hostnames the application uses (file download links, websocket endpoints, webhook receivers): ____
2.5 Route list attached: yes / no. Taken from (route definitions in the code / API schema export / other): ____ Build or commit: ____
2.6 Routes that accept input or return data that is not public. Total: ____
Of these: upload files ____ payments ____ send email or SMS ____ export data ____ change roles or permissions ____
2.7 Hostnames on the same domain that are NOT in scope, and who runs each: ____
PART 3. ENVIRONMENTS
3.1 Staging URLs: ____ Build: ____
Data held (synthetic / masked copy of production / unmasked copy of production): ____
Shared with production (database / file storage / sign-in tenant / payment account / none): ____
3.2 Production URLs: ____
Testing allowed in production (none / checks that need no account and change nothing / signed-in testing with test accounts only): ____
3.3 Differences between staging and production the tester should know about (features switched off, integrations stubbed): ____
PART 4. ROLES, ORGANISATIONS AND RECORDS
4.1 Roles in scope. For each: role name ____ what it may do, in one line ____ number of routes it can call ____
4.2 Roles that exist but are excluded this time, and why: ____
4.3 Separate customer organisations in one database: yes / no. Test organisations provided: ____
4.4 Kinds of record the application keeps, and who owns each (a user, an organisation, or both): ____
4.5 Business rules the server must enforce, one per line (limits, steps that must happen in order, actions allowed only once): ____
PART 5. TEST ACCOUNTS AND ACCESS
5.1 Two accounts for each role in 4.1, in two organisations if 4.3 is yes. One line per account:
Username ____ Role ____ Organisation ____ Environment ____ Multi-factor sign-in on: yes / no
Username ____ Role ____ Organisation ____ Environment ____ Multi-factor sign-in on: yes / no
5.2 Accounts that may be locked, reset or deleted during testing: ____
5.3 How credentials will be handed over (not in plain email): ____ Who disables the accounts afterwards, and when: ____
5.4 Extra access offered (none / API schema / read-only code access to named areas): ____
PART 6. THIRD-PARTY SERVICES AND HOSTING
Your business can authorise testing only of what it controls. List every outside service the application runs on, calls, loads in the browser, or points one of your hostnames at, and repeat this block for each one.
6.1 Service: ____ What it does for the application: ____
Who runs it: ____ Data exchanged, and how sensitive it is: ____
Yours to authorise (your code that calls it, your account settings): ____
Belongs to the vendor or host, so not in scope: ____
Permission, one of: published testing terms read on ____ by ____, allowing ____
written permission from the vendor, dated ____ (attach it)
excluded, because ____
6.2 Hosting provider: ____ Account held by: ____
Testing terms read on ____ by ____ Notice or approval they ask for: ____ Given on: ____
PART 7. SOURCE ADDRESSES AND MONITORING
7.1 Addresses the test traffic will come from (supplied by the provider): ____
7.2 Firewall, bot protection or rate limits to let those addresses through, and in which environment: ____
7.3 Who watches alerts and must be told testing is under way (your team, your host, a monitoring service): ____
PART 8. DATA LIMITS
8.1 Real personal information in the test environment (none / masked / yes, saying what): ____
8.2 Records the tester may create, change or delete, and how test records are marked: ____
8.3 Records and accounts that must not be touched: ____
8.4 Test uploads: largest file ____ most files ____ file types ____
8.5 The only email addresses and phone numbers messages may go to (the tester's own): ____
8.6 Payments in test mode or a non-live account only: yes / no. Details: ____
8.7 Evidence: where it is stored ____ what is redacted ____ when it is deleted ____
PART 9. EXCLUSIONS
One line each, with a reason code. O: owned by someone else. L: adds effort, to be scoped later. S: needs a different kind of specialist. R: too risky in the environment offered.
9.1 Excluded: ____ Reason code: ____ Decided by: ____
9.2 Excluded: ____ Reason code: ____ Decided by: ____
9.3 Excluded: ____ Reason code: ____ Decided by: ____
PART 10. CHANGES DURING TESTING
10.1 Person who may approve, in writing, adding a route or hostname found during testing: ____
10.2 If nobody approves it in time, it is (reported and recorded as a limitation / other): ____
10.3 Build frozen during testing: yes / no. If no, what will change and where: ____
PART 11. RETEST BOUNDARY
11.1 The retest covers (the findings reported from this scope / other): ____
11.2 Environment and build the fixes will be deployed to: ____
11.3 Window for requesting the retest: ____ (from the statement of work)
11.4 Accounts and test data kept for the retest: ____
11.5 Not covered by the retest (new features, routes added after sign-off, excluded items): ____
PART 12. ATTACHMENTS AND SIGN-OFF
12.1 Attached: route list ____ permission matrix (a row for each function, a column for each role in 4.1, each cell marked allowed or refused) ____ signed authorisation letter ____ rules of engagement ____ vendor and host permissions ____
12.2 Technical contact during testing, available at short notice: name ____ phone ____
12.3 Agreed for the business: name ____ role ____ date ____
12.4 Agreed for the provider: name ____ date ____
COMPLETED EXAMPLE: AN INVENTED TWO-ROLE SOFTWARE PRODUCT
An illustration, not a client. The business, its hostnames and every value below were written for this page. The product records daily pre-start vehicle checks and defect reports, sold by subscription to small transport and equipment hire fleets. Fleet managers set up vehicles, drivers and checklists; drivers complete checks on a phone browser and report defects with photos.
1.1 Business: the invented software company that runs prestart.lab.test.
1.2 Scope owner: the operations director. The lead developer filled in Parts 2 to 5.
1.3 Application: a web app where drivers record pre-start checks and fleet managers act on the defects they report.
1.4 Reason: a transport customer's supplier questionnaire asks for "an independent penetration test of the application within the last 12 months" and evidence that high-risk findings were fixed.
1.5 Readers: the developers first, then the transport customer.
1.6 Report needed by: the questionnaire due date. Testing dates: set in the statement of work.
1.7 Built by: the company's own developers. Hosted by: a cloud account the company holds. The customer asked for independence, so the chosen provider had no part in either.
2.1 Web front end: https://app.prestart.lab.test. The bare domain redirects to the marketing site, excluded in 9.2.
2.2 API: https://api.prestart.lab.test/v2/ (34 routes).
2.3 Older versions: https://api.prestart.lab.test/v1/ still answers (11 routes). Nothing current calls it. In scope, so the report shows whether it applies the same checks as v2.
2.4 Other hostnames: https://files.prestart.lab.test, which serves defect photos through signed links.
2.5 Route list attached: yes, exported from the API schema and the route definitions on build 4182.
2.6 Total: 45 routes. Upload files 2, payments 2 (checkout request and payment notification receiver), send email or SMS 3, export data 2, change roles or permissions 2.
2.7 Not in scope on the same domain: www.prestart.lab.test (marketing site on a hosted website builder), help.prestart.lab.test (help desk vendor), status.prestart.lab.test (status page vendor), admin.prestart.lab.test (internal support console, see 4.2).
3.1 Staging: https://staging-app.prestart.lab.test and https://staging-api.prestart.lab.test, build 4182. Data: synthetic, loaded by a seed script. Shared with production: none. Separate database, storage bucket, sign-in tenant and payment test account, confirmed in writing by the lead developer.
3.2 Production: https://app.prestart.lab.test and https://api.prestart.lab.test. Allowed: checks that need no account and change nothing. All signed-in testing runs on staging.
3.3 Differences: SMS on staging goes to the delivery service's test mode. Both environments load map tiles from the same map service.
4.1 Roles in scope:
Fleet manager: adds vehicles and drivers, builds checklists, clears defects, exports reports, manages the subscription. Can call 29 v2 routes and 9 v1 routes.
Driver: sees assigned vehicles, submits pre-start checks, reports defects with photos, sees own history. Can call 10 v2 routes and 4 v1 routes.
Routes both roles can call are counted for each. Three v2 routes need no sign-in: invitation acceptance, the sign-in callback and the payment notification receiver.
4.2 Excluded role: the support console the company's own staff use. It adds a third role and a separate sign-in, so it will be scoped after this test.
4.3 Separate customer organisations in one database: yes. Test organisations: Fleet A and Fleet B, both on staging.
4.4 Records: vehicles, checklists, pre-start checks, defect reports, defect photos, exports and invoices. Every record belongs to an organisation. Pre-start checks and defect reports also belong to the driver who submitted them.
4.5 Business rules:
A driver can submit a check only for a vehicle assigned to them.
A submitted check cannot be edited, only annotated by a fleet manager.
A vehicle with an open critical defect cannot be assigned until a fleet manager clears the defect.
A fleet on the starter plan can register at most 15 vehicles.
Only fleet managers can invite drivers or change anyone's role.
5.1 Accounts on staging: mgr-a1, mgr-a2, drv-a1 and drv-a2 in Fleet A; mgr-b1, mgr-b2, drv-b1 and drv-b2 in Fleet B. Multi-factor sign-in on for every fleet manager account.
5.2 May be locked, reset or deleted: drv-a2 and mgr-b2 only.
5.3 Handover: a one-time share link from the company's password manager. The lead developer disables all eight accounts the day the retest closes.
5.4 Extra access: the v2 API schema. No code access this time.
6.1 Hosted sign-in service. Does: password sign-in, multi-factor sign-in and reset emails. Data: names, email addresses, role and organisation claims. Ours: how the API checks the tokens it receives, which claims it trusts, when sessions end, and our tenant settings. Vendor's: its hosted login pages and platform. Permission: terms read and saved with this schedule; the hosted pages are excluded.
6.2 Payment provider (subscriptions). Data: plan and billing contact; card details stay with the provider. Ours: the checkout request our server builds, the plan it charges for, and the route that receives payment notifications, all in the provider's test mode. Provider's: hosted checkout, card handling, dashboard. Permission: test mode only; the hosted pages are excluded.
6.3 Email and SMS delivery service. Data: driver names, phone numbers, defect summaries. Ours: how often the application will send, and to whom. Vendor's: the delivery platform. Permission: test mode on staging; messages only to the destinations in 8.5.
6.4 Map service. Data: depot addresses and vehicle locations. Ours: the browser key and the restrictions set on it in our account. Vendor's: the map service. Permission: excluded apart from our own key settings.
6.5 File storage, a bucket in our own cloud account. Ours: the bucket's access settings and the signed links the API issues. Provider's: the storage service. Permission: covered by the hosting terms in 6.8.
6.6 Help desk and status page vendors on help. and status. subdomains. Ours: the DNS records, checked to confirm each still points at an active account. Vendors': both products. Permission: excluded apart from the DNS check.
6.7 Error monitoring service. Data: front-end errors and request paths. Ours: what the application sends to it. Vendor's: the service. Permission: excluded; test errors will appear there and are expected.
6.8 Hosting provider: a container platform and managed database in a cloud account the company holds. Terms read by the lead developer and saved with this schedule. Any notice the terms ask for was sent and acknowledged before testing, with copies attached.
7.1 Tester's source addresses: 203.0.113.24 and 203.0.113.25 (documentation addresses used for this illustration).
7.2 Let through: the web application firewall and API rate limit on staging only. Production is left unchanged.
7.3 Told: the lead developer, the cloud account owner and the error monitoring alert channel, so test traffic is not escalated as an incident.
8.1 Personal information on staging: none. Names, numbers and addresses are synthetic.
8.2 May create, change or delete: any record in Fleet A or Fleet B on staging. Test records start "PT-".
8.3 Must not be touched: production records of every kind, and the template fleet the seed script copies from.
8.4 Test uploads: up to 10 MB each, at most 50 files, images and PDFs plus harmless files whose content does not match their extension.
8.5 Messages only to: two inboxes and two mobile numbers the tester controls, listed in the rules of engagement.
8.6 Payments: test mode only.
8.7 Evidence: stored by the provider under its data handling terms, with tokens, passwords and personal details redacted, and deleted on the schedule those terms set.
9.1 Internal support console (admin.prestart.lab.test). L. Decided by the operations director.
9.2 Marketing site (www.prestart.lab.test) on a hosted website builder. O. Decided by the operations director.
9.3 The vendor and host platforms in Part 6. O.
9.4 Load and denial-of-service testing. S. Would need a load-testing specialist and the host's written approval.
9.5 Signed-in testing in production. R. Staging runs the same build and shares nothing with production.
9.6 Staff laptops, the office network and phishing. S.
9.7 Features released after this schedule is signed. L.
10.1 Approves additions: the operations director, by email.
10.2 If not approved in time: reported and recorded as a limitation.
10.3 Staging frozen at build 4182 for the testing window. Production releases continue but do not touch staging.
11.1 Retest covers: the findings reported from this scope.
11.2 Fixes deployed to staging, on a build number given to the tester when the retest is requested.
11.3 Window for requesting the retest: as set in the statement of work.
11.4 Kept for the retest: all eight accounts and both test fleets.
11.5 Not covered: the support console, everything in Part 9, and routes added after sign-off.
12.1 Attached: route list (build 4182), permission matrix, authorisation letter signed by the managing director, rules of engagement, and the host and vendor terms with the dates they were read.
12.2 Technical contact: the lead developer, mobile number in the rules of engagement.
12.3 and 12.4: signed by the operations director and the chosen provider.What a penetration testing scope settles
A penetration testing scope is the written boundary of a test: which systems the tester may send requests to, from which accounts and addresses, in which environment, and what must be left alone.
The rest of the engagement hangs off it. The quote prices it, the authorisation letter gives permission for it, the rules of engagement govern behaviour inside it, and the report can only speak for what it contained.
The UK's National Cyber Security Centre (NCSC) says the output of scoping should be a document that states, among other things, the technical boundaries of the test, the types of test expected, the timeframe and the effort needed, the testing team's requirements, any compliance or legislative requirements, reporting requirements and time constraints.
Its examples of preparing for the team's requirements include creating test accounts before the test date. NIST SP 800-115 describes what a written assessment plan does for both sides. It sets the rules and boundaries assessors must keep to and reduces the risk of accidental disruption or inadvertent disclosure of sensitive information, and it protects the test team by making sure management understands and agrees to the scope, activities and limitations.
The template on this page is a tool for your own procurement. Fill it in once, send the same schedule to every provider you approach, and the quotes come back describing the same work. It is written for a web application and the API behind it. An office network, a native mobile app or a phishing exercise needs a schedule of its own.
Who fills it in, and what to collect first
NCSC suggests that scoping involve the relevant risk owners, technical staff who know the target system and a representative of the penetration test team.
In a business with one application, that is usually the owner or manager who wants the test, the developer or agency that maintains the application, and the provider. The owner answers why, for whom and what must not break. The developer answers hostnames, routes, environments and services. Gathering these before anyone opens the template saves most of the back and forth:
- The exact wording from whoever asked for the test: a customer questionnaire, a contract clause, an insurer's form or your own board minute.
- An export of the routes from the code's route definitions or the API schema, taken from a named build, so the count and the list agree.
- Your DNS zone. It lists every hostname you have pointed somewhere, including the ones that point at other companies' services.
- Every outside service the application calls or loads, which your developer can read from configuration and environment settings and your bookkeeper can cross-check against the bills.
- The terms each host and vendor publishes about customer security testing, saved with the date you read them.
- Usernames for the test accounts, and the name of the person who will create them.
How to fill in each part of the schedule
The schedule has twelve parts.
The five below decide whether the quotes you receive can be compared line for line, so they deserve the most care.
Write every hostname in full, including both the bare domain and www if both answer, and every API base path with its version. NIST SP 800-115 asks an assessment plan to identify the systems authorised for testing, and also to list the specific systems that are not, at minimum by IP address and preferably by name as well.
For a web application the useful name is the hostname and path, so Part 2 asks for both lists that way: what is in, and what shares your domain but stays out.
Older API versions belong on the list even if nothing you know of still calls them. OWASP's API Security Top 10 says threat agents usually get unauthorised access through old API versions or endpoints left running unpatched and using weaker security requirements (API9:2023). If v1 still answers, decide whether it is tested or excluded, and write the decision down.
For each environment, record the hostnames, the build deployed, where its data came from and what it shares with production. OWASP's API9:2023 entry recommends documenting, for every API host, the environment it runs in, such as production, staging, test or development, who should have network access to it and the API version it runs.
It also warns that different API versions or deployments are sometimes connected to the same database with real data. A staging copy that reads production's database, file storage or sign-in tenant carries production's risks, so treat it that way in Part 8.
If production is in scope at all, write what may happen there: nothing, checks that need no account and change nothing, or signed-in testing with test accounts only. Request rates and pause conditions belong in the rules of engagement, and testing dates in the statement of work. The schedule only records which environment carries which kind of testing.
List each role with what it may do, in one line, and roughly how many routes it can call. Providers size work from those counts, and a count by role shows where access checks will multiply. Note roles that exist but are left out this round, such as a staff support console, so the report can say plainly that they were not tested.
Provide two test accounts per role, and accounts in two customer organisations if one database serves several. WSTG v4.2 says the best way to test direct object references is with at least two users, often more, who own different objects. Then list the kinds of record the application keeps and who owns each, and write down the business rules the server is meant to enforce.
WSTG v4.2 notes that a third-party tester has to ask the business whether different operations should be allowed, so a rule that exists only in someone's head gives the tester nothing to measure against.
The provider supplies the addresses its test traffic will come from. NIST SP 800-115 says an assessment plan should identify those addresses so administrators can tell assessment activity apart from a real attack. Part 7 records them beside any firewall, bot protection or rate limit that has to let them through, and the people who watch your alerts, including any monitoring a host or agency runs for you.
Part 8 sets the data limits: whether real personal information sits in the test environment, which records may be created, changed or deleted and how test records are marked, what must not be touched, upload sizes, and the only email addresses and phone numbers messages may go to.
NIST SP 800-115 puts data handling in the plan as well: how your data is stored on the assessors' systems during the work and kept once it ends, how it moves across networks, and how it is removed at the end.
Every exclusion gets a reason, because the reason tells a later reader what the gap means. Four reasons cover most lines: someone else owns it, it adds effort and will be scoped later, it needs a different kind of specialist, or it is too risky in the environment on offer.
NIST SP 800-115 asks for prohibited activities to be stated in a way that leaves no room for interpretation, and exclusions deserve the same plain wording.
The retest boundary is the line people think about last and argue over first. Write which findings the retest covers, the environment and build the fixes will be deployed to, the accounts kept for it, and what it leaves out, such as features added after sign-off. Leave the window for requesting it blank until your statement of work sets it.
Third-party services and hosting: what your signature covers
An authorisation from your business can speak only for systems your business controls.
A typical web application leans on other companies for hosting, sign-in, payments, email, maps and file storage, and those companies' platforms are not yours to put in scope. NIST SP 800-115 makes the point in network terms: where an organisation does not control part of its network, such as systems housed on a third party's network, the owner of that network usually must also consent in writing to the assessment plan, and it treats systems shared between organisations as a similar case.
The boundary usually runs through the middle of a service rather than around it. Your code, your settings and your account's configuration are yours. The vendor's servers, hosted pages and other customers are not. Part 6 asks you to draw that line for each service and record which of three things applies: you read the vendor's published terms for customer testing on a stated date and they allow what the scope describes, the vendor gave written permission, or the service is excluded.
Hosts and vendors word these terms differently, and some hosts ask for notice or approval before testing starts, so read the current version yourself rather than relying on what another customer was told. Typical splits look like this:
- Hosting platform: your deployed application and your account settings are yours to authorise, within the host's terms. The host's platform, control panel and shared infrastructure are not.
- Hosted sign-in service: how your application checks the tokens it receives, which roles it trusts them to carry and when sessions end are yours. The vendor's hosted login pages and platform are not.
- Payment provider: the checkout request your server builds, the amount it sends and the route that receives payment notifications are yours, tested in the provider's test mode. The hosted checkout page, card handling and the provider's dashboard are not.
- Email and SMS delivery: whether your application limits how often it sends is yours, with messages going only to destinations the tester controls. The delivery platform is not.
- Help desk, status page or booking tool on one of your subdomains: the DNS record is yours. WSTG v4.2's subdomain takeover test (WSTG-CONF-10) explains that a subdomain can be taken over when its record points to an external service or resource that is no longer active. The product behind the record belongs to the vendor.
- File storage in your own cloud account: the bucket's access settings and the links your application issues are yours. The storage service itself is the provider's.
Why the schedule asks what data each service receives
OWASP's API9:2023 entry recommends an inventory of integrated services that documents their role in the system, what data is exchanged and their sensitivity. Part 6 asks for the role and the data exchanged, and adds how sensitive that data is. Beyond permission, the answers show the tester where your data leaves your control, which is where a weak link between your application and a vendor tends to matter most.
When something outside the scope turns up mid-test
Testing often finds things nobody listed: an old API version that still answers, a forgotten staging host, a subdomain pointing at a service you stopped paying for.
NCSC describes two ways to handle a system found outside the scope that could affect the ones inside it. The testing team can suggest a change to the scope, which is likely to alter the time frame and cost, or recommend that its exclusion be recorded as a limitation on testing.
NCSC says the choice will generally be down to the risk owner, with the testing team responsible for setting out the factors to consider.
Part 10 of the schedule settles that in advance: who may approve an addition in writing, and what happens if nobody does in time. Without that line, a tester either stops work to ask or carries on into something nobody authorised, and neither outcome helps you.
The same goes for anything that changes during the window. If developers will deploy while testing runs, say where, or freeze the build. NIST SP 800-115 says that when questions about scope or the level of authorisation arise during an assessment, the assessors and the organisation's identified point of contact should meet to discuss them, and NCSC asks for a technical point of contact who is available at short notice throughout the test phase. Part 12 names that person.
Scope gaps that come back as report limitations
A gap in the schedule does not disappear when testing starts.
It comes back in the report as a limitation. The WSTG v4.2 reporting chapter suggests the report introduction set out scope and limitations, and lists out-of-bounds areas, broken functionality, lack of time and lack of access or credentials among the limitations it can record. Most of them trace back to a line in the scope:
- Accounts that arrive late, or for one role only, leave routes tested from one side only.
- An integration switched off on staging becomes functionality the tester could not exercise.
- A hostname missing from Part 2 becomes an out-of-bounds area, even when it runs the same code.
- A vendor whose permission never arrived becomes an exclusion the report has to explain.
- A build that changed halfway through leaves findings tied to a version that no longer exists.
Using the schedule with Clever Ops or another provider
The schedule is yours, not a provider's form.
Send the same copy to each provider you approach and ask them to mark any line they would change, with the reason. How they mark it tells you more about the test each one intends to run than the totals on their quotes.
If you bring it to a free scoping call with Clever Ops, the call goes straight to the parts that carry the risk, and you then receive a written scope and quote naming the targets, environment, routes, roles and exclusions, and what the one included retest covers.
No request is sent until the owner of each target has signed an authorisation and your hosting provider's testing policy has been checked, and services run by other businesses stay out of scope unless their owner agrees.
Destructive actions are off by default for real people's accounts and records that existed before the test. Reset, lockout and deletion checks run only on test accounts and test records, where the rules of engagement allow them.
Some schedules point to a different provider. If Clever Ops built or hosts the application, the work is a security review rather than an independent test, and the report says who built it and who hosts it. Where a tender, panel or contract requires CREST, Clever Ops is not CREST accredited, so we refer that work to a provider that is. Internal networks, staff devices, phishing and load testing go to specialists in those fields.
Frequently asked questions
At minimum: the exact hostnames and API paths in scope and those excluded, the environment and build, the roles with two test accounts each, the third-party services and who owns them, the tester's source addresses, the data limits, every exclusion with its reason, and what the retest covers. The template on this page sets these out in twelve parts, followed by a completed example.
No. The scope says what will be tested. The authorisation letter, signed by someone with authority over each target, gives permission to test it. The rules of engagement govern behaviour inside the testing window, such as request rates, pause conditions and who to call. Most engagements need all three, which is why Part 12 of the schedule lists the other two as attachments.
Only the parts you control, such as your deployed application, your account settings and the code that calls the service. The provider's own platform needs its written permission, or its published terms for customer testing have to allow what the scope describes. Read those terms before testing, record the date you read them, and exclude the service if neither applies.
For a web application, hostnames and API paths, with addresses only where you own them. An application on a cloud platform or behind a content delivery network can sit on addresses shared with other customers, and those addresses can change, so an address on its own can point a tester at someone else's system. The addresses that matter most are the tester's source addresses, which go in Part 7 and in the authorisation letter.
Staging, when it runs the same code and configuration as production and holds no real customer data, because the tester can then create and change records freely. Check what it shares with production first: a staging copy connected to the production database or file storage carries production's risks. Production can still be in scope for checks that need no account, or for signed-in testing with test accounts, under the rules of engagement.
Detailed enough that you and every provider count the same routes. Export it from the code's route definitions or the API schema on a named build, give the method and path of each route, mark which roles may call it, and include older versions that are still deployed. A count without a list makes quotes hard to compare, and a list without a build reference goes stale with the next release.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.