Establishing secure connection…Loading editor…Preparing document…

Security Penetration Test Offer

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

SECURITY PENETRATION TEST OFFER

Offer Date:     Provider Name:     Client Name:

WHEREAS

WHEREAS, Provider represents that it is duly qualified and experienced in performing authorized security assessments, vulnerability scanning, and penetration testing against information systems and networks; and

WHEREAS, Client seeks to engage Provider to perform a security penetration test of specified information assets under the terms and conditions set forth in this Offer; and

WHEREAS, Provider is willing to provide the services described herein subject to Client's authorization, scope limitations, and payment of fees.

SCOPE OF WORK

Provider shall perform a penetration test in accordance with the scope selected below and the detailed description provided by Client. The objective is to identify security weaknesses that could permit unauthorized access, data disclosure, service disruption, or other adverse business impact. Testing shall be performed in a professional manner consistent with industry standards and applicable laws.






Start Date:    End Date:    Business Hours:

REPORTING AND DELIVERABLES

Provider will deliver an interim findings summary (if requested) and a final written report documenting identified vulnerabilities, evidence, risk ratings, and recommended remediation steps. Provider shall not disclose exploit code or excessive detail that would enable widespread exploitation beyond Client's remediation activities without Client's consent.

Retest after remediation included:    Interim report required:

PAYMENT TERMS

Client shall pay Provider the fees set forth below in consideration for the services rendered. Fees are exclusive of taxes and any third-party costs unless otherwise stated.

TERM AND TERMINATION

This Offer commences on Start Date and continues until End Date, unless earlier terminated in accordance with this section. Either party may terminate for convenience upon prior written notice to the other party given at least the required notice period. Termination does not relieve Client of payment obligations for services performed prior to termination.

Start Date:    End Date:    Notice Period (days):

CONFIDENTIALITY

Each party shall keep confidential all non-public information disclosed in connection with this Offer, including test results, vulnerabilities, and remediation details (collectively, Confidential Information). Provider will use Confidential Information solely to perform the services and will not disclose such information to third parties except to personnel and subcontractors who have a need to know and are bound by confidentiality obligations at least as protective as those herein. Confidential Information does not include information that is or becomes public other than by a breach of this Offer, is lawfully received from a third party, or is required to be disclosed by law or regulation, provided the disclosing party gives prompt notice to the other party and cooperates in any lawful effort to limit the disclosure.

Upon completion or termination, Provider shall, at Client's election, return or securely destroy Client Confidential Information in Provider's possession, and shall certify such destruction in writing upon Client's request.

DATA HANDLING

Provider will collect only information necessary to perform the services. Provider shall protect collected data using commercially reasonable administrative, physical, and technical safeguards. Provider will retain test data only for the period reasonably required to perform the services and deliver reports, after which Provider will remove or destroy such data in accordance with Client's instruction.

LIMITATION OF LIABILITY AND INDEMNITY

Except for willful misconduct or gross negligence, Provider's aggregate liability for any claim arising out of or related to this Offer, whether in contract, tort, or otherwise, shall not exceed the total fees paid to Provider for the services under this Offer. In no event shall Provider be liable for incidental, consequential, special, or punitive damages, including loss of profits, loss of data, or business interruption.

Client shall indemnify and hold Provider harmless from and against claims arising from Client's intentional misuse of deliverables, failure to authorize tests, or violation of third-party rights, except to the extent such claims result from Provider's breach of this Offer or gross negligence.

COMPLIANCE WITH LAWS

Provider and Client shall comply with applicable laws, regulations, and contractual obligations of third parties in the performance of the services. Client represents that it has the authority to authorize the specified testing against the systems and assets identified in this Offer.

GOVERNING LAW

This Offer shall be governed by and construed in accordance with the laws of the State of , without regard to conflict of laws principles.

ENTIRE AGREEMENT

This Offer, together with any statements of work, attachments, and accepted amendments in writing signed by both parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior or contemporaneous understandings, agreements, representations, and warranties, whether written or oral.

ACCEPTANCE

To accept this Offer, Client must sign below and return a signed copy to Provider. Acceptance constitutes Client's agreement to and authorization of the scope, schedule, and terms herein.

Provider

Printed Name:

By:

Date:

Client

Printed Name:

By:

Date:

Enter text✕

What a Security Penetration Test Offer Is and what it contains

A Security Penetration Test Offer is a formal engagement document that proposes a controlled security assessment of systems, applications, or networks. It defines scope, objectives, permitted methods, testing windows, deliverables, pricing, liability limits, and acceptance criteria. The document establishes responsibilities for both the client and the testing vendor, defines exclusions and out-of-scope assets, and sets confidentiality and data-handling obligations. It often includes signature blocks for authorized representatives, timelines for remediation, and terms for follow-up validation. Properly prepared offers reduce legal ambiguity and align expectations before active testing begins.

Why a clear offer matters for risk management

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.

Why a clear offer matters for risk management

Typical organizations and teams that issue or respond to offers

Relevant teams usually include security, IT operations, compliance, and procurement.

  • Internal security or risk teams handling vendor assessments and contract terms
  • IT/Network operations organizing test windows and access privileges for vendors
  • Procurement or legal teams reviewing liability, insurance, and service terms

The signed offer ensures a coordinated test with documented authorization and agreed safeguards.

Essential elements to include in a professional offer

A comprehensive Security Penetration Test Offer groups technical, commercial, and legal terms so stakeholders can approve and act without ambiguity.

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.

Objectives

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.

Allowed Techniques

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.

Schedule

Defines the testing window with exact start and end dates, blackout periods, and escalation contacts for incidents discovered during the engagement.

Deliverables

Details final deliverables including interim findings, vulnerability severity mapping, reproducible reproduction steps, mitigation recommendations, and a timeline for a formal final report.

Legal Terms

Covers authorization to test, liability limits, indemnification, data handling, confidentiality, insurance coverage, and acceptance criteria for remediation or retesting obligations.

Step-by-step process to prepare and approve the offer

Follow an ordered checklist to assemble technical, commercial, and legal inputs before issuing the offer.

  • 01
    Gather asset list: Compile exact hostnames, IPs, and application endpoints for inclusion.
  • 02
    Define objectives: Agree on testing goals: coverage, depth, and success criteria.
  • 03
    Confirm legal terms: Include liability, insurance, confidentiality, and permitted techniques.
  • 04
    Obtain signatures: Get authorized signers to approve and retain an executed copy.

How to configure a digital workflow for the offer

Set up automation fields, signer order, and authentication to streamline execution and evidence capture.

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.

Technical considerations for eSubmission and evidence capture

Choose a platform that supports secure signatures, audit trails, and integrations with your workflow tools.

  • Integrations: Supports Salesforce, NetSuite, Google Workspace, and Microsoft 365 integrations.
  • File formats: Accepts PDF, DOCX, and flat text reports for archival.
  • Authentication: Offers multi-factor options and audit logging for signer attribution.

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.

Where to send the completed offer and how it is processed

A signed offer should be routed to operations, legal, and the vendor to enable scheduling and test authorization.

  • Security team: Retain an executed copy for incident escalation and change control.
  • Testing vendor: Vendor receives authorization to schedule and begin testing.
  • Procurement or legal: Store the signed offer for contract and billing reconciliation.
  • Compliance archive: File a copy with records that support HIPAA or other audits.

Common timelines and typical delivery expectations

Penetration test offers include scheduling milestones and delivery dates that stakeholders must track.

Offer validity period:

Typically 30–90 days for acceptance.

Kickoff scheduling:

Schedule within 1–14 days after acceptance.

Testing window:

Commonly 1–14 calendar days depending on scope.

Final report delivery:

Usually 7–21 business days after test completion.

Remediation retest:

Often completed within 30–60 days after fixes.

Required information fields for the offer

Client name: Full legal entity name
Contact details: Phone and email for escalation
Scope list: IP ranges and hostnames
Test window: Exact start and end
Authorized signer: Name, title, signature
Data handling: PHI/PCI handling notes

Common preparation mistakes to avoid

  • Vague scope descriptions that omit critical assets lead to unexpected outages and disputes.
  • Missing or insufficient authorization for credentialed tests causes delays and potential legal exposure.
  • Failing to schedule blackout periods can result in testing during high-traffic windows and service disruption.
  • Not specifying data-handling or retention rules can create noncompliance with HIPAA or other regulations.

Risks and potential consequences of an incomplete or incorrect offer

Service disruption: Operational outages risk
Legal disputes: Contract ambiguity risk
Regulatory fines: HIPAA or other penalties
Liability exposure: Uncapped vendor claims
Invalid authorization: Unauthorized testing findings
Data mishandling: Confidentiality breaches

eSignature vendor comparison for executing the offer

A concise pricing and capability comparison for common eSignature vendors. signNow is listed first per standard comparison format; features are high-level and intended for initial vendor selection only.

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

Real-world examples of offer usage and outcomes

These examples show how organizations structured offers and realized predictable testing outcomes while preserving compliance and uptime.

Optica Ventures (COO)

Optica provided a clear scope and testing window to vendors

  • Kept tests credentialed only against non-production systems
  • The result was rapid findings and minimal operational impact while preserving customer experience and compliance.

Fertility Centers of Illinois (Founder)

The organization required HIPAA-specific handling and a BAA

  • Vendor agreed to encryption and access controls
  • This reduced legal risk and allowed remediation decisions to proceed with both clinical and IT leadership aligned.

Who typically signs the offer and why their role matters

CISO — Authorized Signer

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.

IT Manager — Operational Signer

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.

Practical tips to ensure a smooth engagement

Apply these practical practices to reduce friction, limit downtime, and maintain clear audit trails during and after testing.

Define clear acceptance criteria
Specify how findings will be classified, remediation expectations, and the criteria for an acceptable retest to avoid disagreements after remediation work is complete.
Limit blast radius
Exclude critical production processes and schedule high-impact tests during maintenance windows; document rollback and escalation plans to protect operations.
Preserve evidence
Require tamper-evident logs and secure transfer of proof-of-concept artifacts so remediation teams can reproduce and verify fixes reliably.
Coordinate stakeholders
Share the offer with legal, risk, ops, and business owners before signing to ensure coverage of compliance needs and operational constraints.

Frequently asked questions about Security Penetration Test Offers

Answers to common questions about authorization, signatures, scope disputes, and recordkeeping for penetration test engagements.


Need help? Contact support

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