Free tool

Pentest engagement letter generator

Write the document that opens every pentest: scope and exclusions, testing window, rules of engagement, emergency contacts, deliverables and the client's signed authorization to test. Free, no sign-up, and nothing you type leaves your browser.

This is a template, not legal advice. For large engagements, or if you're unsure about liability, have it reviewed by a lawyer in your jurisdiction.

Everything stays in your browser. Nothing you type is sent to us or stored on a server.

Your firm
The client
The assessment
The application
Scope
Testing window
Rules of engagement
Contacts during testing

Testing lead

Client contact

Deliverables
Fees and terms
Signatures
In the print dialog, choose “Save as PDF”.

[Your firm]

Date:
21 November 2026
Reference:
ENG-2026-001

Penetration Test Engagement Letter and Rules of Engagement

This letter sets out the terms under which [Your firm] (“the Firm”) will perform a penetration test for [Client] (“the Client”), and records the Client's authorization to carry it out.

1. Services

The Firm will perform a [type of assessment], using a grey-box approach: the testers are given user accounts and basic documentation, as an attacker with a foothold would have.

2. Scope

Testing is limited to the following assets:

  • [Systems in scope, one per line]

Any asset not listed above is out of scope, even if it is discovered during testing or appears to belong to the Client. Changes to the scope must be agreed in writing by both parties before they are tested.

3. Testing window

Testing will take place between [start date] and [end date], during business hours, 09:00 to 18:00, Monday to Friday.

The Firm will provide the IP addresses that testing traffic will originate from before testing begins.

4. Rules of engagement

The following techniques are permitted or excluded:

  • Automated vulnerability scanning: Permitted
  • Exploitation of identified vulnerabilities to confirm their impact: Permitted
  • Password attacks (guessing, spraying, cracking captured hashes): Not permitted
  • Lateral movement and privilege escalation beyond the initial target: Not permitted
  • Social engineering, including phishing of the client's staff: Not permitted
  • Physical access testing: Not permitted
  • Denial-of-service or load testing: Not permitted

The Firm will not intentionally disrupt the availability of any system. If testing appears to affect the stability of a system, the Firm will stop that activity and notify the Client's contact immediately, and resume only with their agreement.

Critical findings, and any evidence that the systems have already been compromised by a third party, will be reported to the Client's contact within 24 hours of discovery, without waiting for the report.

Access to data will be limited to what is needed to demonstrate a finding. The Firm will not modify or delete the Client's data, and will not copy personal data beyond the minimum evidence required, which will be redacted in the report.

Either party may suspend testing at any time by notifying the other party's contact.

5. Contacts

During the testing window, each party's contact must be reachable for the notifications above:

  • Testing lead ([Your firm]): [Name] [contact details]
  • Client contact ([Client]): [Name] [contact details]

6. Deliverables

  • A written report with an executive summary and each finding with its evidence, impact, severity and remediation guidance, delivered within 10 business days of the end of testing.
  • One retest of the reported findings, if the Client requests it within 30 days of the report's delivery.
  • On request, an attestation letter summarizing the assessment and its remediation status, which the Client may share with auditors and customers.

7. Confidentiality and data handling

The Firm will treat all information obtained during the engagement as confidential, will share the report only with the Client's contacts, and will securely delete test data and evidence 90 days after delivery of the final report, unless agreed otherwise in writing.

A penetration test is a point-in-time assessment of the agreed scope. It reduces risk but does not guarantee that every vulnerability will be found.

8. Authorization

By signing below, [Client] confirms that it owns the assets in scope or is authorized to approve their testing, including any consent required from third parties that host or operate them, and authorizes [Your firm] to perform the testing described in this letter, within the scope and testing window above.

For [Your firm]

Name: [Name]

Title:

Date:

For [Client]

Name:

Title:

Date:

Engagement letter template by Closeout · getcloseout.tech

What is a pentest engagement letter?

A pentest engagement letter is the document signed before testing starts. It says what will be tested and what won't, when, how far the testers may go, who to call if something breaks, what the client gets at the end, and, most importantly, that the client authorizes the test.

Without that written authorization, a penetration test is legally indistinguishable from an attack. Laws such as the US Computer Fraud and Abuse Act, the UK Computer Misuse Act and article 197 bis of the Spanish Criminal Code punish access to systems without permission, and the signed letter is your evidence that you had it.

Engagement letter, SOW, rules of engagement, authorization letter

These names overlap, and firms split them differently. In practice:

DocumentWhat it answers
Statement of work (SOW)What work will be done, the deliverables and the price
Rules of engagement (RoE)How testing may be done: techniques, hours, limits, contacts
Authorization letterWho allowed the test, for which assets, and that they had the right to
Engagement letterAll of the above in one signed document, often under a master services agreement

Large engagements often keep them separate. For most small and mid-size tests, one engagement letter is clearer for everyone, and it's what the generator above produces. When testers need something to show a SOC, a hosting provider or building security, add a separate one-page letter from the authorization letter generator.

What to include

  1. Both parties, with the client's legal name, and a reference number.
  2. The type of assessment and the approach: black, grey or white box.
  3. The application itself: what it is (web app, API, mobile, thick client), what it does, who uses it, what data it handles, the environment being tested and the test accounts provided.
  4. The scope: every domain, IP range and application in scope, and the exclusions written out, not implied.
  5. The testing window: dates, hours and time zone, and the IP addresses your traffic will come from.
  6. The rules of engagement: which techniques are allowed (exploitation, password attacks, social engineering, denial of service…) and which aren't.
  7. What happens when something goes wrong: stopping on instability, and reporting critical findings or signs of a prior breach straight away.
  8. Contacts on both sides who can be reached during testing.
  9. Deliverables and deadlines: the report, whether a retest is included and until when, and the attestation letter.
  10. Fees and payment terms, or a reference to the master agreement that covers them.
  11. Confidentiality and how long test data is kept.
  12. The authorization, signed by someone with authority over the systems.

Getting the scope right

Most disputes start with the scope. A few habits avoid them:

  • List, don't describe. “The customer portal” is ambiguous; portal.example.com and api.example.com/v2 are not.
  • Write the exclusions down. Payment providers, third-party SaaS, shared hosting and production databases are the usual ones.
  • Check who owns each asset. A domain the client uses may be hosted by someone else, whose permission also matters. AWS, Azure and Google Cloud allow testing of most services without asking first, but each has a policy to follow.
  • Agree changes in writing. Testers find new hosts during every test; they get tested only once the client adds them.

Put the retest in the letter

If one retest is included, say so, and say until when. An open-ended promise turns into months of chasing; a window, commonly 30 to 90 days after the report, keeps both sides moving. Our guides on pentest retesting and remediation timelines cover what's usual.

When the retest is done, the attestation letter generator writes the closing document from the same details: scope, dates, findings and what was verified as fixed.

Frequently asked questions

Is this engagement letter template free?

Yes. There's no account, no limit and no watermark: just an optional one-line credit at the bottom that you can switch off.

Is an engagement letter the same as a statement of work (SOW)?

Close. A SOW describes the work and the commercial terms; rules of engagement describe how testing may be done; an authorization letter records the client's permission. For most small and mid-size engagements one signed letter covers all three, which is what this generator produces.

Who should sign the authorization on the client side?

Someone with authority over the systems in scope, such as the CISO, CTO or a director, not just the technical contact. If the assets are hosted or operated by a third party, the client must also have that party's consent where its terms require it.

Do I still need a contract if I have this letter?

If you already have a master services agreement with the client, this letter works as the per-engagement document under it: name the agreement in the form and it will prevail. Without one, the letter records the essentials, but liability, insurance and payment disputes are better covered by a proper contract.

Is my client's data safe?

The generator runs entirely in your browser. What you type is kept only in your browser's local storage, so you don't lose a draft, and is never sent to Closeout or stored on a server.

Do I need permission from AWS, Azure or Google Cloud?

Not for most services: all three dropped their pre-approval requirement, but each publishes a policy you must follow, and denial-of-service testing is restricted. Check the provider's current policy before testing assets hosted there.