Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

About the Device

Sophos Next-Gen Firewall is a comprehensive cybersecurity solution designed to protect modern networks from advanced threats.1 It goes beyond traditional firewalls by offering a robust set of features to safeguard against evolving cyberattacks.

Device Information

 Entity

Particulars

Vendor Name

Sophos

Product Name

Firewall (Formerly Known as XG Firewall)

Type of Device

Hosted

Collection Method

Log Type

 Ingestion label

Preferred Logging Protocol - Format

Log collection method

Sophos Firewall (Next Gen)

SOPHOS_FIREWALL

Syslog - Structured

CyberHub

Port Requirements

Source

Destination

Port

Sophos Firewall

CyberHub

514 (UDP)

To facilitate secure communication and align with our best practice, we strongly encourage the use of Transport Layer Security (TLS) between your security devices and our Adaptive MxDR platform for event forwarding.

While we understand that TLS support may not be available on all devices, if your devices do support TLS communication, we recommend utilizing port 6514 for seamless integration.

In some cases, the upgraded version of the device might incorporate TLS support without prior notice. If you come across such a scenario or for further assistance in configuring TLS, we kindly ask you to reach out to your dedicated Adaptive MxDR Service Delivery Lead.

Device Configuration

  1. Login the Web UI.

  2. Navigate to System services > Log settings and click Add.

  3. Enter a name of Syslog Server.

  4. Specify the below settings:

 

IP address/domain

IP address or domain name of the syslog server. Logs are sent to this server.

Secure log transmission

Encrypts logs sent to the syslog server using TLS.

Port

Port number for communication with the syslog server.

Facility

Facilities reflect the names of processes and daemons, and inform the syslog server of the origin of the log.

  • DAEMON: Processes running as daemon service

  • KERNEL: Kernel processes

  • USER: Processes started by signed-in users

  • LOCAL0-LOCAL7: You can use these for your own purposes.
    Example: If you configure LOCAL1 for firewall 1 and LOCAL2 for firewall 2, the syslog server receives the respective facility value along with the log.

Severity level

The device logs all the messages at and above the logging severity level you select.

 Select INFORMATION here.

Format

Select

  • Device standard format (legacy): A custom format in which the number of log data fields differs for each module.

 

image-20240805-091546.png

  1. Click Save.

  2. Navigate to Log settings and select the logs you want to send to the syslog server.

 After configuring syslog server, configure logs to be sent to the syslog server by selecting checkbox against the log under Syslog . 

To record logs you must enable the respective log and specify logging location. Administrator can choose between On-Device (local) logging or Syslog logging. 

The following Log Types must be ticked to send syslog to LCP.

  • Base Firewall (Security Policy log)

l1.png
  • Web Protection (Web filtering log and Application filtering log)

l2.png
  • Network Protection (IPS log)

    l3.png
  • System log

l4.png

Integration Parameters

Parameters required from customer for Integration.

Property

Default Value

Description

IP Address

Sophos Firewall interface IP address

Hostname or IP address of the device which forwards logs to the CyberHub

 

  • No labels