Sophos XGS 87 vs Check Point: How to Choose

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

Quick comparison

Compare Sophos XGS 87 against Check Point on price, ecosystem, support tier, and your existing team skill set.

Decision criteria

| Criterion | Why it matters |

|---|---|

| Existing skills | Your team's training is a sunk cost; switching vendors carries a re-training tax. |

| TCO over 5 years | Hardware + licenses + support + training + power. |

| Ecosystem fit | Controllers, cloud management, APIs. does it integrate with what you already run? |

| Support / RMA | Tier-1 vendors have predictable 24x7 TAC; smaller vendors vary by region. |

| Compliance | If your regulator names a specific vendor, comparison ends there. |

| Feature parity | Some vendor-specific features (SDN fabric, telemetry) don't have direct equivalents. |

When to stay with Sophos

• Standardisation across enterprise.
• Sophos Support + RMA matters for your SLAs.
• Existing investment in Sophos management / fabric.

When to switch to Check Point

• Sophos refresh quote is 2-3x the alternative for the same use case.
• Your team is already strong on the alternative vendor.
• The alternative's cloud-managed / SaaS architecture is the goal.

Frequently asked questions

Will this work on my specific SFOS (Sophos Firewall OS) version?

The procedure reflects current SFOS (Sophos Firewall OS) behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a Sophos Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the Sophos official documentation?

https://support.sophos.com/support/s/: search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides

• All Sophos fix guides → /sophos/
• All vendor guides → /vendors/

Related fixes

Related guides worth a look while you sort this one out:

• Sophos XGS 107 vs Check Point: How to Choose
• Sophos XGS 116 vs Check Point: How to Choose
• Sophos XGS 126 vs Check Point: How to Choose
• Sophos AP6 420 vs Check Point: How to Choose
• Sophos XGS 87 all ports dead: Diagnose & Fix
• Sophos XGS 87: How to back up configs nightly to a Git repo

References

• Sophos support portal: https://support.sophos.com
• Sophos knowledge base: https://support.sophos.com/support/s/
• Sophos security advisories: https://www.sophos.com/en-us/security-advisories
• Open a case: https://secure2.sophos.com/en-us/support.aspx

Reference material, not professional advice. Validate against your specific SFOS (Sophos Firewall OS) version and test in a non-production environment before applying.

Common patterns we see

When this symptom shows up on a Sophos device, three patterns repeat:

1. Recent firmware update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger. temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Before you start

A few things to confirm so the Sophos device fix goes cleanly:

• Latest firmware downloaded if you're going to update.
• Warranty + support contract status checked: opening sealed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time, rushing causes regressions.

Quick verification

Before you walk away from a Sophos device fix, run through:

1. Reproduce the original trigger. does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

Escalation guide

For a Sophos device, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the Sophos app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of warranty: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Should I update firmware first or last?

Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.