Home / Security updates / HelloSign/Dropbox Sign Incident
HelloSign/Dropbox Sign Incident
Security updates detail rendered from /security-updates/upd_4d39e9b9dfe504a3.
Overview
| ID | upd_4d39e9b9dfe504a3 |
| Collection | Security Updates |
| Provider | SafeBase |
| Company | Ironclad |
| URL | - |
| Counts | - |
| Updated | - |
Raw record
| Field | Value |
|---|---|
| id | upd_4d39e9b9dfe504a3 |
| providerId | safebase |
| organizationId | org_6b28e9b720761d3b |
| trustCenterId | tc_8c0d22d941b59e5c |
| title | HelloSign/Dropbox Sign Incident |
| message | Ironclad is investigating a security *[notification](https://sign.dropbox.com/blog/a-recent-security-incident-involving-dropbox-sign)* by one of our subprocessors, Dropbox. Dropbox features that were impacted were HelloSign/Dropbox Sign, which has resulted in the exposure of emails, usernames, phone numbers and hashed passwords for customers using their own HelloSign/Dropbox Sign accounts. Ironclad’s Legacy Signature solution leveraged HelloSign/Dropbox Sign, but the customer impact is limited to the exposure of signature request recipient data (e.g., names and emails). At this time, Dropbox has said that it has no reason to believe the signed documents themselves were exposed. Safeguarding the security and privacy of our customer's data is our top priority, and we are working diligently to assess the extent of the impact. Ironclad has already completed the immediate recommended actions posted by Dropbox to address any further concerns as of 5:45 pm PST on May 1st, 2024. We are |
| url | - |
| publishedAt | 2024-05-02 |
| source | {
"field": "statuspage/public/compliance-update",
"category": "subprocessors"
} |
| company | {
"id": "org_6b28e9b720761d3b",
"name": "Ironclad",
"domains": [
"security.ironcladapp.com",
"ironcladhq.com"
]
} |
| trust_center | {
"id": "tc_8c0d22d941b59e5c",
"name": "Ironclad",
"url": "https://security.ironcladapp.com",
"host": "security.ironcladapp.com"
} |
| provider | {
"id": "safebase",
"name": "SafeBase"
} |
| links | {
"self": "/v1/security-updates/upd_4d39e9b9dfe504a3",
"company": "/v1/companies/org_6b28e9b720761d3b",
"trust_center": "/v1/trust-centers/tc_8c0d22d941b59e5c",
"provider": "/v1/providers/safebase"
} |
Get this page with API
Rendered from the bluedoor Trust Centers API. Reproduce it:
GET https://api.bluedoor.sh/trust-centers/v1/security-updates/upd_4d39e9b9dfe504a3JSON