Authorisation-to-Test Agreement
The draft agreement a website owner signs before we run any active, authorised security testing: scope, ownership proof, limits and safeguards.
Last updated · draft, not yet in effect
1. Purpose
This agreement records that the client authorises Odesstra (Pty) Ltd, trading as Odesstra ("the tester"), to carry out the security testing described in the schedules, on the systems listed, within the window stated. Testing systems without permission can be a crime (including under South Africa's Cybercrimes Act 19 of 2020 and similar laws elsewhere). No active testing will start until this agreement is signed and ownership has been verified.
2. Proof of ownership or control
Before testing, and again before each scheduled test, the client must prove control of every domain in scope using one of:
- a DNS TXT record with a value we provide;
- a file we provide, placed at a path under
/.well-known/on the domain; or - a meta tag we provide, added to the home page.
If verification fails or is removed, testing of that domain stops until it is restored.
3. Who signs
The person signing confirms that they are authorised to grant this permission on behalf of the client, and that the client owns or has the right to authorise testing of every system in scope, including any hosted by third parties (for example a hosting company) whose own terms may require notice or consent. The agreement records the signer's full name, role, organisation, email address and the date and time of signing.
4. Scope, test types and window
- [Schedule A: scope] — the exact domains, sub-domains and IP addresses that may be tested. Anything not listed is out of scope, including systems that in-scope pages link or redirect to.
- [Schedule B: allowed test types] — for example external vulnerability scanning with safe, non-intrusive settings, TLS configuration testing, and named manual tests. Any heavier testing must be listed explicitly.
- [Schedule C: testing window] — the dates, days and times when testing may run, and the time zone.
- Expiry — this authorisation ends on [expiry date], or earlier if either party ends it.
5. Safeguards and limits
- Every test runs with a requests-per-second limit, a time budget and a kill switch that stops it immediately.
- Tests detect and report. The tester will not exploit vulnerabilities, extract or alter data, run destructive payloads, attempt logins against real user accounts, or keep any access.
- The safest settings are used by default; anything heavier needs the client's explicit written opt-in.
- Automated testing can still occasionally slow or disrupt a system. The client should keep current backups.
6. Emergency contact and stopping a test
The client names an emergency contact who can be reached during the testing window: [Schedule D: emergency contact name, role, phone and email]. Either party can stop testing at any time by contacting the other. If a test appears to affect the client's systems, the tester stops, notifies the emergency contact and investigates before resuming.
7. Confidentiality and data handling
Findings, evidence and reports are confidential client information. The tester will keep them only as long as needed to deliver and support the service, restrict access to people who need it, protect them with appropriate safeguards, and process any personal information encountered only as needed for the testing and in line with POPIA and, where applicable, the GDPR. Findings will not be shared with third parties, including AI services, unless the client agrees in writing.
8. Responsibility
Testing reports what was found within the agreed scope and window. It cannot find every vulnerability and is not a guarantee that a system is secure. Limits of liability, fees and other commercial terms are set out in [Schedule E: commercial terms], subject to any liability that cannot lawfully be excluded.
9. Ending this agreement
Either party may end this agreement at any time by written notice. Testing stops immediately. On request, the tester will delete or return client findings, except where it must keep records by law. This agreement is governed by the laws of the Republic of South Africa.
10. Signatures
Signed for the client: [name], [role], [organisation], [date]. Signed for the tester: [name], [role], [date]. An immutable copy of the signed agreement is kept by both parties.