Skip to main content
Security templateReviewed

Penetration test authorisation letter: an Australian template, clause by clause

A letter you can copy, adapt and put in front of a solicitor.

It covers who signs, which systems, which hosts have agreed, when and from where testing runs, what testers may do, how testing stops and what happens to the evidence. This is general information, not legal advice: have a solicitor review the letter before anyone signs it.

Australian penetration test authorisation letter template

Copy the letter onto the letterhead of the business that controls the systems, fill in each blank line, and complete Schedules A to C for every target, host permission and test account. Prompts in round brackets say what each blank needs, and ( ) marks a box to tick.

How to use it

This is general information, not legal advice: have a solicitor review the letter before anyone signs, verify the signatory's authority and the business's control of each target yourself, and attach every permission a host or third party requires. The letter does not replace those permissions.

penetration-test-authorisation-letter.txt

PENETRATION TEST AUTHORISATION LETTER
A template for Australian businesses. General information, not legal advice.

BEFORE YOU USE THIS TEMPLATE
1. Have a solicitor review the letter for your business, your systems and this engagement before anyone signs it.
2. Verify the signatory's authority yourself and attach the evidence (clause 2).
3. Verify that the business controls every target in Schedule A (clause 3).
4. Attach every permission or notice a host or other third party requires (clause 5 and Schedule B). This letter does not replace any of them.
5. Remove these notes, and every line that starts "Note:", before signing.

(Print on the letterhead of the business that controls the systems in Schedule A.)

Date: ____
Letter reference: ____ (use the same reference as the scope document and statement of work)
To: ____ (legal name of the testing provider)   ABN or company number: ____
Address: ____

AUTHORISATION TO CONDUCT SECURITY TESTING

1. PARTIES AND PURPOSE
1.1 This letter is given by ____ (legal name of the business), ABN ____ ("the Business"), to ____ (legal name of the testing provider) ("the Provider").
1.2 It records the Business's permission for the people named in clause 1.3 to carry out security testing of the targets in Schedule A, only within the limits in this letter and only during the window in clause 6.
1.3 Named testers (full name of each person who will send test traffic): ____
    The Provider will not add or substitute a tester without the Business's written agreement.
1.4 This letter is read with the documents listed in clause 13.1. Where they differ, the narrower limit applies.

2. SIGNATORY AND AUTHORITY
2.1 Signatory name: ____   Position: ____
2.2 The signatory confirms that they have authority to permit security testing of every target in Schedule A on behalf of the Business.
2.3 Source of that authority (describe it and attach the evidence): ____ (for example, a board resolution dated ____, or a written delegation dated ____ from ____ naming these systems and this period)
2.4 Recorded by the Provider before testing. Evidence checked: ____   Checked by: ____   Date: ____

3. CONTROL OF THE TARGETS
3.1 The Business states that it owns or controls each target in Schedule A. Where another party owns or operates part of a target, the Business holds that party's written permission, listed in Schedule B.
3.2 Proof of control for each domain and subdomain is recorded in Schedule A. Accepted methods: a DNS TXT record holding a one-off value supplied by the Provider; a file or page placed on the target at a path the Provider names; or another method agreed in writing: ____
3.3 If the Business learns that it does not control a target, or that a permission in Schedule B has changed or been withdrawn, it will tell the Provider contact at once. Testing of that target stops until both parties confirm in writing that it may resume.

4. TARGETS AND EXCLUSIONS
4.1 Testing is permitted only against the targets listed in Schedule A. Any hostname, subdomain, API path, IP address, environment or account not listed there is out of scope, including one created after this letter is signed and one hosted on the same server as a listed target.
4.2 Excluded even where reachable from a listed target: ____ (for example, a payment provider's hosted checkout, an embedded booking or chat widget, the hosting control panel, shared email services, other customers of the same platform)

5. HOSTING AND THIRD-PARTY PERMISSIONS
5.1 Schedule A names the hosting provider and plan, or cloud account, for each target, and each third-party service in front of or behind it, such as a content delivery network, firewall, sign-in service or payment service.
5.2 Schedule B records, for each of those providers, the terms the Business read about security testing, the date it read them, and the outcome: no approval needed under those terms, notice given, or written approval received, with a copy attached.
5.3 No target is tested until its Schedule B entries are complete. This letter does not give, and does not replace, any permission a host or third party requires.

6. TESTING WINDOW
6.1 Start: ____ (date and time)   End: ____ (date and time)   Time zone: ____ (for example AEST or AEDT)
6.2 Daily testing hours: ____   Blackout periods with no testing: ____ (for example, a sale, a payroll run or a product launch)
6.3 A change to the window takes effect only once the contacts in clause 10 have agreed it in writing.

7. SOURCE ADDRESSES
7.1 All test traffic will come from these IP addresses only. IPv4: ____   IPv6: ____
7.2 The Provider will notify the Business contact in writing before using any other address. Traffic from an address that is neither listed nor notified is not covered by this letter.
7.3 Allow-listing for the window (tick one): ( ) the Business will allow-list these addresses in ____ (firewall, rate limiting or bot protection)   ( ) the Business will not allow-list them

8. PERMITTED AND PROHIBITED ACTIONS
8.1 Permitted within Schedule A and the window (tick each that applies):
    ( ) testing without signing in
    ( ) signed-in testing with the accounts in Schedule C
    ( ) requests sent to the API directly, not only through the screens
    ( ) file upload tests using harmless files
    ( ) creating test accounts and test records
    ( ) changing or deleting records the testers created
    ( ) read-only review of the code areas named in the scope document
    ( ) other: ____
8.2 A finding is proved with the smallest step that shows its impact, such as reading one record that belongs to a second test account. Data is not extracted in bulk.
8.3 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.
8.4 Prohibited unless a variation signed under clause 13.2 names it: denial-of-service, load or volumetric testing; sending email, text messages or password resets to real people; phishing or any other contact with staff or customers; physical access to premises; installing persistent access; using access gained on a listed target to reach anything not listed; other: ____

9. PRODUCTION RISK ACCEPTANCE
9.1 Environments in scope (tick one): ( ) staging only   ( ) production only   ( ) staging and production, as marked in Schedule A
9.2 Where production is in scope, the Business acknowledges that testing a live system can have unintended effects even within this letter, such as error pages, slower responses, messages sent by forms or test records visible to staff.
9.3 The Business confirms that a backup of production data was taken on ____ and a restore from it was tested on ____; that the person who can restore service during the window is ____; and that these records, features and integrations must not be touched: ____
9.4 Accepted for the Business by: ____ (name and position of the clause 2 signatory)

10. CONTACTS, EMERGENCY STOP AND CRITICAL FINDINGS
10.1 Business contact during the window. Name: ____   Phone: ____   Email: ____
10.2 Business backup contact, if the first does not answer within ____ minutes. Name: ____   Phone: ____
10.3 Provider contact during the window. Name: ____   Phone: ____   Email: ____
10.4 Stop phrase: ____ (short, agreed in advance, used for nothing else). When either party gives the stop phrase, or asks by phone or email for testing to stop, all testing stops at once. It resumes only when the approver named in the rules of engagement confirms in writing, or the Business contact where the rules of engagement name none.
10.5 The Provider will stop testing the affected target and call the Business contact if the target slows, errors or becomes unavailable in a way testing may have caused; if real personal or payment data is exposed in bulk; if there are signs that someone else has already compromised the system, in which case the Provider leaves what it found untouched; or if a request reached a system not listed in Schedule A.
10.6 Findings the Provider rates critical are reported to the Business contact by phone within ____ of being confirmed, as well as in the report.

11. EVIDENCE AND DATA HANDLING
11.1 The Provider keeps only the evidence each finding needs. Passwords, session tokens, keys and personal details are redacted from the report and from stored evidence.
11.2 Evidence is stored in ____ (country) using ____ (service). Encrypted at rest: yes / no
11.3 Evidence is deleted ____ (period) after ____ (event, for example acceptance of the final report), and the Provider confirms the deletion in writing on request.
11.4 The report and evidence go only to the Business, except to: ____ (anyone else who must receive them, and why)

12. SAFE HARBOUR
Note: this clause is a promise between the Business and the Provider only. It does not speak for the police, a regulator, a host or any other third party, and what effect it has in law is for your solicitor to advise. Have your solicitor review, change or remove it.
12.1 For testing carried out by the named testers within the targets, window, source addresses and permitted actions in this letter, the Business will not treat that testing as unauthorised, and will not bring a claim against the Provider or the named testers on the basis that it was unauthorised.
12.2 If a host, a third-party service or a law enforcement body asks whether specific traffic was authorised by the Business, the Business will say in writing whether that traffic falls within this letter.
12.3 This clause does not apply to anything outside the limits of this letter.

13. RELATED DOCUMENTS, CHANGES AND END OF PERMISSION
13.1 Scope document: ____ (title, version, date)   Rules of engagement: ____ (title, version, date)   Statement of work: ____
13.2 Any change to the targets, window, source addresses, named testers or permitted actions is made by a written variation signed by a person with authority under clause 2.
13.3 The Business may withdraw this permission at any time by telling the Provider contact. Testing stops on notice.
13.4 This permission ends when the window in clause 6.1 closes, whether or not testing is finished.

SIGNED for the Business
Signature: ____   Name: ____   Position: ____   Date: ____

ACKNOWLEDGED for the Provider
Signature: ____   Name: ____   Position: ____   Date: ____

SCHEDULE A. TARGETS
Copy this block once for each target.
A1. Target (exact URL, hostname, API base path or IP address): ____
    Environment: production / staging / other: ____
    Hosting provider and plan, or cloud account: ____
    Third-party services in front of or behind it: ____
    Proof of control. Method: ____   Value or location: ____   Confirmed on: ____   By: ____
    Testing depth: without signing in / signed in / with read-only code access
    Limits that apply to this target only: ____

SCHEDULE B. HOST AND THIRD-PARTY PERMISSIONS
Copy this block once for each provider named in Schedule A.
B1. Provider: ____   Targets it affects: ____
    Terms or policy read (title and where found): ____   Date read: ____
    Outcome: no approval needed under those terms / notice given on ____ to ____ / written approval received on ____, reference ____
    Copy attached: yes / no

SCHEDULE C. TEST ACCOUNTS
Copy this line once for each account.
C1. Account: ____   Role: ____   Organisation or tenant: ____   Holds real customer data: no / yes, described here: ____   Reset or removed after testing by: ____

What an authorisation to test letter is for

A penetration test authorisation letter is a business's written permission for named testers to send test traffic to named systems, inside stated limits, for a stated period.

Providers call it different things: an authorisation to test letter, a penetration testing authorisation form, a consent letter. The title matters less than three things the document has to get right. The person signing can approve testing for the business. The business controls what is listed. And every limit a tester needs to stay inside is written down where both sides can point to it.

Read this page as general information, not legal advice. The template is a starting point to adapt with a solicitor who knows your business and the systems involved, and it should go to them before anyone signs. Three checks stay with you whatever the wording says: confirm the signatory's authority, confirm the business controls each target, and attach any permission a host or other third party requires. A signed letter does not replace any of those permissions.

The letter sits beside two other documents. The scope document lists what is being tested and how deeply. The rules of engagement set how testers behave once testing starts, such as request rates and when to pause.

The authorisation letter is the one a person with authority signs to say yes, and the one you produce when a host, a monitoring service or your own staff ask whether some unusual traffic was expected.

Permission for penetration testing: what the Criminal Code text says

Part 10.7 of the Criminal Code, the Schedule to the Criminal Code Act 1995 (Cth), is headed Computer offences.

The section numbers and quotes below come from the compilation on the Federal Register of Legislation that shows the law in force on 30 June 2026 (Compilation No. 174), read on 14 November 2026. They restate the text and go no further.

Each offence in sections 477.1 to 478.2 lists, among its conditions, that the person causes an unauthorised access, modification or impairment. Section 476.2(1) gives the meaning: the kinds of access, modification and impairment it lists, starting with access to data held in a computer, are unauthorised "if the person is not entitled to cause that access, modification or impairment".

Section 476.2(3) adds that, for an offence under the Part, a person causes unauthorised access, modification or impairment if their conduct substantially contributes to it.

Section 478.1 is an example of how an offence is framed. Its conditions are that the person causes unauthorised access to, or modification of, restricted data, intends to cause it, and knows it is unauthorised. The section defines restricted data as data held in a computer to which access is restricted by an access control system associated with a function of the computer.

Two points about what the text leaves out matter for this page. Apart from the warrants, authorisations, requests and notices listed in section 476.2(4), Part 10.7 does not say what makes a person entitled, and it does not mention penetration testing or authorisation letters.

Section 476.4 also states that, subject to sections 476.6 and 476.7, which deal with certain intelligence agencies and defence officials, the Part is not intended to exclude or limit the operation of any other law of the Commonwealth, a State or a Territory.

So this page gives no view on whether a particular test is authorised, and no template can settle that. What a careful letter can do is put the relevant facts in one signed record, so that you, the provider and your solicitor are reading the same thing: who agreed, on what authority, for which systems, with which third-party permissions and within which limits.

Who signs, what the business controls, and who else must agree

Clauses 2, 3 and 5 of the template deal with the permission itself.

Each one fails quietly when it is wrong: the letter looks complete, testing starts, and the gap only shows when something breaks or someone complains.

Clause 2: the signatory and their authority

The person who signs needs authority to approve testing for the business that controls each target. That is often not the person who asked for the test. A marketing manager may run the website day to day without authority to let outsiders probe the customer database behind it, and an IT contractor may hold every password without holding any authority to approve anything.

Before signing, agree with your solicitor what evidence shows that authority for your business, such as a board resolution or a written delegation naming the systems and the period, and attach a copy. Clause 2.4 asks the provider to record what it checked, who checked it and on what date. If nobody can produce the evidence, find the person who can sign before you book a testing window.

Clause 3: proof the business controls each target

Domains drift over the years. An old campaign subdomain still points at a former agency's server, a staging hostname was handed to a contractor, or a DNS record leads to a service you trialled and abandoned. A target listed on your say-so can turn out to be someone else's system, so the template asks for proof for every domain and subdomain, recorded in Schedule A.

Two practical methods appear in clause 3.2. One is a DNS TXT record holding a one-off value the provider supplies, published by whoever manages your DNS. The other is a file or page placed on the target at a path the provider names.

Either shows that someone acting for the business can change that system now, which an old contract or invoice cannot show. Before signing, compare every hostname in Schedule A with your DNS records and hosting accounts, and remove any you cannot prove.

Clause 5: hosting and third-party permissions

Your business may own the application while the servers, network and platform underneath belong to a host or cloud provider, and parts of the site, such as payments, bookings, chat or sign-in, belong to other businesses. Each of them has its own terms, which may limit what testing it allows on its platform, and a host's terms may ask for notice or written approval before any testing, even of your own site. The letter does not give permission on their behalf, and clause 5.3 says so in terms.

Before signing, find the terms that apply to each target's hosting plan and to every service in front of or behind it, such as a content delivery network or a web application firewall. Read what they say about security testing, and record the outcome and the date in Schedule B.

Where the terms are silent or unclear, ask the provider in writing and attach the reply. A service you cannot get permission for moves to the exclusions in clause 4.2.

Skipping this step leaves a gap the rest of the letter cannot close: a test you approved can still be one your host's terms do not allow, and those terms govern your hosting account.

Exact targets, the testing window and the source addresses

Clauses 4, 6 and 7 turn the permission into something a tester, a host and your own team can check against live traffic.

Clause 4: targets listed exactly, exclusions named

Write each target as an exact URL, hostname, API base path or IP address, with its environment. "Our website" is not a target; the production shop hostname and the staging API hostname are two. Clause 4.1 puts anything unlisted out of bounds, including a subdomain launched during the window and another site sharing the same server.

Exclusions deserve the same care. Name what sits inside your site but is not yours to test, such as a payment provider's hosted checkout, an embedded booking widget or the host's control panel, so a tester who reaches it knows where the edge is.

Clause 6: the testing window

State dates, daily hours and the time zone, and list blackout periods for events such as a sale, a payroll run or a launch. A window gives your team and anyone monitoring your systems a way to tell expected traffic from unexpected traffic. Clause 13.4 ends the permission when the window closes, so a retest weeks later needs a signed variation or a fresh letter.

Clause 7: the source IP addresses

List every address test traffic will come from, both IPv4 and IPv6. Your team, your host and any monitoring service can then match an alert to the test quickly instead of treating it as an attack, and traffic from any other address falls outside the letter.

Clause 7.3 records whether those addresses will be allow-listed in a firewall or bot protection for the window. Allow-listing changes what the test can say about those defences, so make the choice deliberately and keep it on paper.

What testers may do, the risks you accept and how testing stops

Clauses 8, 9 and 10 set the boundaries of the work itself and the way out if something goes wrong.

Clause 8: permitted and prohibited actions

Tick only the activities the scope needs. A short permitted list is easier to check than a long list of prohibitions. Clause 8.2 limits how far a tester proves a finding: the smallest step that shows the impact, such as reading one record that belongs to a second test account, rather than downloading a table.

The template keeps destructive actions off by default for real people's accounts and records that existed before the test, and reset, lockout and deletion checks run only on test accounts and test records where the rules of engagement allow them. Clause 8.4 names the actions that stay prohibited unless a signed variation adds them: denial-of-service, load or volumetric testing, messages or password resets sent to real people, contact with staff or customers, physical access, persistent access, and moving from a listed target to an unlisted one.

Clause 9: accepting the risk of testing production

Testing a live system can have effects nobody intended, even inside every limit: error pages, slow responses, emails sent by a form, test records appearing in a staff dashboard. Clause 9 has the business acknowledge that in writing, confirm a recent backup and a tested restore, name who can restore service during the window, and list anything that must not be touched, such as a live payments integration or a feed into the accounting system.

Check the backup claim yourself before signing, because a backup nobody has restored is an assumption rather than a fallback. If you have a staging copy that mirrors production, choose staging in clause 9.1 for most of the work and keep production for the checks only production can answer.

Clause 10: contacts, stop phrase and critical findings

Name a business contact who will answer the phone during the window, a backup if the first does not answer, and the provider's contact. The stop phrase is a short agreed phrase that halts all testing the moment either side uses it, with no discussion first; testing resumes only when the approver named in your rules of engagement confirms in writing, or your contact where they name none.

Clause 10.5 lists the conditions under which the provider stops on its own and calls you: the target slowing or erroring, real personal or payment data exposed in bulk, signs that someone else has already compromised the system, or a request that reached something outside Schedule A.

Signs of an earlier compromise need particular care. The clause has the provider leave what it found untouched, because cleaning up can destroy evidence an incident response specialist may need. Critical findings are reported by phone within a time you agree in clause 10.6, rather than waiting for the report.

Evidence handling and safe-harbour wording

The last two working clauses deal with what is left after the test and with the promise the business makes about testing inside the letter.

Clause 11: evidence and data handling

A test of a live application can pass real customer data through a tester's hands. Clause 11 limits evidence to what each finding needs, has passwords, session tokens, keys and personal details redacted, and asks where evidence is stored, whether it is encrypted, when it is deleted and who else may receive it.

Fill in the country and the service rather than accepting "secure storage", and tie deletion to an event you will notice, such as acceptance of the final report.

Clause 12: what safe-harbour wording is, and what it is not

Safe-harbour wording in a testing letter is a promise between the two parties named in it. In the template, the business agrees not to treat testing inside the letter's limits as unauthorised and not to bring a claim against the provider or the named testers on that basis.

It also agrees to say in writing, if a host, a third-party service or a law enforcement body asks, whether specific traffic fell within the letter.

It is written as a promise from the business alone, and it does not speak for the police, a regulator, your host or any third-party service. What effect the wording has in law is for your solicitor to advise, so treat it as drafting for them to review, change or remove. It also covers nothing outside the letter's limits, which is one more reason to keep those limits exact.

Final checks before anyone signs

Run through this list with the completed letter, its schedules and the attachments in front of you.

  • A solicitor has reviewed the letter for your business and the systems involved, including the safe-harbour wording.
  • The signatory's authority is evidenced, the evidence is attached, and clause 2.4 shows what the provider checked.
  • Every hostname, path and address in Schedule A has its proof of control recorded, and anything without proof has been removed.
  • Each host and third-party service has a Schedule B entry with the terms read, the date read, and any notice or approval attached.
  • The window, time zone, blackout periods and source addresses match the scope document and the rules of engagement.
  • The test accounts in Schedule C exist, any real customer data in them is described, and someone is named to reset or remove them afterwards.
  • Both contacts know the stop phrase, and each knows who to call if the other does not answer.
  • If production is in scope, a restore from the backup named in clause 9.3 has been tested.

Frequently asked questions

No document can promise that, and this page gives no view on whether any test is lawful. The letter records who gave permission, on what authority, for which systems and within which limits. Whether that is enough for a particular test is a question for your solicitor, with the letter, the evidence of authority and the host permissions in front of them.

Someone with authority to approve testing for the business that controls every target, whose authority you can show on paper. Who that is depends on how your business is set up, so confirm it with your solicitor and attach the evidence, such as a board resolution or a written delegation naming the systems and the period. The person who requested the test, or who manages the website, is not automatically that person.

That depends on who your business has authorised to commit it, which is a question to settle with your solicitor before anyone signs. If your business does delegate the signature, the letter should say so and attach the delegation. An agency or IT provider often holds the hosting and DNS logins, which makes it the natural party to publish a domain-control record. Holding a login is not the same as having authority to approve testing.

No. Your letter speaks for what your business controls. A host, cloud provider or third-party service has its own terms, which may limit testing on its platform or ask for notice or written approval first. Read the terms for each target, record the outcome and the date in Schedule B, and attach any approval. A service you cannot get permission for belongs in the exclusions.

Usually, yes. Providers use consent letter, authorisation form and authorisation to test letter for the same kind of document. Judge it by its content rather than its title: if the letter you are given leaves out the signatory's authority, proof of control, host permissions or a way to stop testing, ask for them to be added before anyone signs.

Do not rely on it as one. It is a promise from the business to the provider named in the letter, covering testing inside the letter's limits. It does not speak for the police, a regulator, a host or any other third party. What effect it has in law is for your solicitor to advise, so treat it as drafting for them to review.

If the retest falls after the window in clause 6, or needs new targets, accounts or source addresses, yes: sign a variation or a fresh letter before it starts. The template ends the permission when its window closes, so that a later retest is approved by someone with authority at that time, against the system as it then stands.

Yes. Clever Ops starts testing once the written scope is agreed and an authorisation has been signed for each target. The template on this page is not Clever Ops' own letter. It is a tool for checking any letter you are asked to sign, with any provider, against the clauses above. If Clever Ops built or hosts the system, the engagement is a security review rather than an independent test, and the report states who built and who hosts it.

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.