Find the Sophos Firewall serial number

The serial number uniquely identifies a Sophos Firewall. This identifier is required for support cases, warranty or RMA clarifications, license questions, central registration, account transfers, inventory lists and internal documentation.

In SFOS you can find the serial number directly in the Control center and also in the license area under Administration > Licensing. For everyday support, it makes sense to document the serial number, model, firmware version, license status and location together so that you don’t have to access the firewall in the event of a problem.

For an overview of the different Sophos accesses, Sophos portals: SophosID, Central, Support and Firewall accesses also fits. If the firewall later needs to be transferred to another account, Transfer Sophos Firewall to another Sophos Central account is the appropriate connection item.

Find serial number in SFOS dashboard

Menu path:

WebAdmin > Control center

Procedure:

1. Log in to the Sophos Firewall WebAdmin Console.
2. Open Control center or dashboard.
3. Read the Serial number in the system or appliance area.
4. Document serial number along with model, firmware version and location.

If the local WebAdmin Console is not accessible, you should not only look for the serial number, but also check the access itself. For local management access, Device Access and Local Service ACL on Sophos Firewall is relevant. If WebAdmin hangs, Restart Sophos Firewall WebAdmin GUI will help.

Check serial number in the license view

Menu path:

Administration > Licensing

In addition to the license status, the license view also shows the firewall’s registration data. You should check the serial number there when it comes to activation, subscription status, renewal, license synchronization or account assignment.

There are three practical checks:

• Serial number matches the device: prevents licensing of the wrong firewall
• Model and serial number match order or renewal: avoids queries when renewing licenses and support
• License status has been synchronized: shows whether local firewall and Sophos Central see the same status

In Sophos Central, one additional detail matters: For the Base License, the License ID is the same as the serial number. However, this is not the License Key from the license schedule. For renewal, activation or license transfer, serial number, License ID and License Key should therefore be handled as separate values.

If the serial number is correct locally but the license status is not, Activate Sophos Firewall License Key is the more appropriate next step. If Central connection and management need to be checked, Connect Sophos Firewall to Sophos Central will help.

Check serial number in Sophos Central

In Sophos Central, firewalls are under My Products > Firewall Management > Firewalls. You can search by name, model, or Serial Number and open the firewall details. In license management, the same perspective is available under Profile icon > Licensing > Firewall licenses.

This is especially useful when there is no local WebAdmin access, an account transfer is being prepared, or you need to check whether the firewall is in the correct tenant. For Controlled Zero Touch and OTP registration, the serial number is also the entry point. For HA devices, Sophos requires both serial numbers for OTP registration, separated by a comma. HA serial numbers should therefore never be recorded only as one shared cluster note.

Find serial number outside the dashboard

Depending on the situation, the serial number may also be available outside of the dashboard:

• on the device label of the appliance,
• in purchase, license or renewal documents,
• in internal inventory or CMDB systems,
• in Sophos Central or license views if the firewall is registered,
• in previous support tickets or RMA communications.

For virtual firewalls or cloud installations, you should document particularly carefully which serial number, license, instance and environment belong together. Otherwise, confusion quickly arises during migration, restore or support cases.

Which serial number in which case?

Not every situation needs the same perspective on the serial number. Especially with HA, replacement devices and central registration, you should clarify which serial number is meant before issuing a ticket or change.

• Single hardware firewall: Serial number, model, firmware version, location, license status
• Active-Passive-HA: Serial numbers of both nodes, initial primary, current role, HA status
• RMA or replacement device: old serial number, new serial number, RMA number, license transfer status
• Central Registration or OTP: Firewall serial number; with HA both serial numbers are clearly separated
• Account transfer: Serial number, source account, destination account, responsible admins
• Virtual Firewall: Serial number, license type, instance, hypervisor or cloud environment

This separation is particularly important for HA clusters. Otherwise, a license or RMA case can point to the wrong node, even though the productive fault is on the other device. Understand Sophos Firewall HA Cluster variants is suitable for the role logic.

Quickly provide serial number for support

The serial number alone is rarely enough for a support ticket. This identifier is the unique anchor, but support must be able to classify the device, version, error and impact. It is therefore best to copy the serial number directly together with the most important operating data.

Practical template:

Serial number:
Model:
Firmware version / build:
Location:
Central account or tenant:
HA cluster: yes/no
Affected HA node:
Affected function:
Error since:
Impact:
Latest backup available: yes/no

If the firewall is part of an HA cluster, both serial numbers should be specified. It is also important to know which node is affected, what role it had at the time of the error and whether a failover took place.

Do not confuse serial number, license and account

The serial number identifies the firewall, but does not automatically prove that the license, support and account assignment are correct. This information should be checked separately, especially in the case of renewals, changes to service providers, HA clusters or virtual firewalls.

• Which firewall is affected?: Serial number, model, location and firmware version
• Is support or a bundle active?: License status and terms in the product or license area
• Which account has the firewall in it?: Sophos Central or SophosID account assignment
• Does the serial number belong to the correct order?: License documents, renewal documents or invoice
• Can the firewall be restored?: Current Backup, Secure Storage Master Key and Restore Plan

Understanding Sophos Firewall Base License is suitable for the classification of base license, support and subscriptions. If account assignment and license responsibility change, you should also check Transfer Sophos Firewall to another Sophos Central account.

What the serial number is needed for

Typical situations:

• Open a support ticket with Sophos or partner.
• Check license status or renewal.
• Assign firewall to an account or central tenant.
• Clarify hardware defect or RMA.
• Update asset inventory.
• Document backup, restore or replacement processes.

The serial number should not be passed on in isolation for support cases. Firmware version, model, time of error, affected function, logs and a short description of what has already been checked are also helpful. The process is described in How to open a support ticket with Sophos.

In the case of hardware defects or RMA cases, it should also be checked whether the model, serial number, warranty or support status and location are clear. The classification can be found in Classify Sophos Hardware Warranty, Support and RMA.

Avoid typical mix-ups

Serial number, model, license, account and backup are sometimes mixed up, especially in support and license cases. This leads to unnecessary queries.

• Serial number confused with model: XGS 2100 describes the platform, but not the specific device
• License status passed on as a serial number: The license explains the right to support, but does not necessarily identify the affected appliance
• HA cluster only documented with a serial number: In the case of an RMA, license check or failover, it is unclear which node is affected
• Replacement device not recorded separately: After an exchange, old and new serial numbers in tickets, CMDB or renewal documents may diverge
• Backup stored without serial number: If there are several similar firewalls, it will later be unclear which device the backup belongs to

After a hardware replacement, the documentation should be consciously updated: new serial number, old serial number, RMA number, restore date, backup source, license status and central assignment. When restoring to replacement hardware, Create or restore Sophos Firewall Backup is the key connection item.

Follow up after RMA, restore or transfer

After an exchange or transfer, the serial number should not only be closed in the ticket, but also corrected in all operational departments. Typical rework:

• Compare Sophos Central and license view.
• Update monitoring, backup and inventory systems.
• Add HA documentation with old and new serial numbers.
• Store RMA or transfer number with the asset.
• Check support and renewal documents for incorrect old serial numbers.
• After restore, check whether backup, license, central connection and location documentation match.

This step seems banal, but it saves a lot of time later. Old serial numbers in monitoring, CMDB or renewal documents will otherwise result in the next support case starting again with the basic clarification.

Documentation check

At least the following information should be maintained in firewall documentation:

• serial number,
• model and appliance type,
• firmware version,
• location and function,
• responsible Sophos Central tenant or account,
• License or renewal information,
• HA role if the firewall is part of a cluster,
• last backup time,
• Secure Storage Master Key if encrypted backups are used,
• Contact and support responsibilities.For HA clusters, you should document both serial numbers and clearly state which node has which role. For HA basics, Understanding Sophos Firewall HA Cluster variants fits. For backup, restore and SSMK, Create or restore Sophos Firewall backup is the more suitable connection article.

FAQ