Scope of Work
Specify assets, IP ranges, applications, and test types (external/internal/black-box/white-box). List excluded systems and third-party boundaries to prevent unintended impact.
A clear Legal Penetration Test Agreement allocates responsibility, documents consent to testing, and limits legal and operational risk. It protects both the organization and testers by setting boundaries for methods, systems, and data handling while establishing procedures for incident escalation and remediation.
Final signatories usually include an authorized business representative and a designated security contact from the provider; legal and procurement approvals are commonly required before tests begin.
Typically reviews and approves scope, risk thresholds, and remediation expectations. The CSO or equivalent certifies that testing aligns with organizational risk tolerance and coordinates internal stakeholders such as IT, legal, and incident response.
A senior representative from the vendor (owner, COO, or authorized signatory) accepts the engagement, confirms insurance limits and technical approach, and commits to rules of engagement, evidence retention, and non-disclosure obligations.
Specify assets, IP ranges, applications, and test types (external/internal/black-box/white-box). List excluded systems and third-party boundaries to prevent unintended impact.
Define acceptable techniques, times of testing, escalation contacts, and any prohibited actions such as destructive testing or social engineering against employees.
A clear written authorization clause that confirms the organization grants testers permission to access specified systems and that testing will not be treated as unauthorized access.
Describe how sensitive data (PII, PHI) will be handled, encrypted, segregated, and destroyed; include any required privacy or HIPAA addenda.
Set timelines for preliminary and final reports, expected format, severity ratings, and procedures for secure delivery of findings.
Allocate risks, set insurance minimums, state caps on liability, and provide mutual indemnities where appropriate to manage legal exposure.
| Field | Recommended Setting |
|---|---|
| Signer Authentication | Email + SMS code or SSO where available |
| Access Window | Time-boxed to the testing window start/end |
| Evidence Retention | Store A/V and logs for 3–7 years |
| Escalation | Notify security and legal contacts on incidents |
Verify the platform can produce a tamper-evident audit trail, retain evidence per policy, and support the integrations your team relies on for automated tracking and ticketing.
Provide at least 14 calendar days before testing begins
Define start and end dates; avoid indefinite ranges
Deliver preliminary report within 3–7 business days
Deliver final report within 10–30 calendar days
Schedule retest or verification within agreed timeframe
Agreement signed and archived before any testing occurs
Stakeholders and affected vendors are informed
Tests performed within authorized window
Final report issued and remediation confirmed
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Business Premium tier) | Yes | Yes | Yes | Yes |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Optica adopted a standard testing agreement to reduce back-and-forth during procurement and improve scheduling efficiency
Tech Data formalized rules of engagement to protect production systems during vendor testing
Include strong non-disclosure terms and secure delivery methods for reports to prevent sensitive findings from being disclosed or misused.
A signed authorization clause prevents misinterpretation by third parties and defends testers against claims of unauthorized access.
Require secure transfer, storage, and destruction procedures for logs, recordings, and proof-of-concept artifacts to maintain chain-of-custody.
Specify minimum professional liability and cyber insurance limits and require certificates of insurance prior to testing.