Free tool

Pentest authorization letter generator

Create the signed permission to test that every penetration tester should carry: who is authorized, which systems, when, from which IP addresses, what's allowed, and who to call to confirm it. Free, no sign-up, and nothing you type leaves your browser.

This is a template, not legal advice. For large engagements, physical tests or regulated sectors, 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 (who authorizes)
The test
Systems
Testing period
Authorized activities
Verification contacts

Who a SOC, a hosting provider or the police can call to confirm the test is authorized. Ideally reachable 24/7 during the testing period.

Client contact

Testing lead

Signatures
In the print dialog, choose “Save as PDF”.

[Your firm]

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

Authorization to Perform Penetration Testing

[Client] (“the Client”) authorizes [Your firm] (“the Firm”) and the individuals named below to perform a [type of assessment] against the systems listed in this letter, within the period and under the conditions set out below.

1. Authorized testers

This authorization covers the following people, acting on behalf of the Firm:

  • [Tester names]

Anyone not named above needs a written amendment to this letter before taking part in testing.

2. Systems in scope

Testing is authorized only against the following systems:

  • [Systems in scope, one per line]

Any system not listed above is not covered by this authorization, even if it is discovered during testing or appears to belong to the Client.

3. Ownership and third parties

The Client confirms that it owns the systems in scope or has the legal right to authorize their testing.

Where any system in scope is hosted or operated by a third party, the Client confirms that testing complies with that party's terms and that it has obtained any consent they require.

4. Testing period

Testing is authorized from [start date] to [end date] inclusive, during business hours, 09:00 to 18:00, Monday to Friday. This authorization expires at the end of that period.

5. Authorized activities

  • Automated vulnerability scanning: Authorized
  • Exploitation of identified vulnerabilities to confirm their impact: Authorized
  • Password attacks (guessing, spraying, cracking captured hashes): Not authorized
  • Lateral movement and privilege escalation: Not authorized
  • Social engineering, including phishing of staff: Not authorized
  • Physical access to premises: Not authorized
  • Denial-of-service or load testing: Not authorized

The testers will stop any activity that appears to affect the stability of a system and notify the verification contact below. Access to data is limited to what is needed to demonstrate a finding.

6. Verification

If this testing is detected or questioned by the Client's staff, a security provider, a hosting provider or the authorities, this authorization can be confirmed at any time during the testing period with:

  • For the Client: [Name], [24/7 phone]
  • Testing lead ([Your firm]): [Name]

7. Validity

This authorization applies only to the testers, systems, period and activities above. The Client may suspend or revoke it at any time by notifying the testing lead; testing stops on notice.

Authorized by [Client]

Name:

Title:

Date:

Acknowledged by [Your firm]

Name: [Name]

Title:

Date:

Authorization letter template by Closeout · getcloseout.tech

What is a pentest authorization letter?

A pentest authorization letter is a signed document in which the owner of a set of systems gives named testers permission to attack them, within a defined scope and period. It's also called a permission-to-test letter, a letter of authorization or, informally, a “get out of jail free” letter.

It exists for one reason: without written permission, a penetration test is legally indistinguishable from an attack. Laws such as the US Computer Fraud and Abuse Act (18 U.S.C. § 1030), the UK Computer Misuse Act 1990 and article 197 bis of the Spanish Criminal Code punish access to systems without authorization. The letter is your evidence that you had it, and the first thing to show if anyone asks.

What to include in an authorization letter

  1. Who authorizes: the client's legal name and a signer with authority over the systems.
  2. Who is authorized: the testing firm and each tester by name. Unnamed people aren't covered.
  3. Which systems: every domain, IP range, application or address in scope, and the exclusions.
  4. Third parties: cloud, hosting or CDN providers involved, and the client's confirmation that testing follows their terms.
  5. When: start and end dates, hours and time zone. The authorization should expire.
  6. From where: the source IP addresses, so the client's SOC can tell your traffic from a real attack.
  7. What's allowed: exploitation, password attacks, social engineering, physical access, denial of service, each one authorized or not.
  8. Verification contacts: someone on the client side, reachable during testing, who can confirm the letter is genuine.
  9. Revocation: the client can stop testing at any time.

The generator above produces all of these from the form, and highlights what's still missing in the preview.

Who should sign it

The signature only protects you if the signer could actually grant permission. A developer or the IT contact who asked for the test usually can't: look for the CISO, CTO, IT director, a company officer or, in small companies, the owner. If the systems belong to a parent company or a customer of your client, the permission must come from them.

A common trap: the client “owns” app.example.com, but it runs on a provider's infrastructure. AWS, Azure and Google Cloud allow testing of most services without pre-approval, but each has a policy to follow; shared hosting and managed providers often require notice. List them in the letter.

Authorization letter vs. engagement letter

Authorization letterEngagement letter / SOW
PurposeProves the test is permittedDefines the whole job
Length1–2 pagesSeveral pages
Fees and deliverablesNoYes
Shown to a SOC, provider or policeYesRarely: it has commercial terms
Signed byThe system ownerBoth parties

Many firms sign an engagement letter for the job and an authorization letter to carry during testing. For small tests, the engagement letter's authorization clause can be enough; the separate letter is worth it as soon as there's a SOC, a third-party host, physical access or social engineering.

In practice

  • Get it signed before the first packet. Not on day one of testing, not by email “to follow”.
  • Keep it at hand. A PDF on your phone for remote work; a printed copy for on-site and physical tests.
  • Call the verification contact first. Check the number works before testing starts, especially for night or weekend windows.
  • Re-issue it when anything changes. New hosts, new testers or new dates mean a new version, not a verbal OK.

When testing ends, the report and the fixes take over: see our guides on retesting fixes and remediation timelines, and close the engagement with an attestation letter.

Frequently asked questions

What is a penetration testing authorization letter?

It's a short document, signed by someone with authority over the systems, that gives named testers permission to test specific systems during a specific period. It's the evidence that the test is authorized, and testers carry it, or keep it at hand, while they work.

Why is it called a “get out of jail free” letter?

Because it's what a tester shows if a SOC, a hosting provider, building security or the police question the activity. Without it, unauthorized access laws such as the US Computer Fraud and Abuse Act, the UK Computer Misuse Act or article 197 bis of the Spanish Criminal Code make no distinction between a test and an attack.

Who should sign the authorization letter?

Someone with authority over the systems in scope: the CISO, CTO, IT director or another executive, not just the technical contact who requested the test. If a third party hosts or operates the systems, the client must also comply with that party's terms, and get its consent where those terms require it.

Is an authorization letter the same as an engagement letter?

No. The engagement letter (or SOW) covers the whole job: deliverables, fees, retest, confidentiality. The authorization letter only records the permission to test, in one or two pages, so it can be shown to anyone who asks without revealing the commercial terms. Many firms use both.

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

Not for most services: all three dropped pre-approval, but each publishes a policy that testing must follow, and denial-of-service testing is restricted. List those providers in the letter so the client confirms testing complies with their terms.

Is this template free, and is my data safe?

Yes, there's no account, no limit and no watermark. The generator runs entirely in your browser: what you type is kept only in your browser's local storage so you don't lose the draft, and is never sent to Closeout.