Use this e-signature vendor security questionnaire to compare platforms, document procurement decisions, and identify control gaps before approving a tool for business document signing. It covers encryption, authentication, identity verification, access control, audit trails, integrations, privacy, incident response, retention, and contract terms, with a scoring method that can be reused during renewals and annual reviews.
Overview
An e-signature platform may handle contracts, employee records, customer forms, financial documents, and other files that require careful protection. A polished user interface is not enough for approval. Procurement and IT teams should understand how the vendor protects documents, verifies signers, limits administrative access, records activity, responds to incidents, and supports the organization’s retention and compliance requirements.
This questionnaire is designed for an initial electronic signature vendor risk assessment, but it also works for renewals, new use cases, acquisitions, system migrations, and changes to a vendor’s security documentation. Ask the vendor to answer each question in writing and identify the supporting evidence, such as a current security report, penetration-test summary, certificate, privacy notice, data-processing agreement, architecture diagram, or product documentation.
Do not treat a certification or compliance label as a complete security review. Confirm what the stated control covers, which services are included, where data is processed, and whether the control applies to the features your organization will use. Legal teams should separately assess whether the planned workflow supports applicable electronic-signature requirements, including requirements related to consent, signer intent, record integrity, and retention.
What to track
1. Encryption and document protection
- Is document content encrypted in transit and at rest?
- Which encryption protocols and key-management practices are used, and are they documented for the relevant service?
- Are completed documents tamper evident, and how can a recipient verify that a signed file has not changed?
- Are temporary files, previews, thumbnails, backups, and cached copies included in the vendor’s protection and deletion controls?
- Can the customer manage encryption keys, or is key management fully controlled by the vendor?
Ask for a clear data-flow description rather than a broad statement that the platform is “secure.” If documents are scanned before signing, confirm where OCR output, page images, and metadata are stored. A secure document scanning workflow should protect the original files, extracted text, and any temporary processing copies.
2. Authentication and identity verification
- Does the service support single sign-on, multi-factor authentication, and centralized user lifecycle management?
- Can administrators enforce strong authentication for senders, approvers, and other privileged users?
- What signer-verification options are available, such as email verification, access codes, knowledge-based checks, identity documents, or stronger identity verification?
- Can the organization select different verification methods by document type, risk level, geography, or recipient?
- Are failed verification attempts, changes to signer details, and authentication events recorded in the audit log?
Verification should match the risk of the transaction. An internal policy document may need a different control than a high-value contract or a form containing sensitive personal information. Ask whether stronger verification is included in the standard workflow or requires a separate product, configuration, or service.
3. Access controls and administration
- Does the platform provide role-based access controls and separate roles for sending, viewing, signing, reporting, and administration?
- Can administrators restrict access by team, workspace, department, document type, or geographic region?
- Are privileged actions logged, including permission changes, exports, deletions, impersonation, and configuration updates?
- Can access be removed promptly when an employee leaves or changes roles?
- Does the vendor support approval rules for high-risk templates or unusual recipient changes?
Look for least-privilege controls that can be managed without creating a large number of shared accounts. Shared credentials make investigations and accountability more difficult, especially when a document workflow involves multiple senders or administrators.
4. Audit trails and evidence
- What events appear in the audit trail, and does the record include timestamps, actors, IP information, authentication events, recipient actions, and document status changes?
- Is the audit trail protected against alteration by ordinary users and administrators?
- Can logs and completed documents be exported in a usable format?
- Are exports available through an API, scheduled process, or security-information and event-management integration?
- How long are audit records retained, and can retention be configured to match organizational policy?
An audit trail should help an independent reviewer reconstruct what happened, when it happened, and which account performed each action. Confirm whether the audit record travels with the completed PDF or must be stored separately. For a broader retention plan, see Document Retention Policy for Signed PDFs.
5. Privacy, subprocessors, and data location
- What categories of personal and confidential information does the vendor process?
- Where are documents, metadata, backups, and audit logs stored and processed?
- Does the vendor offer data-location options that meet the organization’s requirements?
- Which subprocessors handle hosting, communications, identity verification, analytics, support, or document processing?
- How are subprocessor changes announced, reviewed, and challenged?
- Does the contract define the vendor’s permitted use of customer content and prohibit unrelated secondary use?
Review the privacy notice, data-processing terms, subprocessor list, and product-specific terms together. A general corporate privacy statement may not answer where a particular e-signature service stores completed files or how long support systems retain attachments.
6. Incidents, resilience, and recovery
- How does the vendor detect, classify, investigate, and notify customers about security incidents?
- What customer contacts and escalation channels are available during an incident?
- What backup, disaster-recovery, and service-continuity controls protect documents and audit records?
- Can customers retrieve documents and logs if the service is unavailable or the contract ends?
- What service-status, maintenance, and outage communications are provided?
Ask for the contractual notification window and the information the vendor commits to provide. Avoid relying only on a general promise to notify customers promptly; the agreement should describe responsibilities, contacts, cooperation, and evidence preservation.
7. Integrations and workflow security
- Does the API support scoped credentials, token rotation, rate limits, webhook signing, and replay protection?
- Can integrations limit which templates, folders, users, and documents an application can access?
- Are webhook events authenticated and delivered with enough information to verify document state?
- Can the platform integrate with identity providers, document management systems, ticketing tools, and retention systems without copying unnecessary data?
- Are failed, duplicated, or delayed events visible to administrators?
For API-based workflows, test authorization boundaries and failure handling before production use. The E-Signature API Integration Guide provides a useful companion checklist for secure requests, webhooks, and document completion.
8. Contract terms and exit controls
- Who owns documents, templates, signer data, and audit records?
- What happens to active envelopes, completed files, backups, and support records after termination?
- How can the organization export its content, metadata, and audit history?
- Are deletion timelines, deletion certificates, and legal holds addressed?
- Does the contract cover confidentiality, security obligations, subcontractors, incident cooperation, and audit rights?
Exit planning is part of vendor security. A platform may meet requirements during normal operations but create avoidable risk if the organization cannot retrieve signed files or prove that unnecessary copies were deleted.
Comparison by service model
| Service model | Typical review focus | Questions to prioritize |
|---|---|---|
| Hosted e-signature service | Vendor-operated storage, administration, availability, and user access | Where are files stored? How are tenants separated? What controls govern administrators, subprocessors, exports, and deletion? |
| API-based e-signature service | Application permissions, data flows, credentials, webhooks, and integration failures | Can tokens be scoped and rotated? Are callbacks signed? What data is returned, logged, or retained by each connected system? |
| Enterprise e-signature service | Advanced identity, policy, data residency, governance, and centralized administration | Which controls are included in the contracted edition? Can policies vary by business unit? Are audit exports and retention settings manageable at scale? |
Reusable scoring matrix
Score each control from 0 to 3: 0 means no answer or unacceptable gap; 1 means a partial answer or compensating control is required; 2 means the control is documented and appears suitable; 3 means the control is documented, evidenced, contractually supported, and tested where practical. Apply a separate criticality rating of low, medium, or high to encryption, identity, audit trails, data location, incident response, and exit controls.
Do not approve a vendor solely because its average score is high. A single unresolved high-criticality gap—such as no usable audit export, unclear ownership of customer content, or inadequate privileged access controls—may require remediation, a contract condition, a different workflow, or rejection. Record the owner, due date, evidence reviewed, and accepted risk for every open item.
Cadence and checkpoints
Use the questionnaire at three points. During initial procurement, request written answers and evidence before the final approval. During implementation, validate the controls in a test workspace: enable multi-factor authentication, review roles, complete a sample signing flow, export the audit trail, test an integration failure, and confirm the deletion and retention settings.
For an ongoing review, check high-impact items quarterly or on another risk-based cadence. Confirm the current subprocessor list, privacy terms, security documentation, data-location options, incident contacts, service status, audit-log export, and material product changes. At least annually, repeat the broader questionnaire and confirm that the deployed configuration still matches the approved use case.
Also trigger an unscheduled review when the vendor changes ownership, moves data locations, introduces a new identity-verification provider, changes contract terms, reports a significant incident, adds artificial-intelligence or automated document-processing features, or when your organization begins handling more sensitive documents.
How to interpret changes
A new feature is not automatically a security improvement. Determine whether it changes the data collected, the parties receiving it, the retention period, or the administrator permissions required. A new subprocessor may be acceptable, but it should prompt a review of its purpose, location, access, and contractual coverage.
A lower score is not always a reason to terminate a vendor. First classify the gap: configuration error, missing evidence, product limitation, contract weakness, or unacceptable risk. Some gaps can be addressed with stronger authentication, restricted templates, encrypted document sharing, shorter retention, or a separate approval step. Others require a documented exception or a replacement plan.
Pay particular attention to changes that affect evidence. If the platform changes its audit-log format, export method, timestamp behavior, or document-integrity mechanism, test whether existing records remain understandable and defensible. Preserve prior review results so changes can be compared over time rather than evaluated from memory.
When to revisit
Set the next review date before closing the current assessment. A practical baseline is a quarterly check of changing vendor information and an annual full review, adjusted for document sensitivity and regulatory or contractual requirements. Revisit immediately after a security incident, major platform change, acquisition, migration, or expansion into a new country or business process.
To make the process repeatable, save the questionnaire, scoring matrix, evidence links, approval decision, exceptions, and action owners in the organization’s vendor-management record. Assign one person to monitor vendor notices and another to validate technical controls. Before renewal, confirm that unresolved issues have owners and deadlines, export a current sample of completed documents and audit logs, and verify that the planned retention and deletion workflow still works.
Finally, connect the assessment to the real signing process. Review who can send a document, how recipients are verified, where completed PDFs are stored, who can retrieve them, and how unnecessary copies are securely deleted. This turns an e-signature vendor security questionnaire from a one-time procurement form into a practical control for secure document signing.