Step 2: Authorization

Example Authorization Agreement

Before we test anything, you sign a short document like this one. It's not complicated — just the essentials to protect both sides. Here's a filled-out example for a fictional company.

A.K.S Security, LLC
Web Application Security
844-955-HACK (4225)
info@aks-llc.com
DFW Metroplex

Security Testing Authorization

This document authorizes A.K.S Security, LLC ("Tester") to perform security testing on systems owned and operated by the undersigned party ("Client") under the terms described below.

1. Client Information

Company: Acme Company, LLC
Authorized Representative: Jane Smith, CEO
Email: jane@acmecompany.com
Phone: (555) 123-4567

2. Authorized Targets

The Client authorizes the Tester to perform security testing on all company-owned assets that are publicly accessible from the internet. The Tester will attempt to discover and access anything that an external attacker could reach — including but not limited to web applications, admin panels, APIs, databases, file storage, subdomains, and any other services exposed to the internet.

The Client confirms it owns or has the legal authority to authorize testing against all company assets, including but not limited to:

  • www.acmecompany.com
  • portal.acmecompany.com
  • api.acmecompany.com

Testing should exclude the following:  

3. Exclusions

Testing is limited exclusively to the systems listed above. The Tester will not attempt to access, test, or probe any third-party services, hosting infrastructure, payment processors, or any systems not explicitly listed in Section 2. Any systems discovered during testing that are owned by third parties will not be tested.

4. Authorization & Data Handling

The undersigned confirms that they have the legal authority to grant this permission. The Client hereby authorizes A.K.S Security, LLC to perform external security testing against the authorized targets — including automated scanning, manual testing, and attempted exploitation of discovered vulnerabilities. This authorization is valid from the date of signature through the completion of the agreed-upon engagement.

The Client understands that during the course of testing, the Tester may encounter, view, or temporarily download sensitive data — including but not limited to customer records, financial information, personally identifiable information (PII), credentials, and other confidential business data. This is necessary to confirm and document the severity of discovered vulnerabilities, and mirrors the same access a real attacker would obtain. Any such data will be handled within the Tester's secure environment, used solely as evidence for the assessment report, and permanently deleted upon completion of the engagement.

5. Confidentiality

All findings, methods, communications, and materials related to this engagement are confidential. Neither party will disclose any details of this engagement to any third party without prior written consent from the other party. This obligation survives the termination of the engagement indefinitely.

6. Point of Contact

If a critical vulnerability is discovered that poses immediate risk to the Client's systems or data, the Tester will notify the Client immediately using the contact information provided in Section 1.

Client

Jane Smith

Jane Smith, CEO

Acme Company, LLC

Date: March 15, 2026

Tester

Eric Turner

Eric Turner, Owner

A.K.S Security, LLC

Date: March 15, 2026

This is a fictional example. The actual document you sign will be tailored to your specific systems and situation, but it looks a lot like this. Short, clear, and to the point — nothing you'd need a lawyer to read.