Skip to content

Update ASEC-25-001-Security-incident-on-Arduino-infrastructure.md #479

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 27, 2025
Merged

Update ASEC-25-001-Security-incident-on-Arduino-infrastructure.md #479

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...o Security Bulletins/ASEC-25-001-Security-incident-on-Arduino-infrastructure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ As announced in a previous bulletin [ASEC-24-002](https://support.arduino.cc/hc/
As a consequence, we took the following actions:

* We immediately responded to the incident and identified the root cause of the attack, which was related to an API key from one of the SaaS providers involved in providing Arduino services. Furthermore, we conducted thorough internal security analysis and forensic investigations to ensure that no unmanaged risks remained from the leaked data.
* We informed the GDPR authority about the exfiltrated user data.
* We informed the Data Protection Authority about the exfiltrated user data.
* We informed via email all users affected by the issue related to Arduino Cloud IoT devices. An update was provided, instructing them to regenerate device credentials for Arduino Cloud.

## What happens now?
Expand Down