How to Connect to a Syslog

Last updated on 2022-07-07 16:26:32

Syslog Integration supports syslog version 3.

Syslog Integration enables you to export your event data to a syslog server or a security information and events management (SIEM) system. With Syslog Integration, you can store your information and use it for tracking, analysis, and troubleshooting.

Setting Up Syslog Integration

To configure Syslog Integration:

Open any firewall ports needed for communication with your syslog server/SIEM system.
Barracuda public IP addresses for Impersonation Protection are: 3.232.50.116 and 52.202.236.132
Click the Settings icon to access the administrative functions.
Select the Syslog Integration tab.
Enter the IP Address/Hostname and Port for your syslog server/SIEM system. The default port is 6514.
Click Save.
Click Test to ensure that Barracuda can connect with your syslog server/SIEM system.
- If the test is successful, your message log data begins transferring to your syslog server/SIEM system.
- If the test is not successful, check the IP Address/Hostname and Port information and reenter it if needed. Then perform the test again.

To deactivate the syslog server, switch off the Active toggle. Then click Save.

Notes:

You can only connect one syslog server/SIEM system at a time. You can delete an existing entry and replace it, but you cannot have multiple entries.
This feature is available only for Transmission Control Protocol (TCP) with Transport Layer Security (TLS).
If your syslog server/SIEM system stops responding, data will not spool until the communication is re-established.
After you enable or disable syslog integration, it can take up to 10 minutes for message transmission to either start or stop.

Data Sent

Barracuda sends the following objects to syslog:

Spear Phishing Threat
Sample of JSON sent to syslog
{
"sender":"user@example.com",
"recipient":"user@barracuda.com",
"subject":"YOUR FUND NOTIFICATION",
"date":"2022-06-22 - 16:34:34",
"category":"Spear Phishing Threat",
"type":"spam"
}

{
"sender":"user@example.com",
"recipient":"user@barracuda.com",
"subject":"Lily, Shop Gifts for Grads & Dads",
"date":"2022-06-23 - 15:42:58",
"category":"Spear Phishing Threat",
"type":"phishing"
}

{
"sender":"user@example.com",
"recipient":"user@barracuda.com",
"subject":"One more question",
"date":"2022-06-25 - 12:11:50",
"category":"Spear Phishing Threat",
"type":"becSpoofing"
}

{
"sender":"user@example.com",
"recipient":"user@barracuda.com",
"subject":"Private photos",
"date":"2022-06-25 - 15:22:32",
"category":"Spear Phishing Threat",
"type":"blackmail"
}
Account Takeover Alert
- Email
  Sample of JSON sent to syslog
  {
  "user_email":"user@barracuda.com",
  "user_display_name":"Internal, User",
  "subject":"HW#22.pdf",
  "sender_email":"user@example.com",
  "sender_display_name":"John, User",
  "date":"2020-06-23 - 21:45:27",
  "category":"Account Takeover Alert",
  "type":"Email"
  }
- Sign Ins
  Sample of JSON sent to syslog
  {
  "user_email":"user@barracuda.com",
  "user_display_name":"Internal, User",
  "login_ip":"189.210.116.245",
  "login_user_agent":"Windows/10 - Chrome",
  "login_country":"Mexico",
  "date":"2020-06-21 - 00:40:00",
  "category":"Account Takeover Alert",
  "type":"Sign Ins"
  }
- Inbox Rules
  Sample of JSON sent to syslog
  {
  "user_email":"user@barracuda.com",
  "user_display_name":"Internal, User",
  "rule_name":"Forward mail to John",
  "rule_sequence":"1"",
  "date":"2020-06-21 - 00:40:00",
  "category":"Account Takeover Alert",
  "type":"Inbox Rules"
  }

Data Format

Data is sent to the syslog in JSON format. You can parse the data any way you choose to meet the needs of your organization.