GUIDE · VULNERABILITY AND TESTING

Preparing a penetration test: scope, rules of engagement and what to ask

By the end of this guide you will know how to prepare a penetration test so that it produces useful results without disrupting the business. You will see how to define the scope, how to write the rules of engagement, which authorisations are needed, and which questions to put to the provider before signing.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. Why preparation determines the value of the test

A penetration test is a controlled exercise in which a specialist attempts to breach your systems as an attacker would. It only produces value if it is well defined. A poorly prepared test can be slow, incomplete or risky for the business. It may leave out the most important systems because nobody named them, or touch systems that should not have been touched. A well-prepared test avoids both risks and makes the results comparable with later tests.

Preparation therefore serves three purposes: defining what is being tested, setting the limits within which it happens, and deciding how to handle what emerges. Whoever signs the test must know what they are authorising. Whoever carries it out must know what they may and may not do. Whoever receives the report must be able to act without further questions. Use precise dates and names in every preparation document.

2. Prerequisites: what you need before starting

Before writing a request you need some information: an inventory of the systems in scope, with addresses, applications and owners; a list of the personal or confidential data those systems process, because the test may encounter it; a verified backup of the most critical systems; and an internal contact with decision-making authority who is reachable during the test. If that contact is unavailable, every urgent decision stalls, and the tester must either stop or proceed without instructions.

You also need an agreed time window, with the periods when work cannot take place, such as financial closings or production peaks. If some systems are managed by a supplier, obtain its written consent first, because without it the test on its services is not authorised, even if you commission it. The same applies to third-party services you use in the cloud, where the provider's terms may limit the scope.

3. The preparation steps

Follow this sequence. Each step produces a document or decision that the next one uses, so it is best to do them in order. A common mistake is to jump straight to the quote and write the rules of engagement afterwards, when the tester has already started work. In that case the rules become a formality that protects nobody. Keeping to the order lets you compare like-for-like offers.

  1. Define the objective: assess an external perimeter, verify an application, check an internal environment or simulate a targeted attack.
  2. Set the scope precisely: addresses, domains, applications, test accounts and what is out of scope.
  3. Choose the type of test based on the information the tester receives at the outset, from none to full.
  4. Write the rules of engagement: prohibited techniques, such as attacks that could interrupt service, and the handling of data the test encounters.
  5. Define emergency contacts and the procedure to follow if the test causes a disruption or finds a serious flaw.
  6. Obtain written authorisation, signed by the owner of the perimeter, with date, window and scope attached.
  7. Agree the report format, delivery timelines and how the findings will be reviewed.

4. Rules of engagement: the document that protects everyone

The rules of engagement are the most important document and the one most often overlooked. They describe what the tester may do, what they may not do, and how they behave when they find something unexpected. A well-written rule avoids arguments during the test and protects both the business and the provider, because every action has a reference perimeter. When a rule is missing, the decision in the moment is made by whoever has the least information.

They also set out the excluded techniques. Common restrictions cover attacks that can saturate services, social engineering of staff, use of copied real data, and modifying or deleting information. Ask that the tester does not extract personal data beyond the minimum needed to demonstrate a flaw, and that they delete it at the end. These points must be agreed beforehand, not afterwards.

5. Common mistakes in preparation

The most common mistakes concern communication rather than technique. A test carried out well can still cause problems if someone did not know it was happening. It is worth informing in advance the owners of the systems involved, the customer service team if there could be any impact, and the person monitoring alerts. If monitoring is outsourced, also notify the provider in writing.

  • Declaring a vague scope, such as the whole network, which makes it impossible to tell what was tested.
  • Forgetting the provider of a hosted service, which has not authorised testing on its own systems.
  • Not telling the monitoring staff, who mistake the test for a real attack and open an incident.
  • Setting too short a window for the intended perimeter, with rushing and partial coverage as the result.
  • Not arranging an available contact, so questions remain unresolved during the test.

6. Legal aspects and personal data

A test may encounter personal data, because the systems you are checking process it. The GDPR requires that all processing has a legal basis and adequate security measures, even when the processing is dedicated to security. The contract with the testing provider must therefore cover how data encountered is handled, stored and deleted, with clear responsibilities.

If the perimeter includes third-party systems or cloud services, the authorisation of whoever manages them is also needed, and it cannot be replaced by that of your own manager. Check the terms to include in the contract and the authorisation with a legal adviser. Do not treat the authorisation form as a mere formality: it is the proof that the test was authorised, so it must be kept.

7. What to ask the provider

When choosing who carries out the test, the quality of the preparation says a lot. A serious provider asks questions about the perimeter before proposing a price, and explains its method in a verifiable way. Here are some questions to put before signing. Do not look for the perfect answer: look for a concrete one. A good answer describes the method, shows an anonymised sample report and makes clear what is not included.

  • Which method do you use, and how do you document the phases of the test?
  • Who carries out the test, and what experience do they have with the type of system we will check?
  • How do you handle the personal data you encounter, and how long do you keep it?
  • What happens if you find a serious flaw during the test, and whom do you contact?
  • Does the report include justified priorities and verifiable remediation guidance?
  • Do you offer a re-test after fixes, and on what terms?

8. How to get started

This week, write a page with the objective, perimeter and time window. It does not need a perfect form: it needs text the owner can read and correct. State the systems included, those excluded and the personal data that might be encountered. Send it to the system owners and ask for written confirmation of the critical points. Owners' comments often correct a perimeter that seemed clear but was not.

Then prepare the list of emergency contacts and tell those monitoring alerts the date. Only at this point request quotes, attaching the page. A provider who works well will ask for corrections and clarifications, and that is a good sign: it means they have read the perimeter. A generic answer with no questions suggests the provider offers the same test to all clients.

Frequently Asked Questions

How long does a penetration test take?

It depends on the perimeter, the type of test and the complexity of the systems. A small, well-defined perimeter takes much less time than a complex application or a network with many segments. Ask the provider for an estimate justified by the scope you have defined, and compare it with the agreed window. If the window is shorter, reduce the scope, not the quality of the test.

Can the test cause disruption?

It can, particularly if the rules of engagement do not limit the more intrusive techniques or if the perimeter includes fragile systems. For this reason the rules should exclude attacks that saturate services, require an available contact and define what to do in case of impact. The risk is reduced but not eliminated, and must be knowingly accepted by the owner.

Do I need to tell employees?

At a minimum, tell those who run monitoring and the owners of the systems involved. If the test must remain realistic, limit the number of people who know the date. A test that the security staff do not recognise is useful, but notice is necessary to prevent the test from becoming a real incident. Agree the level of confidentiality with the provider.

Can I test a system hosted in the cloud?

Yes, but the perimeter must respect the cloud provider's conditions and the authorisation of whoever manages the service. Some providers have their own rules for security testing, which may impose limits or require notifications. Check these conditions before planning, and include them in the rules of engagement.

Is one test a year enough?

It depends on your risk and on how your environment changes. An annual test is a checkpoint, not continuous coverage. If you change applications or architectures often, or if your systems are exposed, it is worth planning recurring, more targeted tests, alongside continuous vulnerability management. Discuss this with your provider based on your situation.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →