From 8e5fccae2f3cf7a6cd8551b122e2a5e08a575c10 Mon Sep 17 00:00:00 2001
From: seaxwi <71350948+seaxwi@users.noreply.github.com>
Date: Thu, 27 Feb 2025 15:00:31 +0100
Subject: [PATCH] Update
 ASEC-25-001-Security-incident-on-Arduino-infrastructure.md

---
 .../ASEC-25-001-Security-incident-on-Arduino-infrastructure.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/About Arduino/Arduino Security Bulletins/ASEC-25-001-Security-incident-on-Arduino-infrastructure.md b/content/About Arduino/Arduino Security Bulletins/ASEC-25-001-Security-incident-on-Arduino-infrastructure.md
index 07ee0e88..ee148389 100644
--- a/content/About Arduino/Arduino Security Bulletins/ASEC-25-001-Security-incident-on-Arduino-infrastructure.md	
+++ b/content/About Arduino/Arduino Security Bulletins/ASEC-25-001-Security-incident-on-Arduino-infrastructure.md	
@@ -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?