Requester Details
Identify the requesting organization, contact name, role, email, and phone so testers and stakeholders have a primary point of contact for approvals and incident escalation.
Using a structured request reduces legal and operational risk by documenting consent, scope, and constraints; it clarifies authorization for testers and notifies stakeholders. This helps ensure tests do not trigger incident response, violate policies, or breach third-party contracts.
Security Intrusion Test Requests are usually created by security teams or third-party vendors and routed to system owners, legal, and compliance for approval.
Approval signatures from each stakeholder provide an auditable record that testing was authorized and coordinated across teams.
Identify the requesting organization, contact name, role, email, and phone so testers and stakeholders have a primary point of contact for approvals and incident escalation.
List explicit target IPs, hostnames, URLs, and excluded systems. State permitted ports, applications, and any segmentation or honeypot exclusions to avoid unintended impact.
Specify allowed testing techniques (e.g., external black-box, authenticated scanning, social engineering excluded) and disallowed actions such as destructive payloads or data exfiltration attempts.
Define exact start/end dates, daily testing windows, blackout periods, and maintenance windows so operations and avoidance of business-critical times are clear.
Require procedures including test account credentials, rollback steps, contact points for outages, and rules for immediate cessation of testing if service degradation is detected.
State required deliverables: preliminary findings, final technical report, executive summary, remediation verification, and expected delivery timelines.
| Field | Configuration |
|---|---|
| Routing Order | Requester → Security → System Owner → Legal |
| Authentication | Email invite with optional SMS code for approvers |
| Notifications | Auto-reminders at 24h and 72h if unsigned |
| Audit Capture | Enable full audit trail and time-stamped approvals |
Choose a platform that supports secure eSigning, audit trails, and conditional routing for multi-stakeholder approvals.
Ensure the platform can retain tamper-evident copies, produce a certificate of completion, and support any regulatory requirements such as HIPAA where applicable.
Allow 5–10 business days for full review and approvals
Short-notice tests require explicit managerial approval
Coordinator should confirm 48–72 hours before start
Notify SOC/monitoring at least 24 hours prior
Preliminary findings within 7 days; final report within 30 days
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/yr | Varies | Varies | Varies |