Barracuda’s November 13, 2026 update advises directly notified customers to revoke and recreate affected integration credentials and review connected-system activity logs from November 1, 2026 onward. Barracuda says organizations that did not receive a notification need take no action under this advisory. Verify any apparent notice through your usual Barracuda contact or support channel.

The advisory applies only to organizations using an API integration for Barracuda Managed XDR Cloud or Monitored Endpoint. Barracuda reported unauthorized activity in its internal cloud environment and said it found no direct evidence that customer integration credentials were viewed or accessed.

Start with one affected integration

Use the integration-specific steps Barracuda provided for your affected connector. The steps and their order can vary by integration.

  • Match the affected integration to the verified notice and identify its authorized owner.
  • Follow the vendor’s instructions for replacing and revoking credentials for that integration.
  • After the change, use approved administrative records to check that the old credential was revoked.

Validate fresh collection after the cutover

After the authorized change, verify that a new benign event from the source arrives in XDR. Check the source identity and the event timestamp, then compare the arrival time in XDR to confirm the integration is collecting again. A green connection indicator, or the presence of only old events, does not prove fresh collection.

Record only non-secret evidence: the integration name, owner, source event time, arrival time, and whether revocation of the old credential is verified through approved administrative records. If fresh collection is missing, mark the result as incomplete and escalate through your own response team or official support rather than putting the old credential back into use.

For example, a test event generated before the change shows nothing about the new connection, even if it appears in XDR later. Look for an event generated after cutover from the same source and confirm that XDR received it.

Review activity from November 1 without overclaiming

Separately review connected-system activity from November 1 onward, as directed by the advisory. Keep in mind that validating collection does not prove there was no security exposure. Collection success and security investigation are related, but they are not the same conclusion.

Official references

Barracuda Trust Center: Barracuda XDR integration credentials

Barracuda Documentation: Barracuda XDR Integration Credentials

Barracuda Blog: Anatomy of a machine-speed intrusion

Illustration of two server panels connected by a blue shield, with a red alert icon below.
Illustration of two server panels connected by a blue shield, with a red alert icon below.