Explainers
What Is Third-Party Risk Management (TPRM)? A Practical Guide
Solomon Amos · 2 Nov 2026 · 10 min read
Jitterbit
SOC 2 evidence
Ignite business productivity with data orchestration, iPaaS, workflow automation, and low-code app development solutions—all on one unified
Vendor-statedJitterbit and SOC 2
Jitterbit states it holds a SOC 2 Type II report. CertReports captured this on 2 Nov 2026 from its trust centre (Drata); it is a vendor statement, not an independent confirmation.
Evidence
Vendor-statedVendor states SOC 2 Type 2 on its trust centre
as of 2 Nov 2026 · confidence 80%- Kind
- Type II
| Source | Captured | Quote | Links |
|---|---|---|---|
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 1 Nov 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 31 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 29 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 27 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 25 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 23 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 21 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 19 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 17 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 15 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 13 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 11 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 9 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 7 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 5 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 3 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 1 Oct 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 29 Sep 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 27 Sep 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 25 Sep 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 21 Sep 2026 | SOC 2 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 18 Sep 2026 | SOC 2 Type 2 |
Vendor-statedVendor states SOC 1 Type 2 on its trust centre
as of 2 Nov 2026 · confidence 80%- Kind
- Type II
| Source | Captured | Quote | Links |
|---|---|---|---|
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 1 Nov 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 31 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 29 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 27 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 25 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 23 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 21 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 19 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 17 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 15 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 13 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 11 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 9 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 7 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 5 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 3 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 1 Oct 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 29 Sep 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 27 Sep 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 25 Sep 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 21 Sep 2026 | SOC 1 Type 2 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 18 Sep 2026 | SOC 1 Type 2 |
Vendor-statedVendor states SOC 3 on its trust centre
as of 2 Nov 2026 · confidence 80%| Source | Captured | Quote | Links |
|---|---|---|---|
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 1 Nov 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 31 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 29 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 27 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 25 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 23 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 21 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 19 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 17 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 15 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 13 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 11 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 9 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 7 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 5 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 3 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 1 Oct 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 29 Sep 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 27 Sep 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 25 Sep 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 21 Sep 2026 | SOC 3 | |
Jitterbit trust centre (Drata) Vendor trust centre · HTTP 200 | 18 Sep 2026 | SOC 3 |
What is not public
- The report period is not public, so CertReports cannot say whether the Jitterbit SOC 2 report covers the last 12 months.
- The audit firm is not stated in any public source CertReports has captured.
- Trust services criteria in scope, carve-outs and bridge-letter status are only in the restricted-use report, which CertReports never hosts.
What SOC 2 means, and what it does not
SOC 2 reports are restricted-use and are never "certifications". A Type II report covers a period; freshness is the period end plus a bridge letter of at most three months. "SOC 2 ready" and "in progress" are not reports. No public SOC 2 registry exists; the strongest registry-grade signal is a CSA STAR Level 2 attestation, then a public SOC 3.
Read the SOC 2 guide and browse all vendors with evidenceQuestions buyers ask
Is Jitterbit SOC 2 certified?
No organisation is "SOC 2 certified": SOC 2 is an attestation report issued by a CPA firm, not a certification. Jitterbit states it holds a SOC 2 Type II report as of 2 Nov 2026.
How do I get the Jitterbit SOC 2 report?
SOC 2 reports are restricted-use documents shared under NDA. Request it through the Jitterbit trust centre or security page; CertReports links to it and never hosts the report.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Change history
- 18 Sep 2026SOC 2 evidence addedA SOC 2 row entered the index with state Vendor-stated.
Alternatives with SOC 2 evidence
Similar vendors (shared product tags or the No-code and automation category) whose SOC 2 row is verified or vendor-stated, ranked by similarity.
n8n
No-code and automation
n8n is a workflow automation platform and the Berlin company, n8n GmbH, that develops it
Celigo
No-code and automation
Build, run, and govern automation on one
Halo
No-code and automation
Streamline your processes with Halo's workflow
Quickbase
No-code and automation
Quickbase is a cloud-based platform that allows businesses to create custom applications and workflows to streamline their processes and
InRule Technology
No-code and automation
InRule brings together business rules, process automation, and AI to design, test, and deploy governed decisions that meet regulations
Katalon
No-code and automation
Katalon True Platform unifies test management, automation, execution and production
TeamDynamix
No-code and automation
TeamDynamix is a no-code AI ITSM
Applitools
No-code and automation
Applitools is an AI-powered end-to-end testing platform that combines our proven Visual AI with the latest GenAI and no-code approaches to