TL;DR: A System and Organization Controls (SOC) 2 Type 2 report shows that an independent audit firm tested a vendor’s security controls over months. Before you trust an e-signature provider, check the report’s scope, its dates and the controls that matter to you. See how we protect your documents.
Your e-signature platform holds signed contracts, personal details and payment data. A breach there exposes your customers, not just the vendor. That makes the signing vendor a critical supplier, and your security team will want proof.
A SOC 2 Type 2 report is the proof most teams ask for first. This guide explains what the report covers and what to check in it. It also covers how to store signed files for your own audit.
What is a SOC 2 Type 2 report?
A SOC 2 Type 2 report is an audit report on how a service company protects customer data. An independent certified public accountant (CPA) firm writes it after testing the company’s controls over a span of months.
The American Institute of Certified Public Accountants (AICPA) sets the rules the auditors follow. The report checks controls, which are the rules and tools a company uses to protect data. It does not rate products or features.
Think of a restaurant health check. One surprise visit shows the kitchen was clean that day. A year of visits shows the staff keep it clean every day.
What is the difference between a Type 1 and a Type 2 report?
A Type 1 report checks whether controls are designed well at one point in time. A Type 2 report checks whether they are designed well and work as intended over a set period.
A Type 1 report can be a fair start for a young vendor. Most buyers still ask for Type 2, since it shows the controls held up in daily use. Our own SOC 2 Type 2 audit covers 12 months.
What do the five Trust Services Criteria mean for e-signatures?
The AICPA Trust Services Criteria are the five areas a SOC 2 Type 2 audit can cover. Each one maps to a real risk in a signing workflow.
- Security: access control and encryption protect contracts and attachments.
- Availability: uptime and disaster recovery keep signing open when deadlines hit.
- Processing integrity: each signing step runs in the right order without errors.
- Confidentiality: private business terms stay limited to the people who need them.
- Privacy: personal data is collected, used, kept and deleted under the vendor’s privacy policy.
A vendor can pick which areas go into its audit. Check that the report covers the areas your data needs.
What compliance certifications should enterprise e-signature platforms support?
Ask for a SOC 2 Type 2 report first, then for the rules that match your data. The right set depends on where your signers live and what your documents hold.
- The General Data Protection Regulation (GDPR) when you handle personal data from the EU.
- Health Insurance Portability and Accountability Act (HIPAA) support with a business associate agreement (BAA) for health data.
- The Electronic Signatures in Global and National Commerce (ESIGN) Act for US signatures.
- The EU electronic identification and trust services (eIDAS) rules for signatures in the EU.
Ask each vendor which of these apply to the exact product you will use. A badge on a home page does not tell you that.
What should you check in a vendor’s SOC 2 Type 2 report?
Read three things: the scope, the dates and the controls that match your needs. Each one can change how much the report tells you.
Does the scope cover the product you will use?
The system description should name the e-signature product itself, not just the parent company. A very narrow scope may skip systems you will rely on.
A broad or vague scope is also a warning sign. The parts you use may never have been tested.
Is the report recent, and how long was the audit period?
Look at the report date and the period it covers. A report from more than a year ago tells you less about today.
Ask when the next report is due, and read it once it arrives. A 12-month period also says more than a 3-month one, since the controls had to work for longer.
Do the controls match your own needs?
Look for controls on incident response and breach notice that fit your rules. For signing, also look at controls on data integrity, encryption and audit trails.
Many reports also list controls you must run on your side, such as user access reviews. Plan for those, since the vendor’s audit does not cover them.
How should you store e-signed PDFs for a SOC 2 Type 2 audit?
Keep each signed PDF with its audit trail, under access rules you can show an auditor. Then write down how long you keep files and who may delete them.
- Store the signed PDF and its audit trail together, so each record proves who signed and when.
- Limit access by role, and remove access when people change jobs.
- Keep files encrypted at rest and in transit, in the platform or in your own storage.
- Set a retention period for each document type, and delete files on schedule.
- Log every download and deletion, so you can show the auditor what happened.
Our guide to e-signature retention and secure record keeping goes further on retention periods. The audit trail page shows what each log records.
How do you find SOC 2 Type II compliant e-signature solutions for financial services?
Ask each vendor for its SOC 2 Type II report and check it against your own risk rules. Banks and lenders should also ask how signers prove who they are, where data is stored and how long records are kept.
Financial teams sign account openings, loan files and statements that hold account details. Our page on electronic signatures for banking shows those workflows. Share the vendor’s report with your risk team early, since reviews can take weeks.
What should HR teams look for?
HR document signing with SOC 2 Type 2 security protects offer letters, tax forms and ID copies. Check that only HR staff can see those files and that each signature has an audit trail.
See how teams handle this on our page for HR teams.
How does BoldSign protect your documents?
Our product went through a SOC 2 Type 2 audit by an independent CPA firm, covering all five Trust Services Criteria. The audit covers 12 months and repeats every year.
Here is what our security policy lists beyond the audit:
- We encrypt data twice, at the service and infrastructure levels, with the 256-bit Advanced Encryption Standard (AES).
- Every document has an audit log with user details, internet protocol (IP) address and time stamp.
- We host data on Google Cloud Platform and Microsoft Azure in the US East, EU, Canada and Australia.
- Our primary database keeps hourly backups for the last 30 days.
You can also give users roles with custom permissions. BoldSign follows GDPR, and its signatures meet the ESIGN Act and eIDAS.
Which BoldSign plan do you need, and what does it cost?
Admins on any paid plan can read our SOC 2 Type 2 report in the Compliance section of account settings. If you are not a customer yet, ask for it through our Security and Legal Compliance Request form.
Our Essential plan is free. The Growth plan costs $5 per user a month, and the Business plan costs $15 per user a month.
The Premium plan costs $99 a month for unlimited users. All prices are in USD and billed yearly.
Choose the Business plan or higher when you need HIPAA support or single sign-on (SSO). You can try the product first with a 30-day free trial. Compare all features on our pricing page.
How do you start with a SOC 2 Type 2 eSignature platform?
Request the report, read the scope and dates, then try the product with a real document. These links help with each step.
- Start your 30-day free trial and send a test document.
- Book a demo to walk through our security setup with our team.
- Browse the BoldSign help center or ask our support team.
Frequently asked questions
What security certifications should an electronic signature vendor have?
Start with a current SOC 2 Type 2 report from an independent audit firm. Then match the rest to your data: GDPR for EU personal data, HIPAA support for health data, and e-signature laws such as ESIGN and eIDAS.
Is a SOC 2 Type 2 certified e-sign tool really certified?
The word certified is common shorthand. What the vendor holds is a SOC 2 Type 2 report from an independent CPA firm, so ask to read the report itself.
Which digital signature services meet SOC 2 Type 2 compliance requirements?
Any service with a recent SOC 2 Type 2 report that covers the signing product you plan to use. Ask each vendor for its report and check the scope and the audit period.
How long does a SOC 2 Type 2 audit period last?
It covers a span of months, not a single day. Our own SOC 2 Type 2 audit covers 12 months, and an independent firm repeats it every year.
Is a Type 1 report enough for an e-signature vendor?
It can be a starting point for a young vendor. A Type 1 report only checks control design at one moment, so most buyers ask for Type 2 before they sign.
Are documents signed on a SOC 2 Type 2 platform legally binding?
Yes, when the signing meets the e-signature law that applies, such as ESIGN in the US or eIDAS in the EU. The audit report covers the vendor's security controls, not the legal effect of a signature.
How do I get the BoldSign SOC 2 Type 2 report?
Admins on a paid plan open it in the Compliance section of account settings. Anyone else can ask for it through our Security and Legal Compliance Request form, which our legal team reviews.
Does a SOC 2 Type 2 report replace a vendor security questionnaire?
Usually it shortens the questionnaire rather than replacing it. Most teams read the report first, then send a short list of questions for the gaps.