Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dropbox Sign fka HelloSign #179

Open
ramimac opened this issue May 1, 2024 · 0 comments
Open

Dropbox Sign fka HelloSign #179

ramimac opened this issue May 1, 2024 · 0 comments

Comments

@ramimac
Copy link
Owner

ramimac commented May 1, 2024

https://www.dropboxsign.com/blog/a-recent-security-incident-involving-dropbox-sign

When we became aware of this issue, we launched an investigation with industry-leading forensic investigators to understand what happened and mitigate risks to our users.

Based on our investigation, a third party gained access to a Dropbox Sign automated system configuration tool. The actor compromised a service account that was part of Sign’s back-end, which is a type of non-human account used to execute applications and run automated services. As such, this account had privileges to take a variety of actions within Sign’s production environment. The threat actor then used this access to the production environment to access our customer database.

In response, our security team reset users’ passwords, logged users out of any devices they had connected to Dropbox Sign, and is helping customers rotate all API keys and OAuth tokens. We reported this event to data protection regulators and law enforcement.

https://www.sec.gov/Archives/edgar/data/1467623/000146762324000024/dbx-20240429.htm

known AWS customer: https://aws.amazon.com/solutions/case-studies/dropbox-hellosign-security/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant