Scope
Lists systems, domains, IP ranges, and application endpoints included and excluded; defines test depth such as external, internal, web app, API, or wireless testing; identifies credentialed versus non-credentialed approaches in detail.
A precise Security Penetration Test Offer protects both parties by documenting consent, permitted test activities, and legal boundaries. It reduces the risk of accidental disruption, clarifies remediation commitments, and supports compliance reviews for regulated data such as PHI or student records.
Relevant teams usually include security, IT operations, compliance, and procurement.
The signed offer ensures a coordinated test with documented authorization and agreed safeguards.
Lists systems, domains, IP ranges, and application endpoints included and excluded; defines test depth such as external, internal, web app, API, or wireless testing; identifies credentialed versus non-credentialed approaches in detail.
Describes the goals of the engagement (vulnerability discovery, exploit validation, business-impact assessment, compliance mapping) and the expected reporting format such as executive summary plus technical findings.
Specifies permitted methods (active scanning, exploitation, social engineering if authorized), rate limits, hours for intrusive testing, and safety controls to avoid degradation of production services.
Defines the testing window with exact start and end dates, blackout periods, and escalation contacts for incidents discovered during the engagement.
Details final deliverables including interim findings, vulnerability severity mapping, reproducible reproduction steps, mitigation recommendations, and a timeline for a formal final report.
Covers authorization to test, liability limits, indemnification, data handling, confidentiality, insurance coverage, and acceptance criteria for remediation or retesting obligations.
| Field | Configuration |
|---|---|
| Automatic detection | Enable automatic field recognition to map names, dates, and addresses from templates. |
| Conditional fields | Show or hide technical sections based on selected test types to reduce signer confusion. |
| Signer order | Set sequential signing for vendor acceptance followed by client authorization. |
| Authentication | Require email plus SMS or KBA for higher-assurance signers when handling regulated data. |
Choose a platform that supports secure signatures, audit trails, and integrations with your workflow tools.
Ensure the chosen platform preserves a tamper-evident audit trail, supports required authentication levels, and can export signed offers and certificates for secure long-term storage.
Typically 30–90 days for acceptance.
Schedule within 1–14 days after acceptance.
Commonly 1–14 calendar days depending on scope.
Usually 7–21 business days after test completion.
Often completed within 30–60 days after fixes.
| 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 credit card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Optica provided a clear scope and testing window to vendors
The organization required HIPAA-specific handling and a BAA
The Chief Information Security Officer typically signs when the engagement affects enterprise security posture and requires approval of technical scope, risk acceptance, and remediation obligations across business units.
An IT or network manager may sign for operational approvals where the engagement is limited to a particular infrastructure segment and the manager has authority to schedule maintenance windows and grant access.