Scope
Asset list and boundaries: IP ranges, hostnames, cloud services, mobile apps, API endpoints, and third-party integrations that are in-scope or out-of-scope for testing.
A consistent pentest submission form reduces ambiguity, shortens onboarding time, and documents authorization for potentially disruptive testing activities. It helps satisfy legal, compliance, and audit requirements while protecting both the client and the testing team from unintended impacts.
Teams complete the form before testing to ensure proper scope, legal authority, and safe test execution.
Shared review by these parties reduces rework and supports a clear chain of responsibility during and after testing.
Asset list and boundaries: IP ranges, hostnames, cloud services, mobile apps, API endpoints, and third-party integrations that are in-scope or out-of-scope for testing.
Primary and escalation contacts with phone, email, and time zone; include operations, security, application owners, and an emergency on-call person for test-day incidents.
Credentials, test accounts, VPN or jump-host instructions, MFA bypass arrangements if needed, and the least-privilege account types provided for testing.
Signed authorization clause naming the testing provider, grant of limited permission to test, indemnities, and acceptance of potential service disruption risks.
Permitted and prohibited methods (e.g., social engineering, destructive tests, load testing) and any specific limitations tied to production systems.
Expected report format, confidentiality requirements, remediation timelines, retest policy, and evidence retention expectations.
| Field | Configuration |
|---|---|
| Contact Fields | Require name, title, email, phone; validate email format |
| Scope Field | Multi-line text with CSV upload option for IPs and hostnames |
| Access Upload | Secure file field for credentials with encryption at rest |
| Approval Step | Sequential signer flow with audit trail and timestamp |
Choose a platform that supports secure uploads, audit trails, and role-based access for sensitive submission data.
Ensure the platform preserves tamper-evident audit trails, encrypts data in transit and at rest, and supports secure role-based sharing for reports and artifacts.
Submit at least 7–10 business days before desired start date.
Internal approval often completes within 2–5 business days.
Agree specific start/end timestamps and time zone.
Preliminary findings often provided within 3–10 business days.
Allow 2–4 weeks for patching and verified retest scheduling.
| 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 required | 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 |