Establishing secure connection…Loading editor…Preparing document…

Security Intrusion Test Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Security Intrusion Test Request

Parties

Client Name:

Provider Name:

Recitals

WHEREAS, Client requires an assessment of its information systems and infrastructure to identify potential security weaknesses and to validate controls through controlled intrusion testing; and

WHEREAS, Provider represents that it has the experience, personnel, and technical capability to perform controlled security intrusion testing in accordance with the parameters set forth in this Request; and

WHEREAS, the parties desire to define the scope, timing, payment, and legal terms governing the requested testing engagement.

Request Details

Scope of Work

The Provider shall perform the intrusion testing services described below. The parties agree that tests will be performed only against systems and assets explicitly listed as targets and during the agreed test window. Provider will refrain from actions that are outside the authorized scope and will immediately cease any activity upon receiving a written stop order from Client.

Planned Test Window Start:   End:

Estimated Effort:

Report Delivery Method:

Report Delivery Timing:

Payment Terms

Client shall pay Provider for services as set forth below. All monetary amounts are stated in U.S. dollars unless otherwise specified.

Term and Termination

This Request commences on the Start Date and continues until the completion of the Services or the End Date specified below unless earlier terminated in accordance with this section.

Start Date:   End Date:

Either party may terminate this engagement for material breach that is not cured within days' written notice. Termination does not relieve Client of payment obligations for work performed prior to termination.

Confidentiality

Provider will treat all non-public information obtained from Client in the course of the engagement as Confidential Information. Provider will not disclose such information except to personnel and subcontractors who have a need to know and who are bound by confidentiality obligations at least as protective as those herein. Client and Provider will implement reasonable technical and organizational measures to protect Confidential Information. Test findings, exploit details, and vulnerability data shall be disclosed only to Client and its authorized representatives unless otherwise required by law, in which case notification to the other party will be provided to the extent permitted.

Liability, Indemnification, and Risk

Client acknowledges that intrusion testing carries inherent risk of service disruption. Client authorizes Provider to perform the authorized tests and accepts responsibility for obtaining any third-party consents necessary to permit testing. Provider will exercise commercially reasonable care to avoid unnecessary disruption. Provider's liability for direct damages arising from Provider's gross negligence or willful misconduct is limited to the total fees paid under this Request. Neither party will be liable for indirect, incidental, consequential, special, or punitive damages. Client shall indemnify and hold Provider harmless from claims arising from Client's failure to obtain required consents or incorrect target listings.

Data Handling and Retention

Provider will retain logs, exploit artifacts, and copies of Client data only for the period necessary to complete deliverables and for no longer than days, except as required by law. Upon Client request or upon expiration of the retention period, Provider will securely destroy or return such data and provide certification of destruction when requested.

Governing Law; Entire Agreement

This Request shall be governed by and construed in accordance with the laws of the state specified below. Any legal action relating to this Request shall be brought in the state and federal courts located in that jurisdiction.

Governing State:

This Request, together with any incorporated attachments, exhibits, and the parties' written agreements referenced herein, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior representations, negotiations, and agreements, whether written or oral.

Representations and Authorization

By submitting and signing this Request, Client represents that it is the owner or authorized representative of the systems and assets identified herein and that it has obtained all necessary consents to permit the Provider to conduct authorized testing. Provider represents that it will conduct testing in a professional manner in accordance with industry standard methodologies.

Additional Terms or Special Instructions:

By signing below, the undersigned authorized representatives of each party acknowledge and agree to the terms set forth in this Security Intrusion Test Request and certify that the information provided is true and accurate.

Client:

By:

Date:

Provider:

By:

Date:

Enter text✕

What a Security Intrusion Test Request Is

A Security Intrusion Test Request is a formal document used to authorize, scope, and schedule controlled security testing against an information system or application. It records who requests the test, specifies permitted targets and methods, defines timing and duration, and documents safety controls and escalation contacts. The request establishes legal and operational boundaries so testers and internal teams share a clear, auditable understanding before active testing begins.

Why a Formal Request Matters for Risk Management

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.

Why a Formal Request Matters for Risk Management

Who Typically Prepares and Reviews This Request

Security Intrusion Test Requests are usually created by security teams or third-party vendors and routed to system owners, legal, and compliance for approval.

  • Security Operations: initiates scope, target lists, and required safeguards; ensures tests align with SLAs and incident response plans.
  • IT / System Owners: approve scope for their systems, provide maintenance windows, and confirm recovery procedures are in place.
  • Legal / Compliance: review authority to test, data handling restrictions, and any applicable regulator or contract limitations.

Approval signatures from each stakeholder provide an auditable record that testing was authorized and coordinated across teams.

Core Elements of a Complete Request

A professional request includes administrative details, an exact scope of work, accepted techniques, scheduling constraints, communications plans, and post-test deliverables to ensure safe and accountable testing.

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.

Test Scope

List explicit target IPs, hostnames, URLs, and excluded systems. State permitted ports, applications, and any segmentation or honeypot exclusions to avoid unintended impact.

Authorized Methods

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.

Schedule and Window

Define exact start/end dates, daily testing windows, blackout periods, and maintenance windows so operations and avoidance of business-critical times are clear.

Safety Controls

Require procedures including test account credentials, rollback steps, contact points for outages, and rules for immediate cessation of testing if service degradation is detected.

Reporting and Deliverables

State required deliverables: preliminary findings, final technical report, executive summary, remediation verification, and expected delivery timelines.

Required Data Elements

Requester: Name, role, contact
Target List: IP/URL/hostnames
Authorized Methods: Allowed techniques
Testing Window: Start/end times
Emergency Contact: 24/7 phone/email
Approval Signatures: Security, IT, Legal

Step-by-Step: Completing the Request

Follow these steps to prepare a clear, approvable request and minimize review cycles.

  • 01
    Draft Scope: List precise assets and exclusions.
  • 02
    Define Methods: State permitted tools and techniques.
  • 03
    Set Schedule: Choose safe testing windows.
  • 04
    Obtain Approvals: Collect signatures from security, IT, and legal.

How to Configure an Online Authorization Workflow

Set up routing, approvals, and notifications so each stakeholder receives the request and signing prompts in the correct order.

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

Digital Signing and Platform Capabilities

Choose a platform that supports secure eSigning, audit trails, and conditional routing for multi-stakeholder approvals.

  • File Formats: PDF, DOCX
  • Integrations: Salesforce, NetSuite, Google Workspace
  • Authentication: Email, SMS, SSO

Ensure the platform can retain tamper-evident copies, produce a certificate of completion, and support any regulatory requirements such as HIPAA where applicable.

Where to Send and How Submissions Are Processed

A standard submission flow routes the completed request to reviewers, records approvals, and notifies test coordinators and monitoring teams.

  • Submit Request: Upload form and supporting asset list to the approval workflow.
  • Automated Routing: System routes to security, IT owner, and legal per pre-set order.
  • Approval Capture: Each approver signs; audit trail timestamps each action.
  • Scheduling: On approval, coordinator confirms test window and notifies monitoring teams.

Typical Timelines and Response Expectations

Plan realistic lead times to allow security review, legal clearance, and scheduling with operations and third-party vendors.

Request Lead Time:

Allow 5–10 business days for full review and approvals

Emergency Tests:

Short-notice tests require explicit managerial approval

Test Window Confirmation:

Coordinator should confirm 48–72 hours before start

Pre-test Notification:

Notify SOC/monitoring at least 24 hours prior

Report Delivery:

Preliminary findings within 7 days; final report within 30 days

Common Mistakes to Avoid

  • Vague scope descriptions that omit IP addresses or hostnames, causing tests to be delayed or blocked by system owners.
  • Failing to list excluded systems such as production databases, backups, or safety-critical infrastructure, which can lead to outages.
  • Not specifying acceptable testing techniques or credential use, which increases legal and operational exposure for testers and requesters.
  • Omitting emergency contacts or escalation procedures, delaying incident response and increasing business risk if a test causes disruption.

Risks and Consequences of an Improper Request

Operational Outage: Service disruption
Contract Breach: Third-party SLA violations
Legal Liability: Unauthorized access claims
Data Exposure: PHI/PII compromise
Regulatory Penalties: HIPAA or FTC risk
Reputational Harm: Customer trust loss

eSignature Cost and Feature Comparison

Compare common cost and capability dimensions for high-volume eSignature usage; signNow is listed first for straightforward comparison.

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

Frequently Asked Questions

Answers to common questions about authorization, legality, retention, and electronic signing for Security Intrusion Test Requests.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users