Q37
Do you have a current SOC 2 Type II report?
SOC 2 Type II: claimed_with_trust_page
Before you share customer data with Zendesk, your compliance team needs documented proof they can be trusted. ThirdProof investigated Zendesk across 27 intelligence sources — here's what we found.
⚠ FedRAMP Status: Not found in the FedRAMP Marketplace. Vendors handling government data or CUI must be FedRAMP authorized.
25 sources queried. 93% confidence. Every Zendesk investigation produces both a risk report and an auto-filled security questionnaire — no vendor follow-up required.
Get Zendesk's Full Report Free →Security Questionnaire — Auto-Filled
Auto-filled from public evidence • 34% complete
Q37
SOC 2 Type II: claimed_with_trust_page
Q38
ISO 27001 claim found on trust page (Vendor attested)
Q41
FedRAMP authorized: Product: Zendesk Customer Support and Help Desk Platform; Provider: Zendesk; Status: Compliant; Impact Level: LI-SaaS; Authorization Date: 2022-06-10T04:00:00.000Z
Q40
HIPAA compliance / BAA claim found on trust page (Vendor attested)
Q42
Zendesk provides a Data Processing Agreement at zendesk.com/company/data-processing-agreement/ with GDPR compliance commitments and contractual provisions for EU data protection law.
+ 5 more compliance questions answered in the full report
Every investigation produces a full PDF report plus the complete 133-question questionnaire, mapped to SOC 2, HIPAA, PCI DSS, SIG, and more.
Get Zendesk's Full Report Free →Verified against FedRAMP Marketplace API as of March 2026
Organizations with federal compliance requirements should verify this directly at marketplace.fedramp.gov.
Zendesk is not listed on the FedRAMP Marketplace.
Moderate Risk
Vendor Risk Assessment
Based on data availability and source coverage
25
Sources Queried
23
Sources With Data
April 4, 2026
Last Assessed
AI-generated analysis for Zendesk
Zendesk (zendesk.com) is a well-established SaaS customer support platform serving 200,000+ companies worldwide, assessed here at Tier 3 (Moderate Risk) with a 93% confidence score, reflecting a strong compliance posture offset by a recurring pattern of security incidents and an unresolved concern regarding AI training data transparency. Zendesk presents several meaningful positive signals that compliance teams should document:
requiring attention include a documented pattern of security incidents: a 2023 employee phishing attack that led to a breach, a subsequent potential data breach, and a more recent (April 2026) incident in which support tickets were stolen from the Zendesk platform, resulting in a downstream data breach at a customer (Hims & Hers). Additionally, an October 2025 Krebs on Security report highlighted an email-bombing vulnerability related to lax authentication in Zendesk. The vendor's AI training data commitment is described as unclear in the policy text despite adjacent language suggesting customer data is not used for LLM training — this ambiguity warrants direct clarification. Thirteen open ports were detected on Zendesk's infrastructure, which sits at the upper end of typical SaaS exposure. Subprocessor data could not be automatically parsed from the vendor's published page, requiring manual review. The TLS certificate for zendesk.com expires in approximately 56 days and should be monitored for timely renewal. On balance, Zendesk is a mature, heavily certified platform with a credible compliance program, but the recurring security incident history — particularly the platform-level support ticket breach in 2026 — elevates risk for buyers processing sensitive customer data. A conditional approval is warranted, subject to obtaining current audit reports and direct confirmation of AI data handling commitments.
Independence Statement
All evidence in this report was independently sourced from external data providers, public registries, and open-source intelligence without vendor participation or notification.
4 findings identified for Zendesk
Article from Bleepingcomputer: "Hims & Hers warns of data breach after Zendesk support ticket breach"
zendesk.com is missing 3 recommended security headers: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options.
2 article(s) mention "Zendesk" with risk keywords, severity reduced due to article age: "Zendesk Hacked After Employees Fall for Phishing Attack" (SecurityWeek) https://news.google.com/rss/articles/CBMijgFBVV95cUxQU3VlWm5PaHM2UDFLSGdSVWVFSXlrOEp6Y281eTNuU01iMjZ6TlRCQUVENlpQdjdQUm1Ga2Z1VW1zWUd2RlJsaVJrX05oaXJTeHBzcUFaT1U1X0FFWXZWSVNrVmxSLW1xQTk1VExSVi1EWTRhYkxBVzN2NDlRNFE3eVYtSU03VVFRaEZpcHVB0gGTAUFVX3lxTE5YUVpraGR6UzBYenZLcHF5RXVKRHZhYVNteG55VDd1TUIxc0o3cktMNkhFSHRJdFJQTVVnRldVNndMXzlta1JhSkxJR19xajRPRmZhYS1ETDRvNGhOcklRSHpuTEUyOUE2QXQ1SFdMdXdlSUU2YVRGeVRldXdIT0l3WGpZRndkV1ltMkQ5N3c2QXhHcw?oc=5; "Zendesk Experiences Potential Data Breach" (JD Supra) https://news.google.com/rss/articles/CBMigwFBVV95cUxNTmhXaWo3d1k0MWMxY185ZldGZkl6UXZrSFlTNW85WUxkQ19qUHdzQmxFbDVCeTZpX0hyTGlBWVBsaHJURmVtNW1ocndMWEY3MFBzSkRyaVBXeVh4S1VHX2M4T2k0RmQzN0NOemZDV0ZPOFU1RlBrUllMZ29LdFBUbzFCQQ?oc=5
zendesk.com has an AI-related policy page but does not clearly state whether customer data is used for AI model training.
32 positive signals verified
Legal Entity Actively Registered
Business Registration →No Sanctions Matches Found
Sanctions & Watchlist Screening →No Adverse Media Found
Adverse Media Scan →Firmographic Data Available
Company Intelligence →Valid SSL Certificate
Domain Analysis →13 Open Ports Detected
Infrastructure Exposure →Established Domain (20+ years)
Domain Registration →Clean domain reputation
Threat Intelligence →Tech Community Discussion: security
Tech Community Sentiment →HTTP Security Grade: B
HTTP Security Scan →Certificate Data from TLS Handshake
Certificate Transparency →Web Presence: 1 Years
Web Archive History →Threat Intelligence (OTX) Unavailable
Threat Intelligence (OTX) →Low Abuse Score: 0% (1 reports)
IP Reputation →Clean Safe Browsing Status
Malware & Phishing Check →Clean Website Security Scan
Website Security Scan →FedRAMP Authorization Independently Verified
Trust & Compliance Page Scan →Certification Claimed: SOC 2
Trust & Compliance Page Scan →Certification Claimed: ISO 27001
Trust & Compliance Page Scan →Certification Claimed: ISO 27017
Trust & Compliance Page Scan →Certification Claimed: ISO 27018
Trust & Compliance Page Scan →Certification Claimed: PCI DSS
Trust & Compliance Page Scan →Certification Claimed: HIPAA
Trust & Compliance Page Scan →Certification Claimed: CSA STAR
Trust & Compliance Page Scan →Certification Claimed: Cyber Essentials
Trust & Compliance Page Scan →Subprocessor Page Found, No Entries Parsed
Supply Chain & Subprocessor Discovery →Not Found as FDIC-Insured Institution
FDIC Institution Check →No SEC Enforcement Filings Found
SEC Filing Search →FedRAMP Authorization Confirmed via Registry
Certification Registry Verification →SOC 2 Compliance Claimed on Trust Page
Certification Registry Verification →Zero Data Retention for AI Processing
AI Data Usage Policy →AI Governance Standards Referenced
AI Data Usage Policy →Steps to address findings for Zendesk
Request Zendesk's current SOC 2 Type II report and a bridge letter confirming audit coverage through the present date — contact Zendesk's security team via https://zendesk.com/trust-center or submit a request through your account manager. Confirm the audit period post-dates the January 2023 phishing incident remediation.
Request a post-incident security advisory from Zendesk addressing the April 2026 support ticket exfiltration incident (reported by BleepingComputer). Ask specifically: what access control failures were exploited, what remediation steps were taken, and whether your tenant's data was potentially in scope.
Manually review Zendesk's subprocessor list at https://trust.zendesk.com/subprocessors and identify all third parties with access to your customer support data. Retain a dated export in your vendor risk register and confirm each subprocessor is covered under Zendesk's DPA.
Obtain written clarification from Zendesk's security or legal team confirming whether customer data is used for AI model training under your contracted product tier. Reference the AI data use policy at https://support.zendesk.com/hc/en-us/articles/5729714731290-Zendesk-AI-Data-Use-Information and ask for DPA-level contractual confirmation of any no-training commitments.
Download Zendesk's ISO 27001:2022 certificate directly from their trust page (https://zendesk.com/trust-center) and record the certificate number, issuing body, and expiry date in your vendor risk register. This provides vendor-attested documentation even without independent registry verification.
Set a calendar reminder to re-verify the zendesk.com TLS certificate expiry (currently May 31, 2026) within 30 days. If still unrenewal after 45 days, escalate to your Zendesk contact. This is a low-effort check that prevents unexpected disruption.
Review Zendesk's DPA and BAA (if applicable to your use case) to confirm contractual coverage for the high-data-access classification assigned in this assessment. Zendesk's DPA should be available at https://zendesk.com/trust-center.
25 sources in this assessment
Some data sources may have had limited availability during this assessment. This does not reflect negatively on the vendor.
Are you Zendesk? Claim this profile to complete your security record. Buyers are reviewing this profile now.
Claim this profile →Is Zendesk on any OFAC, EU, or UN sanctions list? Are any officers or affiliates flagged?
What is Zendesk's security posture? Threat intelligence scanning, known vulnerabilities, and security header analysis.
Is Zendesk a legitimately registered business entity? Corporate status, jurisdiction, and officer verification.
Has Zendesk appeared in negative news coverage? Data breaches, lawsuits, regulatory actions, and complaints.
Is Zendesk's website secure? TLS configuration, DNS hygiene, security headers, and domain age analysis.
What are Zendesk's firmographics? Employee count, industry classification, technology stack, and corporate structure.
Does Zendesk claim SOC 2, ISO 27001, HITRUST, or FedRAMP? ThirdProof scans trust pages for certification claims and cross-references the FedRAMP public registry for independent verification.
Who does Zendesk depend on? ThirdProof discovers subprocessors from vendor-published pages and runs sanctions screening and safe browsing checks against each one.
Has Zendesk appeared in SEC enforcement filings? Is it associated with any FDIC bank failures? ThirdProof searches regulatory databases with entity verification to confirm attribution.
Full methodology, rule engine, and AI disclosure: /methodology
Seeing this in an audit? ThirdProof lets you investigate Zendesk and every other vendor in your stack — average report time: 7 minutes. Get Zendesk's Full Report Free →
SOC 2 CC9.2, HIPAA, PCI-DSS, and CMMC all require documented vendor due diligence — not just knowing the answer, but having audit-ready evidence you verified it. Most compliance teams can't produce that documentation on demand.
ThirdProof investigates Zendesk across 27 intelligence sources in an average of 7 minutes — sanctions screening, cyber posture, SOC 2 verification, FedRAMP status, and more. Every investigation produces two deliverables: an audit-ready risk report and an auto-filled security questionnaire your prospects and auditors expect to see.
Replaces $600–$900 in manual compliance consulting time per vendor assessed.