Security alertsFri, 13 Nov 2026
Barracuda Managed XDR incident: notified customers should replace integration credentials
Barracuda confirmed an attacker reached a system that stores credentials for XDR integrations. It found no direct evidence that customer credentials were accessed. Customers notified by Barracuda should revoke and recreate the credentials and review connected systems.
Article
From 1 to 2 November 2026, an attacker gained access to part of Barracuda’s internal cloud environment through a third party that had been issued a cloud access key. Barracuda says the attacker found and reused credentials to move within that environment and reached a system that stores customer integration credentials. The investigation has found no direct evidence that the attacker viewed or accessed those customer credentials.
Barracuda’s advisory applies to API integrations for Managed XDR Cloud or Monitored Endpoint. It has directly notified customers with potentially affected credentials. Those customers should revoke and recreate the credentials and review activity in connected systems from 1 November onward. Barracuda says customers who received no notice do not need to act on this advisory.
A monitoring integration may connect to Microsoft 365, Google Workspace, endpoint security tools or other services. If a credential is misused, what it can reach depends on the connector’s actual permissions. Revoking it can interrupt telemetry until the replacement is installed and collection is verified.
- 01
Enter through third-party cloud access
The attacker gained entry through a third party issued a cloud access key.
- 02
Move within the vendor environment
Barracuda observed the attacker searching for and reusing credentials to reach other systems.
- 03
Reach the integration credential store
The attacker had access to the system between 1 and 2 November. Barracuda has found no direct evidence of customer credentials being viewed or accessed.
- 04
Assess potential customer impact
A misused integration identity could reach customer systems only within its granted permissions. This is a possible consequence of exposure.
What Barracuda is changing
Barracuda says it cut off known attacker access and rotated credentials in the affected environment. It is moving integration secrets to storage with a separate security boundary, expanding audit and data access logs, tightening vendor credential lifetimes and restricting which Kubernetes workloads can read secrets. Barracuda has also deployed runtime detection in its clusters and continues to investigate.
- 01
Confirm the notification and identify the integrations
Check the vendor notice with your Barracuda contact. Map the API integrations named in it to their customer tenants, service principals, credential types and owners. Include integrations managed by a service provider.
View guidanceResources: 1
Response guidance
Confirm the notification and identify the integrations
Check the vendor notice with your Barracuda contact. Map the API integrations named in it to their customer tenants, service principals, credential types and owners. Include integrations managed by a service provider.
- 02
Revoke and recreate affected integration credentials
Follow the vendor’s instructions for each connector. Coordinate the cutover between the XDR and customer-platform owners. Create replacement credentials with the minimum permissions required, update the connector, revoke the old credentials and confirm they are disabled. Follow your incident response process for immediate revocation if you see evidence of misuse.
See what to doResources: 1
TWISA member solutions
Revoke and recreate affected integration credentials
Review nonhuman identities and API permissions, record who owns each credential, and track creation, expiration and revocation. Check coverage for the credential types and customer platforms in use.
- 03
Review customer-side activity since 1 November
Preserve API audit logs, service principal activity, access events and relevant endpoint or cloud audit records. Check for unusual sources, access outside the connector’s baseline, permission changes and unexpected data access. Correlate Barracuda’s indicators with tenant, actor, time and action. An indicator match alone does not establish malicious activity.
See what to doResources: 2
TWISA member solutions
Review customer-side activity since 1 November
Use monitoring and incident response services to correlate customer-side records and investigate activity beyond normal data collection.
- 04
Verify collection and follow through on findings
Confirm each connector is collecting the expected telemetry again and record any collection gap. If you find signs of misuse, preserve evidence, contain the affected tenant or accounts as appropriate and investigate what the integration identity could reach. Escalate through your incident response process and coordinate with Barracuda.
See what to doResources: 2
TWISA member solutions
Verify collection and follow through on findings
Incident response services can help scope affected accounts and data. Monitoring services can verify that collection is back to normal and watch for attempted reuse of revoked credentials.
Map connector owners, customer tenants, API scopes, credential types, rotation dates and data collection baselines.
Allow authorized traffic and apply controls at each layer.
- 01
Provider connection
Barracuda Managed XDR API connector
Inventory and coordinateTie each connector to its tenant and owner.
- 02
Customer identity boundary
Service principal, API key or client secret
Constrain accessUse separate credentials and grant only required permissions.
- 03
Connected services
Cloud, collaboration and endpoint platforms
Audit useRecord access and verify that expected telemetry resumes.
Feed logs and traffic data from each layer into monitoring and response.
- Correlate activityCompare audit events across the provider and customer platforms.
- Contain and verify recoveryEscalate suspicious activity and confirm the previous credential is disabled.
Validate the cutover
With authorization, confirm the replacement connector can perform its intended API calls and collect its expected events. Review scope and service principal assignments, and verify that the previous credential is revoked through the issuing platform. Investigate unexpected access separately from a missed collection window.
TWISA member solutions
Supporting: Revoke and recreate affected integration credentials
Review nonhuman identities and API permissions, record who owns each credential, and track creation, expiration and revocation. Check coverage for the credential types and customer platforms in use.
Supporting: Review customer-side activity since 1 November
Use monitoring and incident response services to correlate customer-side records and investigate activity beyond normal data collection.
Supporting: Verify collection and follow through on findings
Incident response services can help scope affected accounts and data. Monitoring services can verify that collection is back to normal and watch for attempted reuse of revoked credentials.
Official sources
For further product and service details, please contact the relevant TWISA members.
Advisory updated: 2026/11/13. Check the vendor’s latest information for product support and fixes.