Scope of Work
Define systems, IP ranges, applications, and excluded assets plus permitted techniques such as external scans, authenticated tests, and social engineering.
A formal agreement reduces legal ambiguity, limits operational risk, and documents consent for intrusive testing. It protects both parties by defining permitted actions, required approvals, data protection measures, and dispute-resolution procedures.
Organizations and independent security providers use this agreement to establish expectations and legal protection before testing begins.
The agreement helps align technical, legal, and business stakeholders so testing proceeds with documented authorization and clear remediation pathways.
Define systems, IP ranges, applications, and excluded assets plus permitted techniques such as external scans, authenticated tests, and social engineering.
Set test windows, blackout periods, and expected report delivery dates to avoid operational conflicts and allow coordination with change windows.
Specify allowable tools, attack intensity limits, escalation procedures for high-severity findings, and immediate stop conditions for critical failures.
Describe handling of sensitive data, encrypted transport and storage, deletion timelines, and breach notification responsibilities for exposed data.
Establish caps on liability, indemnification language, and insurance requirements to manage financial and legal exposure from testing activity.
List final outputs such as executive summary, technical report, proof-of-concept details, remediation guidance, and retest criteria.
| Field | Configuration |
|---|---|
| Authentication Method | Email link, SMS code, or stronger 2FA |
| Signer Order | Sequential or parallel signing flow |
| Conditional Fields | Show remediation retest clause only if requested |
| Audit Trail | Enable timestamps and IP capture |
Use a secure eSignature platform that supports audit trails, encryption, and appropriate signer authentication.
Ensure the chosen platform can export a tamper-evident signed PDF and retain an audit record to demonstrate intent, attribution, and retention for legal enforceability.
Provide at least 5 business days' lead time
Schedule agreed start and end date
Initial critical alerts within 24–72 hours
Typically within 14–30 calendar days after testing
Remediation verification within 30–60 days
A hospital schedules quarterly external penetration tests focused on patient portals
A cloud software provider contracts a third-party penetration test before certification
| 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 | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | Varies by vendor |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA required) | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |