For Term or Master Licensed customers: On the Central License page, if there are 2 or more of the same license line items listed (for example, in the scenarios related to; trial and purchased licenses together, current and future renewal licenses together, or Enterprise Dashboard master licenses)

The usage calculated between the licenses on this page may not be clear. Product usage may not be split evenly between the licenses (one license may show overage, while another will show underutilized), while others may show the usage duplicated between the two.

This usage calculation distribution issue will not affect products' use/management or development. Note: Flex licenses will not be affected by this behavior as they will only have one line item per license possible.

• CPG 2023.43

Central customers are not able to export an Event report as a PDF (https://central.sophos.com/manage/reports/protection/events/create ).

• It will appear as though it downloaded as normal, though the actual file is only zero bytes/ not valid

• Reports can be exported as CSV.

Event reports can be exported as a CSV file in the interim of this being fixed.

There is a known behavior on the Partner Information page within the Central Dashboard, where the partners' Contact Information (Phone/Website) will be blank.

In the interim of this being updated in the future, if you need to find your Partner's contact information: Go to https://partners.sophos.com/english/directory/ - Below the map on the left-hand side, enter the name of your Partner as it is shown on your Central Dashboard partner information page and select the result shown.

• CPG 2023.40

When setting the Allocation for a license within Enterprise Dashboard (with Master Licensing) - If there are duplicate licenses assigned to your Enterprise Dashboard (for example a renewal license that will start after the first one expires)

When using the Allocation window, the total ‘Enterprise Limit’ will show duplicated as well. For example, if you have two licenses for 100 seats (each only being active one at a time) - the Enterprise limit should show 100. Currently, due to this issue, it will show 200.

This will not restrict the use of the Allocation feature, and this will be resolved in a future update.

This will not restrict the use of the Allocation feature, and this will be resolved in a future update.

• CPG 2023.40

The 'get monthly usage' link that resides in the 'Managed Customer Usage' section within the Central Partner Dashboard will disappear if the page is refreshed.

The location for where this link goes is within the Partner Portal and can be accessed directly at: https://partners.sophos.com/English/Reseller/msp_usage_files.aspx

• CPG 2023.37

Engineering is aware of an unexpected behavior where a logged in Super Admin does not have the option to select other Administrators ‘Reset MFA’ option.

Dashboard > People > Select Administrator > on top left of that users page. Hovering over the link for ‘Reset MFA’ shows a red circle with a line through it, which is not selectable.

In order to have the MFA reset for that individual, Please reach out to Customer Care by creating a Customer Care case on the Sophos Support Portal and request a PIN reset process to be implemented (providing the email address of the admin in question). This process may take one or more days to be completed as it requires additional security checks to ensure the person requesting the reset is validated.

Some Partners are unable to create New Trial accounts within the Sophos Central Partner Dashboard.

After clicking on the "Start New Trial" button the error received is "The customer can't be created right now because of server problems. Please try again later." or "This data requires further screening. Please retry your request later. "

One known reason for this is caused by an updated compliance check for trials related to the State code (in the Create a New Trial form). The State field (for US states) must be in the standard 2-letter abbreviation E.G.: For Alabama, use AL.

Update the State field with the two-digit abbreviation and resubmit the new trial form.

The regulatory authorities in certain countries have specific SMS requirements, which may result in some customers not receiving SMS or receiving them as potential spam when signing in.

List of countries with special SMS requirements:

• Belarus

• Egypt

• Jordan

• Kuwait

• Philippines

• Qatar

• Russia

• Saudi Arabia

• Sri Lanka

• Thailand

• Turkey

• United Arab Emirates (UAE)

• Vietnam.

You may use the Multi-factor Authentication's authenticator app or the email and pin method to complete the sign-in process in any scenario where the SMS code is not being received.

• CPG 2023.37

Currently if a partner removes the ‘Central Firewall Reporting Advanced’ license for a flex customer using the ‘Change License’ wizard; it will show an icon under the ‘Central Firewall Reporting Advanced’ column in the Partner Dashboards' Customers page.

The expected behavior is that no icon is shown.

The feature/function for Central Firewall Reporting Advanced is correctly removed from the customers Central Dashboard.

This can be ignored in the interim of it being removed in the future.

If the API credential previously used is no longer present within Settings > API Credentials Management; and there is nothing in the Audit log showing it was removed, then the credential has aged out.

Sophos Central API credentials have defined lifetimes during which they may be used to authenticate to Sophos APIs for data collection and alerting. By design, when an API credential expires it will no longer be allowed to authenticate to Sophos APIs. Creating new API credentials to replace the prior credentials will quickly resolve any access interruption from expired API credentials.

The creation, last used, and expiration dates for unexpired API credentials can be reviewed in Sophos Central's API Credentials Management page. Since expired API credentials are unusable any references to them are automatically removed from the Sophos Central console by design.

• CPG 2023.31

Partners logging into the Partner Central Dashboard via Federated login within Microsoft Edge browser, and using the German as the primary/preferred browser language, will encounter login failures. This authorization will fail and return you back to the login screen again.

In the interim of this be fixed, and where applicable/possible, a Parnter can do one of the following:

• Login using Edge with the Central authentication method (regardless of browser/language).

• Login using Edge and temporarily changing the preferred language to something other than German.

• Login with a different browser (Chrome/Firefox)

Sophos is aware that some US customers may incorrectly see the wrong ‘State’ displayed in their Central Dashboard > Account Details page. It may show ‘Armed Forces America’, instead of the correct company’s State.

This can either be ignored in the interim of a future automatic fix, or a Support Ticket can be raised up to our Customer Care team - asking to update the Central accounts Evaluation record in question so that the ‘State’ field will contains a two-digit state code only

• CPG 2019.45

When using custom date ranges within an Event report, the returned results may incorrectly include events that go beyond the expected Timezone offset. 

Additional information can be found in our knowledge base article https://support.sophos.com/support/s/article/KB-000036898

• CPG 2023.31

Partners with either Connectwise Manage or Datto Autotask PSA integrations may not see the Sophos Central Portal Encryption Add-on for Email Advanced product usage updating within your PSA applications

The usage will be shown correctly in both the customers Central Dashboard, and the Partner Dashboard.

In the interim of this being fixed, Partners will need to manually update the usage for this one product within your PSA application if this is seen before the next billing.

If this is found after the current billing period, please email msporders@sophos.com with
1. Your name, partner account name, the customer account name
2. the amount of usage correction that needs to be fixed for Sophos Central Portal Encryption Add-on for Email Advanced. and
3. This Engineering ID https://sophos.atlassian.net/browse/CPLAT-50800#icft=CPLAT-50800 for reference as to the reason for the correction needed.

When a subestate is unlinked from an Enterprise Dashboard (EDB) it will be removed from EDB, but locally (under the Account Preferences section) - the top ‘Enterprise Management’ section will show it is part of the EDB it was unlinked from, with directions to contact the EDB administrator. (the EDB administrator is not able to resolve this)

This will prevent this Central Dashboard from being able to enable EDB from this account in this state.

To resolve this in the interim of this being resolved, you will want to contact Sophos Customer Care Support team and request that a new ‘Customer’ account be applied to your Central account. This will fully remove the previous EDB connection and allow you to enable EDB in this Central Dashboard if needed.

• CPG 2023.28

Sophos Engineering is aware of an issue on the Co-branding page within the Partner Dashboard. Under the uploaded co-branding image it will say ‘false’ instead of the name of the file uploaded. This will not have any impact or affect with the co-branding functionality and it can be ignored in the interim of this being fixed.

This typo can be ignored in the interim of it being fixed.

• CPG 2022.21

The Partner Dashboard ‘Sophos Customers’ page, may incorrectly show an empty Optix trial icon for one or more customers. The customers' dashboard does not have an Optix trial enabled.

In the interim of this being removed, the icon should be ignored.

• CPG 2023.22

Some customers may see an alert in the dashboard showing the message: “Microsoft API permissions are missing." Even when the permissions are correctly configured.

This alert is incorrectly be triggered due to a timeout with the Azure AD sync. While the timeout is temporary, it is incorrectly triggering this alert to be sent.

What to do if you receive this alert: go to your Global Settings > Directory Services > select your Azure AD sync service in question.

• If this was a legitimate error, you will see a banner with the same message stating API permissions are missing, and the sync would fail.

• If this is related to this known issue, you will not see an extra banner, and your sync is normal/successful.

The alert can be acknowledged when its identified as related to this known issue.

The alert can be acknowledged when its identified as related to this known issue.

• CPG 2023.22

There is a known behavior seen where the Partner Dashboards Alert page will not load fully if the browser webpage is refreshed after they have opened a customer to manage in a different tab.

If a Partner needs to refresh the Alerts webpage (and there is a Customers Dashboard loaded in another tab), logging out of the Customers Dashboard first will avoid encountering this issue.

Possible errors seen

• (ADFS) "Failed to change IDP status" error attempting to add a new Identity Provider configuration.

• (Okta) Attempting to log in via SSO you receive an "Expected 200 OK, got: 403 Forbidden" error

One common reason for these errors is a result of customers' local IDP server being behind a firewall with regional restrictions that is preventing communication with Auth0 services hosted in Europe.

Sophos Federation login utilizes Auth0 as a third-party proxy service for integration with different IDP providers. This requires customers on-premise IDP server to be able to communicate with Auth0’s servers. Please whitelist the IP addresses from the Europe region: https://auth0.com/docs/secure/security-guidance/data-security/allowlist

Customers (Central Dashboard and Enterprise Dashboard), as well as Partners (Partner Dashboard) - could see excess amounts of Audit log entries that reference both 'alerts:read' and 'endpoint-state:read'.

What are these audit log entries?

• These are entries made by your Partner's RMM applications that utilize our Sophos plug-in/Management APIs.

• It is the Sophos Plugin running on the Partners Server that is the source of the request. (examples of some of the utilities: https://community.sophos.com/sophos-integrations/w/integrations )
  

Why do I see this in my Audit Log?

• The RMM Sophos software plug-in is polling all of the Partner's Customers. This currently includes any of the Partners customers who are either not managed by the Partner or are currently Trial/Evaluation customers.

• Our APIs handle the rejection of non-managed tenants by understanding the permissions embedded in the API token, and returning a 403 when the credential does not have permission for that tenant. This in turn results in an Audit log entry for access denied being logged in both the Central Dashboard (and the corresponding Partner and/Enterprise Dashboards)
  

Can these entries be prevented?

• If the entries are once every 20 to 30 minutes, this is currently expected until there are further improvements made within Sophos plugins.

• If the polling happens once every 6 minutes, it is possible to have this reduced to every 20 minutes.

  • The Partner is expected to be using an older version of RMM plugin software (Automate) that includes an update to reduce this.

  • When the Partner updates this plugin, the polling will be reduced to average of once every 20 minutes.
    

How can I tell if this is related or something different?

• It will match this known issue when:

  • Your Central Dashboard is not managed by your partner, or you currently have an evaluation/trial license.

  • The IP address in the audit log entry will be the source of the script (linked to your Partner)

  • The ‘ClientID’ # will be an API ID used by your Partner.

• If there are any questions or concerns about these entries, please contact Sophos Technical Support for help or clarification on what is being logged. Please reference this Known Issue entry.

If there are any questions or concerns about these entries, please contact Sophos Technical Support for help or clarification on what is being logged. Please reference this Known Issue entry.

• CPG 2021.40

When adding users on the Federation Global settings page (within the 'Custom Rules' user selection window), this can take longer than expected (minute +) when there are hundreds or thousands of users with logins to display.

While the performance/slowness is currently expected for customers with a large amount of users; If your list of users fails to load at all, and you are not able to add any custom rules, please raise up a Support case with Sophos, so that we can help manually add these for you in the interim.

Please provide us with the email addresses and login rule requested (Federated only, Central only, or Federated and Central) for those who you would like to have added. Please also reference 'CPLAT-44544'. Technical Support will be able to manually add these in, if it is not possible to do so by a customer.

The remote assistance enablement in Sophos Central Dashboard may take longer than expected if there are a lot of self-service user accounts/Admin user accounts exist.

Reference KB Article: Sophos Central: Turn on Sophos Support remote access for either MSP/Flex or Enterprise Master-licensed Sophos Central accounts

In the interim of this being fixed, please wait until you see a pop-up message/green message box "Remote Access Enabled" once click the Save button. You may experience a number of pop-up windows with "Remote Access Enabled" message.

• CPG 2021.40

Central API: “Error 409. You can't use this API to delete users synced from Active Directory” returned when trying to delete a user who was added to Central via Adsync before November 21st, 2021 and has been unlinked (https://developer.sophos.com/docs/common-v1/1/routes/directory/users/{userId}/delete ).

• Users added to into Central after this date will not encounter this issue.

• This does not affect or prevent manually deleting these users within Central Dashboard UI.

These users affected will need to be deleted manually within Central Dashboard UI

• 2017.32

When viewing or exporting events based on Dates from the 'Logs & Reports' section of Sophos Central Admin;

The resulting events will be shown based off of a 24 hour UTC day instead of a 24 hour period within the time zone of the user.

"This is currently expected behavior though there are plans to have this changed in the future to better match the time zone of the user generating the report.

Additional information can be found in KBA: https://support.sophos.com/support/s/article/KB-000036898

• CPG 2022.27

If the API credentials used are active and confirmed valid (this can be tested using postman or curl to do a basic whoami and tenent list query outside of Kaseya) and this continues to trigger this error - Please ensure that the following is open (without any regional restrictions) from your VSA server:

• Open traffic to and from kaseya.int100fra.ctr.sophos.com

• Ensure the following IP Addresses are whitelisted - 18.159.54.20 , 3.123.181.234 , 52.59.169.88

Please ensure that the following is open (without any regional restrictions) from your VSA server:

• Open traffic to and from kaseya.int100fra.ctr.sophos.com

• Ensure the following IP Addresses are whitelisted - 18.159.54.20 , 3.123.181.234 , 52.59.169.88

Documented in https://community.sophos.com/sophos-integrations/w/integrations/105/sophos-integration-with-kaseya-vsa

• CPG 2020.14

When using Internet explorer please note that you may experience longer than normal page load times working in Sophos Enterprise and/or Sophos Central dashboards.

We expect to address this in the future, in the interim please use Chrome or Firefox to manage Sophos Dashboards.

• CPG 2022.18

Central Dashboard: Custom firewall reports are only able to be sent to local Central Administrators (not Partner or Enterprise administrators)

If a Partner or Enterprise Administrator attempts to add non local administrators to firewall reports (Firewall Management > Report Generator > (add or edit any report) > Available Recipients section.

If you add any Partner or Enterprise Dashboard administrators, these will not receive the report via email. Additionally, when you reopen the report, these administrator names added will show as UUIDs.

There is no workaround to this issue

There is no workaround to this issue. Currently only local administrators are able to be used for Firewall report delivery at the Central Dashboard level

There is a known behavior when viewing particular events on the Events Report page (https://cloud.sophos.com/manage/reports/protection/events/create). The Server re-protected events will remain visible, even after unticking the Event type ‘Computer and Server re-protected’ category.

Until this is resolved, the “Computer or server re-protected” event needs to be ignored in the report. As we understand that this can be annoying, there is a limitation in our current design, and the fix required, unfortunately, needs a good amount of changes. We are in the transformative process of handling all events to go through a centralized workflow.

"Reports that are exported as a PDF have times annotated as UTC

Reports that are exported as CSV have times listed in the time zone of the user running the report.

The times are the same in UTC "

This difference in how the times are presented between reports will be addressed in a future version of Central Admin.

This is an example of what to expect (all times are equal):

1. PDF is UTC time (Regardless of time zone where report is pulled)
= 9/8/17 10:57 PM

2. CSV report pulled from system in EST
= 2017-09-08 T 17:57:01-05:00

3. CSV report pulled from the system in PST
= 2017-09-08 T 14:57:01-08:00

• 2019.12

When logging into Central Partner Dashboard from the id.sophos.com page, you may sometimes get re-directed to a settings/text page instead of the Dashboard

Clearing the browser's cache will temporarily resolve this, though it may happen again until this is resolved.

In the interim, you can avoid this by either logging in to either the Partner Portal first (https://partnerportal.sophos.com then select the 'Manage Sophos Central' link) or log directly into the Partner Dashboard (https://cloud.sophos.com/manage/partner/)

Additional information can be found in KBA: https://sophserv.sophos.com/article/121583 (selecting the question "Why do I see a page of text after attempting to log into Partner Dashboard?")

• CPG 2022.09

When using API credentials (Service Principals) - certain jwt token refresh errors can be logged in the Central Dashboards Audit log as 'anonymous:' and 'failed authentication' with the IP of source. (eg. siem.py script/ ADsync utility/ etc). This is an expected logging event that can occur during normal operation and it does not require any follow up action.

These entries can be ignored. See https://support.sophos.com/support/s/article/KB-000043845 for more information.

• CPG 2020.47

Sometimes during the EDB enablement process, the conversion of the Central Super Admin to Enterprise Super Admin may fail. In that scenario, you will get an 'Authentication Failure' when trying to log back into your newly created Enterprise Dashboard.

If you encounter this, please follow the 'Forgot Password' link/process which will repair your login and access for that account.

• CPG 2019.15

While there is no limit given to the number of users that can be attempted to upload (outside of the 2MB file size limitation).

It is recommended to upload users in batches of 1000 at a time. It is possible to upload more at once, though depending on the time of day (peak business hours) you may experience this timeout behavior.

Additional information can be found in customer KBA https://support.sophos.com/support/s/article/KB-000038811?language=en_US

Using certain browser extensions, error 403 or 404 is received during the selection of the authentication type during MFA setup

Additional information can be found in customer KBA https://support.sophos.com/support/s/article/KB-000038802?language=en_US

• Not planned to be changed.

Application Control cannot detect/block script applications or Java JAR applications during direct execution. It requires a binary package such as .app, .pkg, .dmg to detect/block. On access scanning is not affected by this limitation.

None

• Not planned to be changed.

The feature to enable domain name override for reported users on macOS, detailed in this KB: https://support.sophos.com/support/s/article/KB-000036151 , requires that the user account type is Mobile.

By default, a direct Active Directory join uses this user type, however some other providers may not set it. Sophos’ detection of the user as a domain one requires the user account type to be mobile to trigger. There are no plans to change this behavior at this time.

If the provider allows it, set the user account type to Mobile. Apple has provided information here: https://support.apple.com/en-ca/guide/mac-help/mh32157/mac

Apple Advanced Tracking and Fingerprint Protection on macOS 14 (Sonoma) by design does not pass traffic to any web filters on the system. While this feature is enabled, Web Protection / Web Control will not be able to see the traffic.

This feature is enabled for Private browsing tabs in Safari by default on macOS 14 (Sonoma), and only affects that OS. In the Safari security preferences, it is possible to also enable this feature for all browser connections, or none. Any connections with this feature enabled will not be checked for Web Protection / Control

This feature can be disabled in the Safari security preferences.

Apple iCloud Private Relay uses an isolated connection that the OS does not provide to Sophos for purposes of web protection or control. If a user enables this (paid subscription from Apple), we cannot provide web protection or control on the system for non-local traffic.

None

• TBD

Multiple times per day the security heartbeat can report drops for macOS Monterey clients when they did not actually drop.

None

When Sophos and LightSpeed relay agent are installed together, web browsing will fail to load webpages and installs will fail.

Uninstall LightSpeed relay agent

Ava Reveal’s web protection filter and the Sophos web protection filters may cause web browsing to fail when both are loaded.

Sophos has worked with Ava and we have found that multiple content filters and a transparent proxy triggers an OS issue. As of August 2022, this is considered an incompatibility due to the OS.

Turn off Ava Reveal extension or uninstall Sophos for MacOS

The device summary in Sophos Central lists ‘Endpoint Protection' or 'Server'Protection' as 'Pending...', when the Endpoint is assigned with a Special or Static Package via the Sophos Central 'Software Management’ functionality.

This is a cosmetic issue as static or special packages no longer provide information about the legacy ‘Endpoint Protection' or 'Server'Protection' modules and can be ignored.

None

Customers who have devices hosted in Azure will have the Azure VM ID sent to Sophos Central which will result in the deduplication process being carried out on the device.

See article: https://support.sophos.com/support/s/article/KB-000035040

The checks performed by Sophos Central determining if a device is a duplicate or not is case sensitive.

Sophos Central checks for the following information before making the decision to create a new entry or keep the existing one during the client registration:

-Domain name
-Computer name (Netbios name)
-OS (e.g. Win10, not more specific/detailed than that)
-FQDN
-Mac serial number (if a Mac)
-Whether SSPL or not (Linux)
-If it is marked as a clone always create a new entry

All of the checks are case-sensitive.

• known limitation, not planned to be fixed

CDB Hero Reports export PDF contains no data when created with Central Admin Dark Mode enabled.

Use light mode to generate a PDF report

• Core Agent 2023.1

• Core Agent

Even though updating correctly from an Update Cache, Endpoints running on Windows 7, Windows 8.x, or Windows 10 x86 as well as Windows Server 2012 R2 (and below) are not listed in the ‘Using This Cache’ list in Sophos Central.

None

• Core Agent 2023.2

• Core Agent

The File Integrity Monitoring setup may file with the error “FIM service: Event Journals folder location could not be found atB:\ProgramData\Sophos\Endpoint Defense\Data\Event Journals: [FAILED]” if a drive letter mapping A: or B: exist on the system that matches the actual system root, causing it to mistakenly set A: or B: as the system drive. Example:

B: "\Device\HarddiskVolume1"
C: "\Device\HarddiskVolume10"

Change the "A:" or “B:” drive mapping to a different volume that would not match the system root or set the drive mapping to “D:” (or higher), so that the “C:” drive mapping will be matched first.

• Not planned to be fixed (W10 32bit/W8.1/W8/W7/WinServer 2012/R2/SBS 2011/2008R2)

• Core Agent

Right-click scan of all files and folders in a UNC path only scan files in that folder and one layer of sub-folders. This issue affects legacy platforms only (W10 32bit/W8.1/W7/WinServer 2012/R2/SBS 2011/2008R2).

The right-click scan operation will need to be performed on each sub-folder

• Core Agent 2023.2

• Device Encryption

The Sophos Outlook Add-in for Secure File Sharing is not available in the List of Add-ins from Outlook, despite being enabled for the User in the Central Device Encryption policy

The missing Outlook Add-in is caused by an issue with the Central Device Encryption installer, which is creating the registry key "HKLM\Software\Microsoft\Office\Outlook\Addins\SophosEncryptionAddin" but not adding the required values, if the Device Encryption policy "Enable Outlook add-in" is disabled at the time of the installation or update.

See KBA for details:
https://support.sophos.com/support/s/article/KB-000045689

• Core Agent 2023.2

• Core Agent

Windows Servers might show an increased non-paged pool memory consumption from a pool tag labeled Sg01 or Sg03. The memory is allocated by the Sophos Endpoint Defense Data Content Records (used to keep track of PE-file information and SHA-256 values) which get loaded on boot.

None

• Intercept X 2023.2

• Intercept X

Sophos Central Endpoints with Intercept X 2023.1.1 that have been upgraded from an earlier version (e.g. 2022.1.3) still load the HitmanPro.Alert Service although Intercept X was fully disabled via the Threat Protection policy setting "Turn on anti-ransomware protection and all exploit mitigations".

See KBA for details:
https://support.sophos.com/support/s/article/KB-000045690

• Core Agent 2022.3.0.56 (Win10 64bit and later) - Core Agent 2022.3.0.84 (WinServer 2016 and later) - Not planned to be fixed (W10 32bit/W8.1/W8/W7/WinServer 2012/R2/SBS 2011/2008R2)

• Core Agent

Uploading larger files to FileVine or other document management systems may fail.

Turn off Web Control
Turn off Real-time scanning Internet

• Core Agent 2023.2

• Core Agent

While Windows Operating System is in Connected Standby Mode (Modern Standby), the differentiated throttling applied by the Windows Desktop Activity Moderator (DAM) may allow some processes to generate network traffic even though SntpService is still inactive (3: heartbeatLost → 4: heartbeatMissing).

In such cases, the firewall will report the endpoint as Missing Heartbeat.

Until a fix for the issue is available, you can use one of the following workarounds:
a) Turn off HBT via Sophos Firewall rule OR
b) Do not use the Connected Standby function
More information on Connected Standby: https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/modern-standby

• Core Agent

If “File types” is set to “Warn” for “Executables” in the Web Control policy and “Decrypt HTTPS websites using SSL/TLS” is enabled in the Threat Protection policy, we may not display our warning page for Web Control when a download occurs.

When a download occurs we will try to insert/replace the download page with our warning page, which may not work depending on how the download page is built. In the local Sophos Endpoint UI event page, a “Warn” message will be seen.

1. Change the setting in Web Control for "Executables" from "Warn" to "Allowed" or "Blocked"
2. Create a Website exclusion of the URL in the Threat Protection policy

• Core Agent 2023.2

• Core Agent

Following an upgrade to Core Agent 2023.1, scheduled/on-demand scans fail on some devices.

This has been seen on devices using Google Drive File Stream and RAM Disks.

See article https://support.sophos.com/support/s/article/KB-000045592

• Intercept X

The "Prevent privilege escalation" feature prevents attacks from escalating a low-privilege process to higher privileges to access systems. This may clash with Privileged Access Management (PAM) tools that are installed on the Endpoint to manage the elevation of rights, resulting in "PrivGuard" alerts being reported against the elevated processes.

In these situations, the "Prevent privilege escalation" feature is incompatible with the Privileged Access Management (PAM) software and should be disabled via the Threat Protection policy on impacted Endpoints.

For more details see: https://support.sophos.com/support/s/article/KB-000043114

• Core Agent 2023.2

Following an upgrade to Core Agent 2023.1, legacy platforms report a missing heartbeat connection.

Depending on your policy, the Sophos Firewall may have restricted network access for affected devices.

See article https://support.sophos.com/support/s/article/KB-000045533

• TBD

• Core Agent

The gold image switch is not working for VMware Horizon with ClonePrep environment.

The issue occurs here because when using “ClonePrep” the device is snapshotted and then spun up - a snapshot is then created from this new machine before it's snapshotted and cloned again.

As an example: The machine they use as the “GoldImage” GOLD-W10 is then renamed to W10-1 itself and then from W10-1 a new machine is created called W10-2 and this then repeats.

The workaround is to use the older style gold image prep script

The workaround is to use the gold image prep script during the shutdown.
Details are described in the following KB: https://support.sophos.com/support/s/article/KB-000035040

• Core Agent 2023.1

• Core Agent

Due to an issue in the enumeration function of the Sophos Endpoint, Endpoints with Data Loss Prevention enabled may freeze and eventually crash with stop code DRIVER_POWER_STATE_FAILURE (9f) when a security token (e.g. YUBIKEY) is attached to the system.

Until a fix for the issue is available, exclude storage destinations from any Data Loss Prevention rule, to prevent the issue

• Core Agent

On computers with Sysinternals System Monitor (Sysmon) installed and configured with a "FileDelete" rule targeting ".bin" files, Sophos Endpoint Defense Service (SEDService.exe) will constantly run with high CPU.

This is caused by a conflict with Sysmon when SEDService.exe performs compression of Event Journal data and the subsequent deletion of the uncompressed *.bin Event Journal files. When .bin files are covered by a Sysmon FileDelete rule, Sysmon tries to rename/archive the Tamper Protected file and conflicts with Endpoint Defense Service, leaving the uncompressed file in place.

Removing .bin files from the TargetFilenames of the FileDelete rule resolves the issue. For details, please see KB-000044827

• Core Agent

Updates fail when Sophos Central Endpoint is installed alongside Check Point VPN version 86.40

Please see KBA for workaround steps - https://support.sophos.com/support/s/article/KB-000044497

• TBD (Win10 64bit and later) - TBD (WinServer 2016 and later) - TBD (W10 32bit/W8.1/W8/W7) - TBD (WinServer 2012/R2/2008R2)

• Intercept X

The creation of *.mdb files may trigger a Lockdown detection.

Disable Lockdown mitigation for MSAccess application via Threat Protection policy only to affected systems.

• TBD

• Intercept X

With ‘Monitor Mode’ enabled for the Sophos Central Account (Account Details -> Account Preferences -> Evaluation Modes -> Monitor mode), creating a Diagnose Log from Sophos Central will trigger a Credential Guard alert when Diagnose calls “C:\Windows\System32\tasklist.exe /M /FO CSV”

This is a detection that only occurs in Monitor Mode.

None

• TBD (Win10 64bit and later) - TBD (WinServer 2016 and later) - TBD (W10 32bit/W8.1/W8/W7) - TBD (WinServer 2012/R2/2008R2)

• Intercept X

HitmanPro.Alert Service (Hmpalert.exe) is consuming high CPU when multiple thousand Exploit Mitigation Exclusions are applied to an Endpoint and stored in the Endpoint registry (e.g. under HKEY_LOCAL_MACHINE\SOFTWARE\HitmanPro.Alert_policy_\java.exe).

None

• TBD (Win10 64bit and later) - TBD (WinServer 2016 and later) - TBD (W10 32bit/W8.1/W8/W7) - TBD (WinServer 2012/R2/2008R2)

• Intercept X

Moving and overwriting files on a network location with Ransomware Protection enabled locally may slow down the move operation.

None

• TBD (Win10 64bit and later) - TBD (WinServer 2016 and later) - TBD (W10 32bit/W8.1/W8/W7) - TBD (WinServer 2012/R2/2008R2)

• Intercept X

Ransomware Protection may raise a false alert due to linking unrelated files together, when an identical number of bytes is being read/written

None

• TBD (Win10 64bit and later) - TBD (WinServer 2016 and later) - TBD (W10 32bit/W8.1/W8/W7) - TBD (WinServer 2012/R2/2008R2)

• Intercept X

The HitmanPro.Alert logfile (located at C:\Programdata\HitmanPro.Alert\Logs\Sophos.log) contains entries for non-normalized application paths, which are often logged for compiler applications:

Example:

YYYY-MM-DDTHH:MM:SS.FFFZ [Protected] PID 1234, Features 007D2E3000000100 Silent 0020000000000100, c:\\msys64\\opt\\rtems-5-win\\bin\\..\\lib\\gcc\\arm-rtems5\\7.5.0\\..\\..\\..\\..\\arm-rtems5\\app.exe

This can be relevant when defining exclusions for specific applications.

None

• Intercept X 2022.1.3.3

• Intercept X

Ransomware Protection may raise a false alert against license documents (license.html and license.htm)

None

• Intercept X 2022.1.3.3

• Intercept X

Ransomware Protection may raise an alert against Backup/Sync software if actual ransomware notes are restored from a backup and therefore terminates the backup/sync process.

None

• Intercept X 2022.1.3.3

• Intercept X

Ransomware Protection may raise a false alert due to linking unrelated files together when files share the same name (but different file extension)

None

• Intercept X 2022.1.3.3 (HMPA 3.9.0.1391) on Win10 64bit and later + WinServer 2016 and later - Intercept X 2022.1.3.3 (HMPA 3.8.5.36) on W10 32bit/W8.1/W8/W7 + WinServer 2012/R2/2008R2

• Intercept X

Folder-based Ransomware Protection exclusion (Windows) cannot be applied to root drives (e.g. “C:\”)

None

• Core Agent

If a Microsoft Azure computer running Windows Server 2016 with a Mellanox network interface is started from the "Stopped (deallocated)" state, the Sophos Network Threat Protection service may get stuck in the start pending state. The service is pending a Windows Filtering Platform (WFP) call from the system which is not being returned when the system starts from a “Stopped (deallocated)” state, resulting in the issue.

This is an environmental/driver issue. No solution is available from Sophos Central Endpoint.

To prevent the issue on Windows Server 2016, avoid using the “Stopped (deallocated)” state when turning off the server. However, when the state has to be used, restart the server once again after it started from that state and is in the problematic state.

This issue only occurs on Windows Server 2016. In Windows Server 2019 and Windows Server 2022, starting the server from the “Stopped (deallocated)” state correctly returns the WFP call to the Sophos Network Threat Protection service, which allows the service to start correctly.

Please see KBA for additional information - https://support.sophos.com/support/s/article/KB-000044781

• Intercept X 2022.1.3.3 (HMPA 3.8.5.36) on "W10 32bit/W8.1/W8/W7" + "WinServer 2012/R2/2008R2"

• Intercept X

Browsing a website with Microsoft Edge on Windows 10 32-bit systems may result in error 0x80000001

Turn off Data Execution Prevention on Microsoft Edge for affected systems.

1. Sign in to Sophos Central.
2. Go to Overview > Endpoint Protection > Policies > Threat Protection Policy > Settings.
3. Click Add Exclusion (on the right of the page).
4. Under Exclusion Type, select Exploit Mitigation (Windows).
5. In the application list, select Microsoft Edge
6. Under Mitigations, turn off Data Execution Prevention.
7. Click Add.
8. Click Save.

• Core Agent

After upgrading servers to Core Agent 2022.2 Citrix User Profile Manager process may fail to delete users' temp profiles.

Possible symptoms:

i. user profile is not deleted automatically

ii. ongoing sessions (sessions not getting removed)

iii. some applications fail to launch halfway

Please raise a ticket with Sophos support with the reference https://sophos.atlassian.net/browse/WINEP-43577#icft=WINEP-43577/https://sophos.atlassian.net/browse/WINEP-43242#icft=WINEP-43242 and request to get the corresponding fix enabled.

• Core Agent

If Firefox is configured to use a WPAD for proxy configuration, it fails to browse.

Affects Core Agent 2.20.13 and above.

Use manual proxy configuration for Firefox. All other browsers handle WPAD fine.

• Core Agent 2022.3.0.56 (Win10 64bit and later) - Core Agent 2022.3.0.84 (WinServer 2016 and later) - Not planned to be fixed (W10 32bit/W8.1/W8/W7/WinServer 2012/R2/SBS 2011/2008R2)

• Core Agent

Some customers have reported Firefox having issues loading Gmail intermittently. This is due to a connection reset issue.

Applies to Core Agent version 2.20.13 and above. This has been improved in Core Agent 2022.2.1

In the Threat Protection policy, turn off Real-Time Scanning - Internet
In the Web Control policy, turn off Web Control

• Core Agent 2022.3.0.56 (Win10 64bit and later) - Core Agent 2022.3.0.84 (WinServer 2016 and later) - Not planned to be fixed (W10 32bit/W8.1/W8/W7/WinServer 2012/R2/SBS 2011/2008R2)

• Core Agent

Web browsing and download speeds are slower Web Control and / or Real-time scanning Internet in Threat Protection is enabled

Turn off Web Control policy
Turn off the settings under Real-time scanning Internet in Threat Protection

• Core Agent 2022.3.0.56 (Win10 64bit and later) - Core Agent 2022.3.0.84 (WinServer 2016 and later) - Not planned to be fixed (W10 32bit/W8.1/W8/W7/WinServer 2012/R2/SBS 2011/2008R2)

• Core Agent

With HTTPS/SSL scanning turned on, unable to cast to Chromecast devices.

Add website exclusion for both HTTPS and Threat protection website exclusion for the IP of the Chromecast device

• Core Agent 2022.3.0.56 (Win10 64bit and later) - Core Agent 2022.3.0.84 (WinServer 2016 and later) - Not planned to be fixed (W10 32bit/W8.1/W8/W7/WinServer 2012/R2/SBS 2011/2008R2)

• Core Agent

After the update to Windows Core Agent 2022.2.1.9 a BSOD may occur with the faulting module being - NETIO.sys

The issue is still under investigation, and improvements are expected in the next Core Agent version.

Please see KBA for workaround steps - https://support.sophos.com/support/s/article/KB-000044389

• Core Agent 2022.3.0.56 (Win10 64bit and later) - Core Agent 2022.3.0.84 (WinServer 2016 and later) - Not planned to be fixed (W10 32bit/W8.1/W8/W7/WinServer 2012/R2/SBS 2011/2008R2)

• Core Agent

When using Firefox and browsing a website (IE: Google) and clicking on different links quickly can generate an error: ERR_SSL_BAD_RECORD_MAC_ALERT

1. Close and re-launch Firefox
2. Turn off Web Control and Real-time scanning - Internet
3. Set "security.tls.enable_0rtt_data" = false on the about:config page for Firefox

• Intercept X

Systems running CryptoPro CSP software (http://www.cryptopro.ru) raise APCViolation alerts against random processes on the system (e.g. C:\Program Files (x86)\Sophos\AutoUpdate\Telemetry\SubmitTelem.exe).

Disable "Prevent APC violation" in the Threat Protection policy of the Endpoints that need to run CryptoPro CSP.

• Intercept X 2022.1.3.3

• Intercept X

Improved Ransomware Protection compatibility with 3rd party software eFlow.

Hotfix version 3.9.0.1222 can be applied as a workaround.
Check KB-000038477 for details and download.

Virtualization platforms (e.g. Red Hat KVM, Nutanix VM, Proxmox) running Red Hat VirtIO Ethernet Adapter Service with the default netkvm.sys driver (C:\Windows\system32\drivers\netkvm.sys from 11/08/2016) may show various types of intermittent networking issues when Sophos Network Threat Protection Service is running and the service may show as stuck in a starting state after rebooting the system.

Update the Red Hat VirtIO Ethernet Adapter drivers to the latest version.

• TBD (Win10 64bit and later) - TBD (WinServer 2016 and later) - TBD (W10 32bit/W8.1/W8/W7) - TBD (WinServer 2012/R2/2008R2)

• Intercept X

Folder-based Ransomware Protection exclusions that target a mapped network drive (e.g. X:\), do not apply.

Apply the latest Sophos Intercept X cumulative hotfix from KB-000038477 and change the mapped network drive exclusion to point towards the network location, using a wildcard for the server name. Example: If "X:\" is mapped to"\\server1\share2\folder3", update the folder-based ransomware exclusion to target "**\share2\folder3"

• Intercept X

ConnectWise Automate / LabTech Agent (LTAgent.exe) triggers Dynamic Shellcode mitigation on Servers running Intercept X with Exploit Mitigation and Dynamic Shellcode protection enabled. The ConnectWise Automate host server is unable to launch Automate Control Center as it relies on LTAgent.exe, which fails to launch.

Check KB-000044124 - Dynamic ShellCode Detection on ConnectWise Automate host server

• CM 2023.37

• Firmware Upgrade

The Schedule Firmware upgrade is getting triggered at incorrect time.

Firmware would be upgraded based on UTC offset rather than firewall timezone.

Please refer the KBA more details - https://support.sophos.com/support/s/article/KB-000045716?language=en_US

Please plan to schedule based on adding UTC offset on the firewall timezone,

For Example -1,

The firewall is in AEDT which is UTC + 11:00, The customer wants to schedule it for 6th October at 1:50 AM, The scheduling time can be 6th October at 1:50 am plus 11 hours, which is 6th October at 12:50 PM.

When the firewall upgrades, it will remove the offset and schedule it for 6th October at 1:50 am

For Example -2,

The firewall is in Asia/HongKong which is UTC+ 8:00, The customer wants to schedule it for 19th September at 19:35. The scheduling time can be 19th September at 19:35 plus 8 hours, which is 20th September at 3:35 AM.

When the firewall upgrades, it will remove the offset and schedule it for 19th September at 19:35.

• CM 2022.03

• UI (legacy)

Firewalls managed by Sophos Central without enabled IPS might get a message that enabling IPS worked though there is no valid Network protection license.

Get a valid Network Protection license

• CM 2.0 EAP1

• NoRelease

• Central Management

From SF v18.5 MR2, when FIPS mode is enabled, the device will reboot with factory reset. 

If the Firewall is registered and central services are accepted by the Central Admin and Admin Enables FIPS mode, the device will boot with factory reset config.

On Re-registration and Enable Central Management, Endpoint already known to the Central and Central Management API considers this as a Bad request as Central Services already approved.

There are two workarounds:

After factory reset, Remove the firewall from Central
After factory reset, register the device to Central and de-register it.
After performing any of the above steps, register the device again and now Admin will be able to Enable Central Services (CM/CR)

• CM 2.1 2020.50

• NoRelease

• Import-Export

Steps to recreate:

• Create WAF rule on base Firewall A from which you would want to import the configuration

• Create a group(Group 1) in Central with using config import option "Import existing configuration"

• Import the configuration from Firewall A

• Import would get successful and full sync would also pass if we add any other Firewall device(Firewall B) to this group

• Get onto "Manage Policy" page of that created Group 1.

• You will see "Loading" error on Firewall rules page

Expected Output:

"Loading" error should not show on Firewall rules page on Group, after importing WAF rule

Actual Output:

"Loading" error is there on Firewall rules page on Group, after importing WAF rule

• CM 2.2 2021.16

• SD-WAN

Supporting only bundle license in an SDWAN connection group.

Following bundles are supported:

• CENTRAL_ORCHESTRATION_TERM

• XSTREAM_PROTECTION_TERM

• XSTREAM_PROTECTION

• XSTREAM_PROTECTION_WAF_EMAIL

This bundles are not supported:

• Standard Protection

• Enhanced Support

If a bundle is not supported then the customer is not able to use SDWAN because the device will not appear in SDWAN.

• CM 2.2 2021.04

• UI

Firewall display issues seen in Central with more than 50 groups.
Firewalls in group randomly disappear while managing firewall in Central.
If you logout and log back in, or you un-collapse, navigate away and comeback, firewalls are all displayed okay. This is a pure UI issue with scrolling inside an expanded group.

Collapsing the group and expanding again will solve this issue.

• CM 2.1 2020.35

• Global Policies

Firewall rule reordering in Sophos Central Management group policy page is not supported.

 User can reorder the rule in XG Firewall. 

• CM 2019.30

• Dummy

If the available bandwidth is limited, Firmware upgrades for Sophos firewall devices might fail if triggered via Sophos Central -> login -> Open XG firewall through RP tunnel -> Backup and Firmware -> Upload Firmware

• iView 02.00 MR-2 (02.00.0.776)

• On Premise Reporting

Web surfing Reports as PDF with more than 200 entries is not possible. Creating a web surfing report you can only get an output from the first 200 entries in the iview.

This is applicable both iview1/iview2.

Reason: The reason for this would be that PDF generation with all the records will impact the performance of iview.

The only work around would be to generate the detailed report in Excel format. Excel would support upto 100000 entries.

It is expected behavior for Flex licensed customer accounts are not able to remove the Cloud Optix license

• To remove any usage so the customer is no longer billed, remove the environments in use (each environment section has a ‘remove’ set of instructions) https://doc.sophos.com/pcg/optix/help/en-us/AboutOptix/index.html

It is unexpected behavior seen when attempting to re-run the Partner Dashboard License wizard and check off the Optix component, you will get a generic ‘Update Failed’ pop-up error.

• This will be addressed in a future version of the Partner Dashboard (and remove the UI option to unselect it, as it is not possible).

It is not possible to remove the Optix section from a Flex-licensed Central Dashboard. It is only possible to remove usage so that there is no further billing

 In rare instances, customers may report that phishing threat campaign emails are detected as High Confidence Phish in M365 by the Anti-Spam policy and are quarantined.

 This is a known behavior with Microsoft (https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/secure-by-default?view=o365-worldwide ).

Shared mailboxes are not supported in the Outlook plugin.

The plugin is shown in OWA, but the functionality is incomplete. It is able to report campaign/non-campaign emails but it's not deleting the emails after submission.

Phish Threat currently uses the UTC timezone in all of its regions, there is also no logic defining the start of a work day. This means that there is a possibility that a Training reminder email is sent at 00:01 UTC on a Monday, which, depending on the timezone of the end-user, may be received during the day on a Sunday.

The very first reminder e-mail is sent as quick as possible to make sure users finish their training sooner than later. Every subsequent reminder email will follow the value selected in the frequency drop-down.

Taking Phish Threat Training via Smart Phones is not currently supported due to format supportability issue.

• 3.0 (2018.40)

• backend

If a user is deleted from the Phish Threat Dashboard but repopulate automatically after sometime, this is expected behaviour if a campaign was sent to the user within the last 30 days.
Both v1 and v2 report to Central the usage for the last 30 days, which is based on email addresses that were used as part of a campaign. When a reported email does not exist in Central, a user is created which is expected behaviour.

• 3.0 (2018.40)

• Campaigns

Creating and sending a Phish Threat Campaign without associated training material results in a 404 page being displayed when the enrollee clicks the link.

This allows a dry run of a campaign to be sent so that the admin can gauge how many of his employees are likely to need training. The admin should be able to check how many of the enrollees opened, and clicked on the email attack. But the enrollee should not see anything else, so they won't get suspicious when the new attack is sent.

• Legacy Support

• Legacy Support

• Customer Portal

The powershell script used to generate the macro within attachment attack documents is not working properly on Mac OS.

• 3.0 (2018.40)

• Campaigns

The following warning message might show up when clicking on a link within a Phish Threat campaign for G Suite customers with Central accounts in the East region giving users preemptive warnings:

Suspicious link: this link leads to an untrusted site. Are you sure you want to proceed to vk39fk6q.r.eu-west1.awstrack.me?

 Unfortunately a request cannot be made to delist from google as it requires proof of ownership. As the links are generated using Amazon services, we cannot supply this. A complete rehaul of Phish Threat will need to be made to change URLs for campaigns.

• v2.0

• Campaigns

Microsoft currently provides no effective way for us to monitor and remove domains/URLs from the Microsoft Defender SmartScreen list.

This means that the aforementioned feature is not compatible with our Phish Threat product.

• Campaigns
• Customer Portal

The "select all" functionality of the users selection fields in the "New Campaign creation - Enroll users" is limited to the first 40-50 users, unless the admin manually scrolls the user selection scroll box down to load the full user list into the browser and re-clicks the 'select all' function for adding/removing users to the campaign. 

• Campaigns

The normal workflow for Attachment Campaigns involves the fact that once the attachment has been opened, and the link inside of it activated, the user already failed the campaign - regardless of what's in the document.

Everything else about the Attachment Campaign should still work fine.

• Training

The following URLs are officially blocked in China.

https://sophos-phish-threat.go-vip.co/
https://staysafe.sophos.com

This means that training content will not work properly.

The only possible workaround would be for the affected users to use a tunnel-all VPN solution.

• Campaigns

When using AD sync with Phish Threat you cannot push out campaigns to sub-groups. The user must be a direct member of the group in order to receive the campaign.

• 3.0 (2018.40)

• Campaigns

If a campaign is created with large number of users then there are chances of page gets hang and campaign never gets completed.

Currently it is recommended to add less than 500 recipients at a time.
This will be improved in the future.

• 3.0 (2018.40)

• Campaigns

In rare instances customers may report when sending a training campaign they get presented with a "Oops, that page can't be found" error when clicking the training links.

The page may load after refreshing several times. Please wait and try the link again after some time.

This scenario can be seen during a web server refresh on the hosting server, normally it takes a couple of minutes to refresh all the training and landing pages - if the link was clicked during that specific refresh time the error will be received.

• WIFI Firmware 11.0.018

• Firmware

Roaming from one APX to another APX can cause 15 seconds of network disconnection for traffic between hosts connected to the same APX.
The issue happens if the source and destination devices are connected to the same APX.

• For example, if there is a VoIP connection being established between Notebook 1 and Notebook 2 at APX 1, traffic flow is normal.

• When Notebook 2 roams away from APX 1 and associates with APX 2, the VoIP connection will be disrupted for about 15 seconds.

• After 15 seconds have passed, the connection will work again.

Internet-bound connections and packets which need a next hop (XGS/XG) do not experience the same disruption in connectivity.

If both wireless clients connect to different Sophos APX access points this issue is not present.

• Sophos Connect 2.2

• Sophos Connect

Receiving a “Internet Explorer version earlier than 11 detected on this computer. Upgrade it to version 11 to continue.” error when trying to install Sophos Connect.

This can either show up if the OS where Sophos Connect is being installed doesn’t have IE installed, in which case it will not be able to install since Sophos Connect is tightly coupled with IE11 OR

because Sophos Connect was previously installed on the computer, and there are some issues in the registry preventing IE11 from being detected properly - in which case, the only known workaround for now in a complete fresh install of the workstation.

• Sophos Connect 2.1

• Sophos Connect

There are two cases where the IPSec connection downloaded via the provisioning file might not be updated once a change is made on the XG

1) The Sophos Connect Client has an active connection

2) The Sophos Connect client is not connected to XG when the XG policy is modified.

When the Sophos Connect client will try to connect to XG,  the connection will fail due to a policy mismatch error. The client will not automatically trigger a update policy request. The user has to manually trigger a "Update policy" request from the settings menu.

 This might happen with a greater probability if the allowed networks are changed in the policy. Also this will happen if a policy is changed from tunnel all to split network and the network list is not identical on both ends.

Trigger a "Update policy" to re-synchronize the policy

• Sophos Connect 2.1

• Sophos Connect

This relates to Sophos Connect Client configuration of the SFOS appliance using 3rd party signed certificate.

When using 3rd party signed certificate on the “remote side” of the configuration, and "ApplianceCertificate" on the local side, the connection will import fine and connect the first time. After reboot of the workstation or restart of the services related to Sophos Connect, an error message will pop up stating "Failed to validate server certificate" when trying to connect again.

Use a self-signed certificate, signed by the SFOS appliance on the “remote” side.

Use PSK instead of certificates.

• Sophos Connect

Sophos Connect for the time being only supports Ascii characters, no umlauts or UTF-8 or UTF-16.

• Sophos Connect 1.1

• Sophos Connect

Sophos Connect Client uses Port 60110 on the local host to communicate with the local webserver. If this port is used by some other service before Sophos Connect Client starts, then Sophos Connect Client will fail to start.

• Sophos Connect 2.1

• Sophos Connect

When both the IPsec and SSL VPN policy is configured on XG, the connect client will connect to the user portal and download both the policies on the end user computer. But ONLY the SSL VPN policy will have the option of "Update policy" in the settings menu. In order to trigger a policy update for IPsec policy, the user will have to trigger the same via the SSL VPN policy.

• Sophos Connect 2.1

• Sophos Connect

SSL VPN is not supported for Windows 7/8 in Sophos connect.

You may get the error "Openvpn service is not available" while connecting SSL VPN from Sophos connect.

As a workaround, you may use a legacy SSL VPN client.

Use a legacy SSL VPN client.

• Sophos Connect

Issue:

After deploying the Sophos Connect provisioning file on SC 2.1 the first authentication always fails when OTP is enabled.

 *Behavior:* 

The Client will use the OTP the first to connect to the User Portal. Then it has to use a new OTP, but the OTP is generated by the Sophos Authenticator and the user has to enter the new OTP after the first one rotates. The client does not wait for that to happen. Instead, it uses the same OTP and that will fail and the user is prompted for authentication again. So the user has to enter the credentials again and they should be connected to VPN. This is a known issue. **

Enter the credential and OTP again.

• Sophos Connect 1.1

• Sophos Connect

Sophos Connect is unable to import files containing UTF-8 / UTF-16 characters e.g.

• Sophos Connect 1.3 GA (1.3.65)

• Sophos Connect

This issue is occasionally seen mainly when the computer wakes up from sleep and the connection is set for Auto-connect and user is not on the domain network. The system recovers automatically so user intervention is not necessary.

• Sophos Connect 3.0

• Sophos Connect

-> Go to About page on Sophos Connect UI

-> Click Generate TSR buttong

tsr.zip file is downloaded to the default download location. Tried to unzip the zip file but not able to unzip on 10.12.6 Mac OS version. Tried it on Mac 10.13, zip opens up. 

• Sophos Connect 1.0

• Sophos Connect

If the DNS servers in the Sophos Connect Client policy on the XG firewall are changed while there is a VPN connection established, then the DNS Servers display on the Network Monitor page are not updated to the changed DNS servers.

Disconnect the existing connection and then re-establish it.

• SWG DNS 1.0 EAP

• SWG DNS 1.0 EAP (refresh)

• UI

When creating or editing a policy, on the location tab, the search function in the location selector is currently case-sensitive. If the user enters a search term in lower case, it will not match location names with the same letters but different cases.

Search the location with the exact string match.

• SWG DNS 1.0 EAP

• SWG DNS 1.0 EAP (refresh)

• UI

If user has created more than 20 domain lists with large names, and selects them all to be deleted in one action, the delete pop-up does not display the complete set of list names correctly.

No workaround available.

• SWG DNS 1.0 EAP

• SWG DNS 1.0 EAP (refresh)

• UI

On the policy Page, the 'Locations' column shows a sort control although is not, and should not be sortable.

No workaround available.

• SWG DNS 1.0 EAP

• SWG DNS 1.0 EAP (refresh)

• UI

When creating a domain list or a policy, any leading or trailing space characters are not stripped from name entered by the user. The system will successfully save policies or domain lists that appear to have the same name as existing ones, but which differ only by the spaces.

Create CDLs and Policies with trimming the leading and trailing whitespaces

• SWG DNS 1.0 EAP

• SWG DNS 1.0 EAP (refresh)

• UI

On the Policy page, and the Domains page, the delete button is always visibly active. It should be disabled until at least one Policy or Domain list has been selected for action by checking the boxes in the list.

No workaround available.

• SWG DNS 1.0 EAP

• SWG DNS 1.0 EAP (refresh)

• UI

When creating a new Policy, the 'Keep it clean' category settings apply by default. On the Settings tab, this should be visible in the drop-down control under 'Filtering by web category'. Currently, it does not show up until the user clicks on the drop-down control to activate it.

Click on dropdown to make the web category configuration visible

• SWG DNS 1.0 EAP

• SWG DNS 1.0 EAP (refresh)

• UI

On the Locations and Domains pages, hovering with the mouse over the number indicators in the 'Source' or 'Contents' columns displays a tooltip. The tooltip does not disappear as expected when moving the mouse away. This can result in multiple tooltips being displayed on top of of each other.

Click the mouse when hovering over from one row to another.

• Message History

Searchstrings in Textfields of the advanced search page (From, To, Subject) are treated as wordsearches within the string. Wildcards and Regular Expressions are not supported

E.g.

From: Sender@domain.tld

Possible Searchstrings

Sender

domain

tld

• none

• smart banner

Scenario: Emails from the backup-generating system are received in unreadable format if a smart banner is on.

This issue can be observed if there is an issue with the email content via the sender’s system.

i) If the content is a UTF-16 HTML document that is base64 encoded. But the ‘charset’ field in the tag is saying ‘UTF-8’.

ii) As per standard (https://www.w3.org/International/questions/qa-html-encoding-declarations#utf16 ), if using a UTF-16 HTML document, the document should begin with the UTF-16 BOM. If this is missing in the email content, it will create such an issue.

This needs to be fixed from the originating system.

• MFR

When connecting the primary domain in Mail Flow configuration, all the Emails of the Domain, as well as the Subdomains, start to flow through the Central Email due to the MailFlow Rules created by Sophos.

Two Workarounds:

1) Onboard the Subdomains along with the Primary domain for protection.

2) OR add the Subdomains in the Exception list of the MailFlow Rule created by Sophos

• Mail-flow

Sophos Email in mailflow mode cannot send outbound emails back to Microsoft 365 for further processing.  For the latest status on this, please review https://support.sophos.com/support/s/article/KB-000045035?language=en_US.

• 2017.35

• Postfix

Sophos Email Security doesn't create non-delivery reports (NDR) for emails going to valid mailboxes that it can't deliver to their final internal destination.

• none

• XGE

Scenario: An external domain emails a google group. The inbound email will be scanned and delivered to google. When email reaches the google group it will be forward to any external and internal email addresses. For the external email addresses that forward back to central as outbound email they will be block, because the sender of these emails is external.

Sophos Central email only supports the following

• We support: the sender is a customer address, the group contains internal and external recipients. The email is delivered to all group members.

• We don’t support: the sender is an external address, the group contains internal and external recipients. The email is only delivered to internal group members, not external ones.

• Policy configuration

In situations where customer has setup a Daily malware report to “Attach the report to the email” Sophos Central Email may detect the email as “Malicious URLs” cause the report contains Malicious URLs.

The work around is to configure the report to “Send a link to the report (secure)” instead of “Attach the report to the email”

The work around is to configure the report to “Send a link to the report (secure)” instead of “Attach the report to the email”

• Quarantine

Emails quarantined because of Data control violations can't be released because they don't appear in Quarantined Messages. You can see them in Message History, with the quarantine reason "Data control".

Please ask Sophos Support to release these emails.

• SPF_LOGS

Sophos Email Security only generates an SPF-Fail on a hard fail if the SPF-String is terminated with "-all".

SPF-Strings terminated with "~all" (note the tilde character) that don't match the senders IP address don't cause an SPF-Fail.

• Outbound Relay Control

Sophos Email Security doesn't send emails if there's an exclamation mark in the email address. It's rejected with "Relay access denied".

Remove the "

" character.

• Attachment Filtering

If an inbound email has attachments that use uuencoding, the attachments are removed. This is because messages with uuencoded attachments, and the attachments, are processed as text messages.

• Policy configuration

Emails with addresses containing the "!" character (exclamation mark) in the local part of the email address aren't supported, and are rejected.

For example: mailhost!username@example.org.

Remove the "

" character.

• 2019.15

• Self-Service Portal

A user has been given access to the Sophos Email SSP. They have mail in quarantine and the Emergency Inbox is turned on. But when using SSP the Quarantine and Emergency Inbox pages have no items.

This might happen when more than one user is assigned the same email address, and at least one of those users has no mailbox.

• In Sophos Central go to "People".

-Filter users by the email address of the affected user.

-Click each user to find the one that doesn't have a mailbox.

-Use "Delete User" to delete the user without a mailbox.

-Go to "People" and filter by the email address again.

-Select the user in question.

-Click "Email Setup Link" and select Sophos Central Self Service Welcome.

The user can then access the Self Service Portal using the instructions in their inbox.

• 2017.35

• Custom URL

The Sophos Email Security URL allow list can only contain up to 129 URLs.

• Quarantine

All mailboxes use the same language for the QS email. This can't be changed for individual mailboxes.

• 2020.32

• Outbound

The junk categorization isn't a result of the emails coming from Sophos Email Security, because other emails are succesfully delivered to inboxes of addresses on Microsoft-hosted domains, for example outlook.com.

Although Microsoft does not publicly share how it classifies email as junk, anecdotal evidence suggests that it learns from the recipient's actions. If customers' emails are repeatedly marked as junk by recipients in Microsoft-hosted email domains, then future customer emails might automatically be marked as junk.

Inform and educate customers sending emails to Microsoft-hosted domains to exercise caution with the type of emails they send, to prevent recipients from reporting emails as junk.

• 2020.38

• inbound

Reflexion has a Message Format Options feature which allows you to attach a control panel to the bottom of all incoming messages. This changes the content type of incoming emails to text/html and, if the control panel language is set to English, changes the character encoding to US-ASCII. If it's set to a different language, the character encoding used should match the selection.

Sophos Email Security doesn't have an equivalent feature so it doesn't change the content type and character encoding of incoming emails.

• Admin Quarantine

This happens if a user's account has been linked to a user without a mailbox.

Delete both the user account without a mailbox and the one with the mailbox. Then create a new user and mailbox.

If the email address was used under a different Sophos Central account, it should be removed there first. If you can't do this, raise a case with Sophos Support.

Note: Quarantine repositories and emergency inboxes are linked to user accounts via an ID. You can't remove an ID from these repositories and attach a different one.

• 2020.50

• Postfix

We constantly evaluate the TLS versions and ciphers we support. We accept versions and ciphers earlier than TLS 1.2 because a significant number of customers haven't upgraded.

We don't support PFS for TLS versions earlier than 1.2 because the ciphers available in TLS 1.0 and 1.1 that support PFS are unauthenticated. These ciphers use SHA1 on its own, or with MD5, and they're vulnerable to man-in-the-middle (MITM) attacks.

We recommend customers migrate to TLS v1.2 or later.

• 2021.13

• Quarantine

Sophos Email Security only sends quarantine summary emails to user mailboxes. We don't send them to mailboxes for distribution lists.

• 2021.19

• Quarantine

QS emails don't include messages quarantined because they failed impersonation or Date control rules.

• 2018.9

• Admin Quarantine

QS is empty, although a user received a quarantine summary email.

This can happen with Microsoft's Safe Links feature in Defender for Office 365. This feature clicks links in our notification emails to test them, which can remove the emails from quarantine.

• 2017.35

• Postfix

The "envelope from" and "data from" headers in outbound emails sent through Sophos Email Security must be in the same domain.

When using Google Workspace as an email service provider, if an outbound email is sent with an alias from a different domain, it won't be relayed outbound. This is because when sending as an alias in Google Workspace the "envelope from" header is the primary account.

For example domain1.com and domain2.com are both protected domains with valid mailboxes.

If the primary account email address is user@domain1.com and an email is sent from the alias alias@domain2.com, Google Workspace sends the email with the "envelope from" header as "user@domain1.com". But the "data from" header is alias@domain2.com.

This email is rejected as the "envelope from" and "data from" headers don't match.

Contact Google Workspace support to ask for the "envelope from" and "data from" headers to be matched for outbound emails, regardless of the alias used.

• DLP

If a Data control policy has the Certificates category selected, alerts are raised for .p7b files, even though the .p7b extension isn't in the Certificates category.

This is because Data control blocking uses True File Types and .p7b files share a file type with the .crt exception.

• 2020.05

• user level rate limit

If users send more emails than Sophos Email Security allows, emails are rejected. You see the following error:

NDR/bounce: 554 5.7.28 Mail flood detected.

Admin dashboard: Outbound sender rate limited for "user".

If senders regularly send high volumes of emails, for legitimate reasons, you can ask Sophos Support to classify the mailbox as a bulk sender.

Bulk senders have a higher sending limit than standard users.

• 2017.26

• Quarantine

The subject line of a message in the QS email is compressed to such a small column width, and the text is so small, that users can't easily read it.

Users should log into the Sophos Self Service Portal to check their quarantine summary messages.

• AD Sync

MSP customers can't use Azure AD Sync because of limitations with Azure AD Sync and non-email products. We'll try to resolve this.

• 2017.35

• Policy configuration

If an email arrives without an HTML body part, a smart banner isn't added.

Smart banners are applied if the following conditions are met:

Smart banners are turned on in the policy.

The email contains text/html content in the body.

• 2017.35

• DKIM

There is no industry standard for deciding if a DKIM (DomainKeys Identified Mail) check passes or fails.

To find out how Sophos applies DKIM checks, see Known Behavior of DKIM (DomainKeys Identified Mail).

• SFOS 20.0.0 EAP0-Build165 (20.0.0.165) [Taravai]

• SFOS 20.0.1 MR1 -BuildXYZ(20.0.1.xyz) [Amanu]

• Interface Management

The HA establishment fails if VLAN is used as a dedicated link over an unbound interface (parent interface).

Upgrade behavior: During firmware upgrade, the auxiliary device is upgraded first. After the upgrade, the auxiliary is unable to migrate the configuration, resulting in constant reboots. The primary node will be up during this stage, serving all the traffic.

• For a new HA configuration, the user can configure HA on VLAN over a bound (configured) interface as a dedicated link.

• For firmware migration, disable HA, configure HA on VLAN over a bound (configured) interface, and then migrate to v20.

• SFOS 20.0.0 GA-Build222 (20.0.0.222) [Makemo]

• Azure

SFOS on Azure Firmware upgrade to v20GA fails (results into just 1 NIC) if originally configured with 3 or more NIC

Customer when upgrades Azure SFOS instance on v20.0 GA firmware - if Azure deployment is configured with 3 or more NIC, there will be an outage after upgrading the firmware as only one NIC will be present after v20.0 GA upgrade.

Option-1) Need to re-purpose the deployment that works with 2 NIC on Azure.
Option-2) Continue running 19.5 MRx; the issue will be fixed in v20 MR1.

• SF 16.05 GA (16.05.0.117)

• Reporting

Only displayed result will be included while exporting data into HTML/ PDF / CSV

We can download current page records which is displayed on page through HTML/ PDF/CSV.

Example : Web report total pages 20. If current page 3 then we can download page 3 records through HTML /PDF /CSV.

We can download report which display on current page.

• SF 17.5 MR7 (17.5.7.511)
• SF 17.5 MR9 (17.5.9.577)

• Wireless

When pushing a separate zone WiFi out to a APX MESH network, mobile devices like Iphones and Androids fail to browse the internet from MESH nodes. The Root AP works correctly.

The device is able to ping the internet or any other device, but cannot make a connection with http or https sites

Setting the Separate zone interface to 1450 MTU may work as a workaround.

• SF 18.0 MR5-Build586 (18.0.5.586) [Samal]

• Email

Issue:

When the blocked senders list get large it can fail to add new entries. The exact number of entries will very as it depends on the length of each email address. We have seen issues when lists get over 2400.

Users will see warning message saying The operation will take time to complete. The status can be viewed from the "Log viewer" page

Checking csc.log will show a line like this

“2021-06-02 11:40:21,411:ERROR:CSC - Exception in getStatusFromResponse() :java.lang.NumberFormatException: For input string: ""java.lang.NumberFormatException: For input string: ""

Replace duplicate entries with wild cards to reduce the number on the blocklist where possible. Entries like smith@domain1 and joe@domain1 can be reduced to entries like *@domain1, which will cover a wider range of addresses anyway.

• SFOS 19.0.0 GA-Build317 (19.0.0.317) [Tupai]

• NoRelease

• Clientless Access

Starting with version 19, Sophos Firewall includes several security improvements to prevent attackers from accessing sensitive information. One of these changes is an upgrade to the RDP component to the latest version, which helps to improve overall security. However, this new component library does have a minor behavior difference: in versions 19 and later, the cursor is displayed as a cross instead of an arrow.

• SFOS 19.0.1 MR1-Rebuild-Build365 (19.0.1.365) [Akamaru]

• Logging Framework

/conf partition on the appliance gradually filling up if On box reports of appliance is disabled/off. While conf partition gets 100% unable to login to GUI.

Issue will be resolved in 19.0.2 MR 2 and 19.5 GA

If on box reports are off, Need to turn on On-box reporting from console.

console> set on-box-reports on

• SFOS 19.0.1 MR1-Rebuild-Build365 (19.0.1.365) [Akamaru]

• SecurityHeartbeat

Heartbeat alerts are received on Sophos Central from firewall stating that there are “missing heartbeats” when the endpoint systems are in Modern standby mode.

Modern Standby is a state wherein the display of device turns off, however the internal components may stay remain on.

Since the system is in standby the heartbeat service is not sending information to firewall , hence the firewall is blocking the traffic.

Endpoints with Modern standby enabled is not supported in firewall and so missing heartbeat alerts could be caused.

Heartbeatd.log gives error like below:

[2023-05-30 13:09:07.953Z] TRACE IpsAdapter.cpp[5125]:48 sendData - sessionid not found.

[2023-05-30 13:09:07.953Z] TRACE IpsSender.cpp[5125]:30 sendData - sendData failed (errno=2), entry in resend list created.

• The issue happens when machine is entering modern standby mode which can be identified from SDU logs under LOGS\ProgramData\Sophos\Sophos Network Threat Protection\Logs\sntpservice.log

2023-06-01T09:43:06.681Z [ 5664: 8608] A Inactive Interfaces changed.
2023-06-01T11:04:03.513Z [ 5664: 5668] A Received Screen Off notification: Endpoint entering Modern Standby
2023-06-01T11:04:04.938Z [ 5664: 5668] A Console Disconnect for: domain\username
2023-06-01T12:06:20.781Z [ 5664: 5668] A Received Screen On notification: Endpoint exiting Modern Standby
2023-06-01T12:06:26.891Z [ 5664: 5668] A Console Connect for: domain\username

• Since the system is in standby the heartbeat service is not sending information to firewall , hence the firewall is blocking the traffic

• Endpoints with Modern standby enabled is not supported in firewall and so missing heartbeat alerts could be caused.

Disable Modern standby (AKA connected Standby) on the endpoint side:

Suggested links :

https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/modern-standby

https://binaryfork.com/disable-connected-standby-7953/

https://binaryfork.com/disable-connected-standby-7953/#how-to-disable-connected-standby-with-a-registry-key

https://learn.microsoft.com/en-us/windows/iot-core/learn-about-hardware/wakeontouch#disabling-modern-standby

• SFOS 18.5.1 MR1-GA-Build326 (18.5.1.326) [Cuba]

• SecurityHeartbeat

Customers may face an issue related to the Sophos central registration due to an Amazon certificate not being present in /conf/ directory and gets an error similar to this-

32021-11-25 17:28:36 WARN API.pm[13476]:119 SFOS::Common::Central::API::send_request - 500 Can't connect to dzr-utm-amzn-eu-west-1-9af7.upe.p.hmr.sophos.com:443 (certificate verify failed)

Details here: https://support.sophos.com/support/s/article/KB-000043494?language=en_US

Check if an amazon cert is present. Use this command-

openssl crl2pkcs7 -nocrl -certfile /conf/certificate/internalcas/cloud-ca.crt | openssl pkcs7 -print_certs -text -noout | grep Issuer
If Amazon CA not existing do the following-

mount -o rw,remount /
cp "/conf/certificate/internalcas/cloud-ca.crt" "/conf/certificate/internalcas/cloud-ca.crt.org"
cp "/_conf/certificate/internalcas/cloud-ca.crt" "/conf/certificate/internalcas/cloud-ca.crt"
mount -o remount,ro /

Note: No downtime is required for any of the above steps.

• SFOS 19.5.0 EAP0-Build93 (19.5.0.93) [Taha]

• SFOS 19.5.1 MR1-Build278 (19.5.1.278) [Hatutu]

• SDWAN Routing

Traffic does not pass to the correct gateway if a combination with SDWAN Profile and Gateway based SDWAN routes are being used.

Update the affected SDWAN route to solve this issue
Or
Use only the Gateway based SDWAN route

• SFOS 19.0.2 MR2-Build472 (19.0.2.472) [Kamaka]

• SSLVPN

Description

SSLVPN User still shows in the live user list after disconnection from the client when connecting using UDP 

Configs on SFOS: 

• SSLVPN Global settings are configured with Protocol as UDP

• Create a user, and add it under the SSL VPN profile

• Download the SSLVPN configuration from the user portal and use it on remote access client

• Initiate the connection and the connection will be successful.

• Disconnect the tunnel from the remote access client

• The client will disconnect from the connect client application but it will still appear under the Current activities → Live user list

Use a TCP-based SSLVPN RA connection, Which will immediately disconnect the user from the live user list

• SFOS 19.0.1 MR1-Rebuild-Build365 (19.0.1.365) [Akamaru]

• NoRelease

• SSLVPN

This issue is seen if the sslvpn ra tunnel type is of UDP only, not applicable to TCP type. Issue is applicable to SFOS running v19.0.MR1 or later. 

Configs on SFOS: 

• SSLVPN Globalsettings is configured with Protocol as UDP and ‘Use static IP addresses’ checkbox enabled. 

• Create a user, assign with SSLVPN static ip from the IPv4 address range set the in SSLVPN global settings.  

• Enable user portal login on Admin->device settings.

• Download SSLVPN configuration from the user portal and use it on remote access client

• Initiate the connection and the connection will be successful.

• Disconnect the tunnel from remote access client and connect again; the tunnel will not be established with the reason AUTH_FAILED (in /log/sslvpn.log) and also UI logviewer says ‘User failed to login to SSLVPN through Local authentication mechanism because of ip lease failed’

• Set the value of 'Disconnect dead peer after' in SSLVPN global settings to minimum amount of time, say 60 seconds; so that after 120 seconds (twice the value set in dead peer ) SSLVPN RA tunnel bring up from remote access client will be successful

• Or use TCP based SSLVPN RA connection.

• SFOS 19.5.0 GA-Build197 (19.5.0.197) [Anaa]

• SFOS 20.0.0 EAP0-Build165 (20.0.0.165) [Taravai]
• SFOS 19.5.3 MR3-Build652 (19.5.3.652) [Katiu]

• WWAN

Admin is unable to connect the Sierra-Aircard modem when upgrading to v19.5-GA or higher.

No workaround is available. Pre-fix can be made available by contacting the Sophos Support.

• SFOS 19.0.2 MR2-Build472 (19.0.2.472) [Kamaka]

• IPsec

The traffic fails when compression is enabled for v4inv6 IPSec tunnel. The issue is seen on all XGS platforms and is consistently reproducible.

With ipsec-acceleration disabled on both the DUTs, traffic runs fine with compression enabled, in v4inv4 IPSec tunnel.

STEPS TO REPRODUCE-

Disable ipsec-acceleration, traffic runs fine with compression enabled in v4inv4 IPSec tunnel.

• SFOS 19.0.0 EAP0-Build190 (19.0.0.190) [Tahiti]

• NoRelease

• Clientless Access

In v19 and later, there have been several security improvements in Sophos Firewall to prevent attackers from getting hold of sensitive information. One of the changes we did was upgrading the RDP component to the latest version to improve the overall security posture. The clipboard functionality is not directly compatible with the latest RDP components making it non-supported with versions 19 and later. 

• SFOS 19.5.0 GA-Build197 (19.5.0.197) [Anaa]

• SFOS 19.5.2 MR2-Build624 (19.5.2.624) [Hitra]

• Wireless

There is an issue reported by customers that after upgrading to V19.5 GA separate zone wireless network stopped working and wireless clients are unable to access the Internet. In this case, the wireless interface shows unplugged.

Workaround 1.

Remove and re-add the affected separate zone SSID from AP/APX.

Workaround 2.

Restart the awed(This will disconnect all connected AP/APX(s) and connect back).

service service awed:restart -ds nosync

• Authentication Clients

An issue was found where the existing version of the Sophos Network Agent is using an older version of the Google API’s. This prevents the Sophos Network Agent from being downloadable for devices running the latest version of the Android OS. The Sophos Network Agent will continue to function on devices running the older version of Android OS.

• SF 17.5 MR5 (17.5.5.433)

• Reporting

In an HA configuration pair, with a scheduled report configured, the auxiliary unit will also generate a report containing data about emails being sent from the unit. These emails being sent as per the attached report, from the auxiliary unit is the report itself.

There is no workaround.

• SFOS 19.0.2 MR2-Build472 (19.0.2.472) [Kamaka]
• SFOS 19.5.1 MR1-Build278 (19.5.1.278) [Hatutu]

• SFOS 19.0.3 MR3-Build517 (19.0.3.517) [Kaual]
• SFOS 20.0.0 EAP0-Build165 (20.0.0.165) [Taravai]
• SFOS 19.5.2 MR2-Build624 (19.5.2.624) [Hitra]

• HA

Admin is unable to update or create HA when the bridge interface is configured in the Peer Administrator setting.

Need to remove the bridge interface from the Peer Administrator setting in the HA config.

• SFOS 19.5.0 GA-Build197 (19.5.0.197) [Anaa]

• Logging Framework

Once we tick select “All” option , tick mark will be disappeared and all individual modules / components will be enabled.

Current behaviour of “All” button is since inception as short cut to select all the relevant component. The result of actions is transferred to individual buttons and stored in backend as separate status for each component. As it is only UI action button and not the summary of status all button - it is expected behaviour.

• SFOS 19.5.0 GA-Build197 (19.5.0.197) [Anaa]

• Firewall

The NAT information for Source NAT gets updated for existing connection (re-route) when the failover occurs on IPsec tunnel.

Currently for re-route of existing connection Source NAT information isn’t updated as NAT occurs only when new connection is initiated. ( Known behaviour ) NAT id and Source NAT information doesn’t change when re-route occurs.

For ICMP traffic, the ongoing traffic should be terminated first then wait for 30 seconds to delete/destroy the ICMP conntrack. New ICMP traffic will be forwarded via updated NAT ID.

NAT ID will not be changed for on-going connection during the re-routing.

For TCP: NAT ID will be applied on new connection
For ICMP: Need to terminate the ongoing requests, wait till 30 seconds and reinitiate the ICMP traffic

• SF 18.0 MR1-1 (18.0.1.396)

• WAF

If a file is uploaded which is larger then the limit then message similar to this is visible in the log: 

[Fri Aug 14 15:41:22.414802 2020] [security2:error] [pid 14238:tid 140229323249408] [client 109.91.34.26:44831] [client 109.91.34.26] ModSecurity: Request body no files data length is larger than the configured limit (q).. Deny with code (413) ….

For a workaround please contact support.

• SF 17.5 MR9 (17.5.9.577)

• Firewall

When utilizing the XG Email protection module in MTA mode, this creates an automatic firewall rule for the SMTP traffic at the top of the policy list. If additional rules are created above this rule, this can result in the XG accepting SMTP traffic but then being unable to deliver the mail onto the next hop. This can be seen by the mail queuing on the appliance and time out errors in the /log/smtpd_main.log:

2369   == john.doe@example.com R=default_mx_router T=remote_smtp defer (110): Connection timed out
2020-02-07 10:57:39.081 [2369] xPlIal-cb3y0D-DL == john.doe@example.de R=default_mx_router T=remote_smtp defer (110): Connection timed out

This can occur with:

• Manually configured firewall rules that include the SMTP service

• Automatically created firewall rules when configuring a VPN tunnel

 We plan to improve on this behaviour in an upcoming software release

Ensure that any manually created firewall rules are created below the automatic MTA rule
Ensure that any subsequent automatically created rules are moved below the automatic MTA rule

In the event that mail has already become queued on the appliance prior to the moving of the above rules, contact support for assistance in utilizing the /scripts/mail/replace_firewall_id.pl script to rectify the issue.

• SFOS 19.0.1 MR1-Rebuild-Build365 (19.0.1.365) [Akamaru]

• Authentication

The accounting of processed traffic is run every three minutes. A user may exceed his quota by using more bandwidth than his quota allows between accounting runs.

There is no workaround

• SFOS 19.5.0 GA-Build197 (19.5.0.197) [Anaa]

• HA

Steps To Recreate:

Not able to establish Quick HA if one of the appliances has a bridge interface as an admin port

If both the appliance have the same logical interface which is selected as "Peer administration settings" then it will work

• SFOS 19.5.0 GA-Build197 (19.5.0.197) [Anaa]

• Dynamic Routing (OSPF)

OSPF does not propagate /32 network configuration of P-t-P interfaces e.g. PPTP, L2TP, PPPoE and GRE.

1. Redistribute Connected
2. Add static route for tunnel/desired interface network and redistribute static route in ospf

• SF 17.5 GA (17.5.0.310)

• SNMP

SNMP query for supportSubStatus and appExpiryDate return unexpected values. 

MIB indicates that supportsubstatus should be 1 or 2, but 3 is returned.
MIB indicates that  appExpiryDate should be a date but the value returned is invalid

This will be resolved in the upcoming XG v18 release

• SF 17.5 MR8 (17.5.8.539)

• Hardware

Sophos 40Gbit QSFP+ Flexiport module is not recognized at all in SG/XG 430/450 due to power sequence issues. A fix is in progress.

No Workaround

• SFOS 19.0.0 GA-Build317 (19.0.0.317) [Tupai]

• NoRelease

• XGS BSP

Issue: XGS 10G interface is not working when interface speed is set to Auto-negotiation (Physical or LAG)

Affected Product: Only XGS hardware with 10G interface

Set interface speed to Manual 10000 Mbps - Full-Duplex (Applicable for Physical, LAG interfaces).

• SFOS 19.0.0 GA-Build317 (19.0.0.317) [Tupai]

• Logging Framework

If your device is using a configuration previously restored from a Cyberoam backup, and you have NOT regenerated the appliance certificate on SFOS, upgrading to SFOS v19 will result in operation in fail safe mode.

The appliance certificate generated in cyberoam devices uses a weak signature algorithm (MD5) that is NOT supported for appliance certificates in SFOS v19.

How to verify before upgrading:

Check the Signature Algorithm of the Appliance certificate by running the following command on the advanced shell:

              “openssl x509 -in /conf/certificate/ApplianceCertificate.pem -text -noout” 

If the output shows the signature algorithm as "md5WithRSAEncryption", DO NOT upgrade to v19.

Please refer the KBA: https://support.sophos.com/support/s/article/KB-000044122?language=en_US

• SF 18.0 MR5-Build586 (18.0.5.586) [Samal]

• Firewall

Situation:

The traffic from the terminal Server is not being marked by the User ID as a result that the correct firewall rule is not being applied.

Customer need to join the EAP for New Server Protection Features and confirm the machine is added to the EAP.

Details here: https://support.sophos.com/support/s/article/KB-000038634?language=en_US

Customer need to join the EAP for New Server Protection Features and confirm the machine is add to the EAP

• SFOS 19.0.0 GA-Build317 (19.0.0.317) [Tupai]

• Core Utils

UTF-8 character in backup file name causes issue of user unable to download the backup file.

Nothing happens when the user tries to download the backup file with file name contain UTF8 characters.

We do not have any workaround or solution at the moment, Please do not use UTF-8 characters for the backup filename.

• Core Utils

There is an issue with XGS 116 r1, 116Wr1, 116r2 & 116Wr2 units related to default power settings for the PoE Port.

The default PoE power setting on this models should be AT(30W). But instead the units in the field are running with default PoE power setting as AF(15W). Also there is no mechanism right now in xgs-poe utility for this models to increase the power setting from AF to AT.

This issue is being fixed in SFOS 19.0.2 MR2, 19.5 MR1. Customer when upgrading the units to this version, its default PoE power setting will be set to AT(30). Then customer can also change PoE power from AF to AT & vice-versa using the xgs-poe utility.

• SFOS 18.5.0 GA-Build264 (18.5.0.264) [Antigua]

• SFOS 19.5.0 GA-Build197 (19.5.0.197) [Anaa]

• Licensing

Situation:

•  Partner/customer is unable to activate any evaluation license by initiating it from the XGS unit under “System” → ”Administration” → “Licensing” → “Activate evaluations”

Activate eval license in "My Sophos" portal

• SF 17.5 MR16-Build830 (17.5.16.830) [Timor]

• Web

Issue:
When using the Web Proxy, there are files that are stored in /tmp as they are virus scanned. If Web Caching is turned on (Webadmin → Web → General settings → Enable web content cache) the /tmp directory might run out of space.

Determining if the system is affected by this issue:
df -h /tmp
If the availble space is 0MB

du -c /tmp/0x1*
Non-zero length files can take up a significant portion of the partition.
Note: large numbers of files that are zero length are not an issue.

Impact:
When the /tmp partition is full several parts of the system suffer, webadmin is no longer accessible, and the box needs to be rebooted to recover.

Either disable web content caching: Go to Web > General settings > Enable web content. Disable the option. Note that this option is disabled by default.
or reboot the system

• SFOS 19.0.1 MR1-1-Build384 (19.0.1.384) [Aukena]

To enable NAT or WAF through web admin, you must specify an Original Destination Port (NAT) or Hosted Address (WAF). This is normally set to the IP addressed associated with ‘Port B’ which is the WAN Port.

For CM managed autoscaling instances, there’s no way to identify the original destination as each firewall will have it’s own IP address for the WAN port. This makes it impossible to setup DNAT for a CM managed instance. Even if someone creates a “Dynamic Interface”, it is not available during the “Public IP Address” step.

The "Server access assistant (DNAT)" cannot be used to configure DNAT but the manual method of creating a "New NAT rule" can still work. As the WAN Interface isn't available, you can create an IP range that will be translated to the private IP of the private Server. To setup DNAT:

1. Navigate to "Firewalls" under "Manage Firewalls" in the left sidebar
2. Select the three dots for the firewall group and click "Manage Policy".
3. On the left sidebar, select "Rules and Policies" and go to the NAT sub page
4. Click on the "Add NAT Rule" button and select "New NAT Rule"
5. Enter appropriate settings for your application. Ensure the "Original Destination" is set to "Any" and "Inbound Interface" to "Any" as well.
6. For the "Translated Source", set it to MASQ.
7. Change the "Translated Destination (DNAT)" to the private IPs of private server/load balancer by clicking "Create new" at top of drop down menu and creating appropriate destination.
8. Click Save.
9. Wait for configuration to be distributed to all XG's in group. This can be monitored from the "Firewalls" page

• DHCP

Configuring multiple DHCP Relays where the 'listening' interface in one corresponds to the interface that the DHCP server is connected to in another of the configured relays will cause one of the relays to cease to function.

This is not a supported scenario and is expected behaviour. A DHCP Relay should not be setup on an interface that hosts a DHCP server.

• SFOS 19.0.0 GA-Build317 (19.0.0.317) [Tupai]

• Wireless

When using RadiusSSO and roaming between APX’s the client has to reauthenticate in order to connect again.

This is a limitation with the current deployment. RadiusSSO currently cannot handle roaming between access points

• SFOS 18.5.2 MR2-Build380 (18.5.2.380) [Dominica.NFM]

• IPsec

The issue is happening when Sophos Firewall is configured Sophos IPsec connect with Local ID. This configuration is not supported by IOS.

The IOS profile does not support any parameters with Local ID/Remote ID and which causes a failure to authenticate the connection.

Clear the Local ID value/Field and re-download the configuration file.

• SFOS 19.0.0 EAP0-Build190 (19.0.0.190) [Tahiti]

• SFOS 19.0.0 EAP1-Build244 (19.0.0.244) [Tahiti]

• Email

If a customer restores a Cyberoam backup which does not have Default CA certificate generated or configured, then after restoring the backup in v19 EAP0 or later, awarrensmtp & warren services will be found DEAD.

After restoring the cyberoam backup, regenerate the Default CA certificate

• Login to UI and go to System -->Certificates -->Certificate Authorities --> Edit Default CA

• Reboot the device

• SF 16.05 MR8 (16.05.8.320)
• SF 17.0 MR1 (17.0.1.98)

• Date/Time Zone

GUI time differs from the CLI time

The files /conf/TZ and /etc/zoneinfo/ are not in sync.

1. Copied content from /etc/zoneinfo/ to /conf/TZ
2. Restart the appliance to take change into effect

• SF 17.5 MR5 (17.5.5.433)

When scanning an encrypted split archive with Avira, there is the following limitation:

1) If an encrypted split file was scanned, only the first part contains all information about the archive (includes also the encrypted flag)
2) That's the reason why SAVAPI returns only by scanning the first part, that the file is encrypted. Because the engine/avpack can "unpack" the file, but a password is needed to extract it. So the archive was valid.
3) If the following parts (except the last one) are scanned, then the encrypted flag is missing, that's the reason why SAVAPI returns clean for that part of multipart file.
4) If the last part of the archive was scanned, then Archive is corrupt for SAVAPI, because the other parts are missing.

Additional information: Also a unpacker will not ask for a password when try to extract an encrypted split file not by using the first part of that file. The unpacker will return, its not a archive.

Use Sophos AV

• SF 17.5 MR3 (17.5.3.372)

• Hardware

When the user configures HA on XG105r3, XG115r3, XG106r1 shared port (Port4), the HA pair becomes unstable. After the enablement of HA service, Auxilary rebooted first as usual. But the Primary appliance goes in the rebooting phase because of the shared port which takes more time to wake up.

Do not to use the shared port (Port 4) as HA dedicated link.

• SFOS 18.5.2 MR2-Build380 (18.5.2.380) [Dominica.NFM]

• SecurityHeartbeat

The backup will not be restored if there is an error with the database tblappstoeps as it may contain invalid byte sequence for encoding "UTF8"

Logs will be seen in Postgres.log

772 2022-01-08 03:01:18.064 GMTERROR:  invalid byte sequence for encoding "UTF8": 0xb1
6772 2022-01-08 03:01:18.064 GMTCONTEXT:  COPY tblappstoeps, line 23612
6772 2022-01-08 03:01:18.064 GMTSTATEMENT:  COPY tblappstoeps (app_id, uuid, app_path, occurrence, last_seen) FROM stdin;

Please contact Support for a workaround.

• SFOS 18.5.2 MR2-Build380 (18.5.2.380) [Dominica.NFM]
• SFOS 19.0.0 EAP2-Build271 (19.0.0.271) [BoraBora]

• Network Utils

• The interface display name starting from “port” or “eth” or “ge“ are not allowed.

• The restriction was added for add/edit interface only.  

This is an intentional change and customers will not be able to edit/change interface names starting with “port”, “eth” and “ge”.

• SFOS 18.5.2 MR2-Build380 (18.5.2.380) [Dominica.NFM]

• API Framework

If no , or tag is used after no status will be there in response.

Always use one of these tags after the to get detailed status code messages.

• NoRelease

The LogViewer can’t log values where bytes values are greater than 32 bit. and reporting is unable to store value, due to which there is a drastic difference between SF reports and CFR reports. In case the number of bytes transferred exceeds the limit which can be accommodated in U32, then it shows the truncated value in the log viewer.

• SFOS 18.5.2 MR2-Build380 (18.5.2.380) [Dominica.NFM]

• L2TP

We can not connect multiple L2TP connections behind the same NAT'd device.

Example:-
There are 2 Windows clients behind a NAT'ed device over which the clients are connecting to XG using L2TPoIPSec. The tunnels are established fine, but there is an issue with the traffic. Say ping traffic from Windows1 is working for some seconds and then dropped and Windows2 will not see ping response while ping is working from Windows1 and vice-versa.

• SFOS 18.5.1 MR1-GA-Build326 (18.5.1.326) [Cuba]

• Licensing

Behavior observed:

SFOS gets stuck after a reboot as hyperthreading enabled on hardware blocked the kernel to boot

The issue will only happen when the SFOS RAM/CPUs are lesser than purchased in the license and hyperthreading is enabled on Dell hardware. SFOS was not able to apply RAM and CPU limit on that hardware if hyperthreading is enabled.

This will block the kernel to boot.

The issue is observed on SFOS v18.5 MR1 Build 326 installed on Dell R330 hardware.

Disable hyperthreading on the server.

• SFOS 18.5.1 MR1-1-Build365 (18.5.1.365) [Cuba.ODM]

• Config Migration Framework

*Reported Issue:*Upgrading from v18MR6 to v18.5MR1 results in factory default configuration being applied to the device.
Workaround: Downgrade back to previous firmware and upgrade to v18.5MR2. Alternatively you can upgrade to v18.5GA and then v18.5MR1.

Downgrade back to previous firmware and upgrade to v18.5MR2. Alternatively you can upgrade to v18.5GA and then v18.5MR1.

• SF 15.01.0 MR3 (15.01.0.447)

• Reporting

In Auxiliary appliance if the report don't contain any data then we don't send any report notification to customer. This is intended behavior.

• SecurityHeartbeat

In 18.5 MR2 we have introduced key encryption for the certificate on FW used by endpoints to heartbeat with firewall. During the upgrade to 18.5 MR2 a certificate refresh has to be done as key has to be encrypted. And this certificate need to be made available to endpoints. If endpoints are unable to get the new certificate from Central, then heartbeat will start failing. This might happen when private DNS Servers are being used.

To avoid this ensure that the endpoints have network connectivity during the upgrade. Also disable the checkbox “Block clients with no heartbeat" in the firewall rule in case endpoints need access to the internal DNS server to get updates (new certificate) from Central.

If the system is showing missing heartbeat after the upgrade:
Ensure endpoints has network connectivity so that endpoints can fetch new certifcate from Central. Also disable the checkbox "Block clients with no heartbeat" in the firewall rule in case internal DNS resolution fails.

• SF 18.0 MR5-Build586 (18.0.5.586) [Samal]

• Hotspot

Situation:

When downloading the voucher from the user portal, then the WLAN password is not printed on hotspot vouchers for the types: bridge to AP LAN and bridge to AP VLAN.

The wireless password is only printed on hotspot vouchers for the interface link of "Separate Zone interface(bridge) of Wireless Protection." 

It is known behavior that a hotspot voucher doesn't contain the WLAN password for Bridge to AP LAN and bridge to AP VLAN.

Configure Hotspot voucher for interface link type 21 i.e. "Separate Zone interface(bridge) of Wireless Protection".

• Auth Client macOS 2.1.0

• Authentication Clients

Issue description :

When MAC books comes up from the Sleep mode its takes 2-3 minutes for the user to be able to browse the internet .

This happens only incase we have a User based firewall rule . It takes CAA around 2-3 minutes to authenticate the user .

Workaround :

The user can disconnect and reconnect the client .

Disconnect the CAA , Reconnect

• SF 17.5 MR14-1 (17.5.14.714)
• SF 18.0 MR4-KONICA (18.0.4.519) [Palawan]

• Hardware

Issue :

The 4x10G FlexiPort Modules are not being recognized on Sophos Firewall, the interfaces are being detected as "eth0,eth3"
The 4x10G Flexi modules are not being recognized correctly, the interfaces are being detected as "eth0,eth3".
The modules cannot be detected correctly and hence making them unusable with the Sophos Firewall.

Only SFOS (Sophos Firewall is affected )

Affected Sophos Part Number – “XGMOD410PUR”
Description: 4 ports 10G SFP+ without bypass
Affected Part S/N Prefix – “M2400XXXXXXXXXX” (with NVM FW 7.20)
Note: Module with same prefix “M2400” with NVM 5.05 doesn’t have this issue.
To Identify the affected module NVM FW 7.20: Run ethtool -I

• SF 18.0 MR1-1 (18.0.1.396)

• VFP-Firewall

If the firewall-acceleration is changed on the cli the link state of the affected ports will bounce.

• SF 15.01.0 MR1.1 (15.01.0.407)

• Firewall

STAS is not working if the AD server is only reachable over a WAN conneciton.

• SF 18.0 EAP3-refresh1 (18.0.0.285)

• NoRelease

• Logging Framework

LogViewer shows twice DDNS events for Success/Failure.

• SF 18.0 MR3 (18.0.3.457) [Mindoro]

• Authentication

*Issue:* 

If there is a high number of Radius SSO users logging in at the same time and the firewall reboots then sometimes this may result in web admin is not being reachable after the reboot.
LAN users can connect and the device is accessible via ssh.

• SF 18.0 MR1-1 (18.0.1.396)

• DHCP

Description:

There is a requirement in certain case's where a multiple IP addresses would need to be assigned for a MAC address from different scopes .

One of the use case is that or the captive portal to work over the bridged interface with a vlan , the AP creates a virtual interface and needs an IP address from the VLAN .
When captive portal , a virtual interface is created on the AP , which asks for an IP over a vlan , since this is a briged to vlan set-up , and the discover request come's with the MAC address of the interface .

If one scope is set to static and other to dynamic , the IP assignment doesn't work .

Solution :

Set both the scopes to dynamic .

Set both the scopes to Static .

• SF 17.5 MR8 (17.5.8.539)

• Web

Web policy rules do not support users with a backslash in the name.

Example:  in webadmin -> Authentication -> users :

Creating a user with username a\b and saving it will succeed.

Using this user in a web policy wont work.

Create a username without backslash or single quote

• STAS

*Question:*  

Do we support Secure LDAP port 636 in the Novel eDirectory configuration of STAS?

Answer:

Secure LDAP port 636 is not supported in the Novel eDirectory configuration of STAS.

• SF 18.0 MR4 (18.0.4.506) [Palawan]

• CM (Join to Cloud)

Registering XG with Central Manager for remote management functionality fails with error "Temporary error while accessing Sophos Central, please try again".

Root Cause:
This error could occur due to many reasons, however for this particular issue, the email address being used for registration is longer than 50 characters.

Shorten email address and try again. If you have tried more than 5 times in the last 1hr, the account will be blocked for up to 5 hours. Please wait and try again.

• STAS 2.5.1.0

• STAS

STAS Users are getting disconnected frequently if dead entry timeout configured other than zero.

Dead Entry Timeout does not work and it MUST be set to zero. If the value for the dead entry timeout is configured anything other than zero then such behavior encountered and users may get disconnected randomly.

Need to set the dead entry timeout to zero to avoid user disconnection due to dead entry timeout. It is recommended to use the WMI mechanism in STAS for log-off detection.

• SF 17.0 GA (17.0.0.80)

• Licensing

Unable to activate or register the XG Firewall device with v17.0 MR-10 EAL4+ certified firmware 

1. Customer needs to upgrade the XG Firewall firmware to SF v17.5.MR7 or later and activate the appliance.
2. Customer can then switch back to SF v17.0 MR-10 EAL firmware and continue using it.

• SF 16.01 StagedRelease (16.01.0.190)
• SF 16.01 StagedRelease3 (16.01.1.202)

• Authentication

STAS users with special characters (' , / ") in their name do not show up on XG. 

SFOS doesn't support a username containing special characters.

The user needs to remove the special characters in the username to make it work.

• SF 17.5 GA (17.5.0.310)
• SF 18.0 MR1-1 (18.0.1.396)

• Web

The policy tester is just showing Matched firewall rule ID, matched source, and destination zone. It does not return the webfilter id. 

• SF 17.5 MR9 (17.5.9.577)

• Email

A user interface issue exists in SFOS, reported in v17.5MR9 but also exists in later versions. 

If an Admin adds a wildcard SMTP exception for an FQDN host (Email->Policies and exceptions->Exceptions), the FQDN wildcard entry is accepted and is visible in the UI,  Email -> Policies, and exceptions. However, if the Admin attempts to edit this exception the added wildcard entry will not be visible.

This is confirmed as a UI issue and we are currently investigating. We have no fixed date or version at this time.

NA

• SF 18.0 MR3 (18.0.3.457) [Mindoro]
• SF 17.5 MR14-1 (17.5.14.714)

• Dynamic Routing (OSPF)

Issue description : Auto Cost Calculation does not work for OSPF
This is configurable under advanced settings of OSPF .

Workaround :
Uncheck the Auto Interface Cost and Manually Configure the Cost .

• SATC 2.2.0.0

• SATC

In July 2020, Google Chrome, the new Microsoft Edge, and other Chromium-based browsers moved to version 84. This version removed support for the ForceNetworkInProcess feature used as a workaround for previous versions as per NCL-1114.

Workaround is described here (public link):

https://support.sophos.com/support/s/article/KB-000038634?language=en_US

Downgrade to version below 84 and apply workaround or move to Firefox.

• SATC 2.2.0.0

• SATC

SATC installed on a server having Sophos InterceptX, installed reports wrong port information in new session details to the XG. 

Impact :
If an user attempts to open a TCP connection ,SATC will detect that TCP connection and send an UDP packet containing Login Code, Session ID, Source Port, Destination Port, Destination IP and Username before the TCP connect is completed, SFOS will add a expect based on the information received in that UDP packet.
SATC is unable to detect that TCP connect request thereby not sending any packet to SFOS which results in no expect being added at SFOS side and traffic being dropped. 
SATC is not sending any information on port 6060 which is used by Sophos Firewall to create an Expect Contrack .

https://support.sophos.com/support/s/article/KB-000036880?language=en_US

• SF 17.5 MR9 (17.5.9.577)

• SFOS 19.0.0 GA-Build317 (19.0.0.317) [Tupai]

• Hardware

XG 115 rev3 models will show no HDMI output unless a monitor is connected before boot up.

• SF 18.0 MR3 (18.0.3.457) [Mindoro]
• SF 18.0 MR4 (18.0.4.506) [Palawan]

• HA

With 18.0 MR1 there was a case where a backup contained redundant information increasing the size of the backup.

This was fixed with 18.0 MR3 in all cases.

There was no functional impact for this.

If a larger backup was taken and restored then /conf might be larger then expected.

In such cases please use the described workaround.

Backups after 18.0 MR 3 are not facing this.

Run commands:
rm -rf /conf/httpclient/httpclient
rm -rf /conf/iview_images/iview_images/
Re-run backup.

• SF 18.0 MR3 (18.0.3.457) [Mindoro]

• Web

Log viewer for 'Firewall' & 'Web filter' component shows 'Allowed' in logging for all the port 80/443 traffic, initiated from WAN to WAN/LAN zone. The user (client) who has initiated traffic from the WAN side will be displayed a 'blocked' page.

Note: The actual traffic is being blocked and not forwarded by XG.

• SF 16.01 StagedRelease3 (16.01.1.202)

• Authentication

Using SATC with IE11 in protective mode is not supported.

• SF 18.0 MR3 (18.0.3.457) [Mindoro]

• SSLVPN

OpenSSL limits the CN to be 64. OpenVPN limits the size of the CN to 63 + 1 (null character).

This limits the @ length to 51 characters because 12 characters random string appended to CN.

Only use usernames + domain with max 51 characters

• SF 18.0 MR1-1 (18.0.1.396)

• Email

If the user tries to add any domain or email address on the Page 'Email>> general setting>> block senders', then he'll get the error "Request could not be completed" and the domain or email address would not be added.

 The best possible way to avoid/resolve this is to remove any one of the domain/email address from the block senders list and re-add them again. This resolves the issue.

• SF 17.5 MR9 (17.5.9.577)

• IPS Policy

When the XG device is set to  FETCH mode in SFM and user changes the  "Advanced Threat" setting with template, though setting was applied correctly in XG Firewall, SFM event log show failure message

This is known issue for FETCH mode configured devices in SFM only.

In PUSH mode config XG Firewall devices, this issue is not observed.  

• SF 17.5 MR7 (17.5.7.511)

• Authentication

When using the Sophos Network Agent (iOS or Android) logout could take up to 2h. The APP itself gets disconnected immediately but on the UTM the user is still live which actually means he can still access network resources which should be blocked.

• Login to appliance with SSH

• echo 0 > /content/caaios

• echo 0 > /content/caaand

• restart access_server

Workaround is update and reboot safe

• SF 18.0 GA-SR3 (18.0.0.354)
• SF 17.5 MR9 (17.5.9.577)

• Firewall

**This scenario is observed when the DHCP request comes via a bridge interface and Heartbeat is set to block endpoint communication with RED heartbeat status on the firewall rule with inter-zone communication rule i.e. rule configured for Bridge interface. The MAC address is blocked this would also include the DHCP traffic for affected client machines.

When packets enter into the bridge interface, we are entering into Netfilter stack from L2 and all the decisions related to packet/connection taken at Layer 2. Now here, what happened is that Packet dropped by Firewall when it enters from the L2 stage. So traffic never submits to L3 (bridge interface) where the DHCP server is listening and DHCP will never get the packet. This issue will only for the client behind the bridge and will not happen for any other interface.

Create a Firewall rule which is positioned on top with Service: DHCP and with no heartbeat settings applied.

• SF 17.5 MR10 (17.5.10.620)

• Firewall

Description:

Live connections shown in the live view would not show a connection table entry for DNAT rules. 

Reason: While handling the connection table the connection to ZoneID 4 would not be considered in the live connection table. But this would show in Log Viewer and Reporting.

The issue was sorted out due to architecture changes in V18. 

• SF 18.0 GA-SR3 (18.0.0.354)

• CM (Join to Cloud)

If the Firewall is registered and central services are accepted by the Central Admin and somehow firewall lost its Central Registration information due to Factory-Reset/Firmware Downgrade.
On Re-registration and Enable Central Management, Endpoint already known to the Central and Central Management API considers this as a Bad request as Central Services already approved.

Work-Around 1:
Deregister the XG Firewall(If on HA Remove both the Firewalls) from the Central if already registered (XG Local UI-> Central Synchronization -> Deregister)
Remove the Firewall from the Central.
Login to central.sophos.com
Navigate to Firewall Management.
Choose Firewall row and click on "Remove from Central"

Workaround 2:
The following can be run via the advanced shell:
/bin/central-register --register -u -p -s
Once registration passes you can proceed to unregister from Sophos Central GUI

• SF 17.5 MR8 (17.5.8.539)

• Firewall

When checking email logs for bounced emails in the UI, IP addresses might be shown as source address which are not configured in the UI. 

The log entry is generated for connection table entries, not from the actual routing.
At point of time of conntrack creation SFOS uses any gateway IP as original source address ( example: Port4: 10.24.255.254) When routing is done on L3 , the decision might be to route that connection via Port 2 - but the original source is unchanged.

That means the original source is not necessarily used for routing.

• SF 15.01.0 GA (15.01.0.376)

• Framework part of Base (deprecated)

Sophos XG does only support the following authentication methods. 

PLAIN

Digest MD5

CRAM MD5

To authenticate agains Microsoft Office 365, one of these authentications methods need to be configured on both ends.

• SF 17.0 MR3 (17.0.3.131)

• WAF

We don't have protocol support for Microsoft's RDG  protocol suite which they added with Windows Server 2012 (we only support the "old" MSRPC suite). Whenever such a RDG (2012) connection fails the log contains line stating
method="RDG_IN_DATA"
or
method="RDG_OUT_DATA"
it's a strong indication the lack of protocol support is causing the connection to fail. Currently, this cannot be mitigated using the WAF.

WAF only supports RPC_IN_DATA and RPC_OUT_DATA, these are the only types enabled when Pass Outlook Anywhere is turned on. All other methods are unsupported

• SF 18.0 GA-SR3 (18.0.0.354)

• Firmware Management

XG would take more time (approximately 50 minutes) to upgrade the firmware from v17.5.x to v18 Build_354. This because v18 Build_354 is doing additional checks for file system correction, which would take more time based on the hard disk size and state.

• SF 15.01.0 MR3 (15.01.0.447)

• RED

It is not possible to do offline provisioning for RED50 devices using an USB device without doing an online provisioning first. RED50 keeps on rebooting continuously.

Do an online provisioning somewhere central. After first online provisioning is done offline provisioning is possible.

• SF 17.1 MR1 (17.1.1.175)

• Authentication Clients

We currently don't support SATC with the Edge browser.

• SF 16.05 MR5 (16.05.5.233)
• SF 17.1 MR1 (17.1.1.175)

• Network Services (deprecated)
• PPPoE

+Behavior:+ 

There will be difference in Data Transfer Traffic usages between WAN Link Manager and WAN Zone report.

WAN Link Manager: Go to Network > WAN Link Manager and click the Manage icon next to the IPv4 or IPv6 Gateway to view data transfer graphs related to that Gateway.
*WAN Zone reports:* Generated under Monitor & Analyze - Application & Web - Show:User App risks & Usage.

**

• Data Transfer usages In WAN Link Manager shows Layer 1/ Physical level stats and can be compared against ISP data transfer. 

• WAN Zone is the logical entity that works at Layer 3. Based on the traffic passed from specific firewall rule, the WAN zone graph is generated from the connection. 

Below statistics of WAN Link Manager and WAN Zone reports explain reason about different Data Transfer traffic usages.

1) WAN Link Manager statistics:

This is the statistics of data transfer at interface level – that is per physical or virtual gateway
This also includes device traffic – pattern and firmware download, license sync. And unknown traffic/ ping that is handled at that interface by the device
Device can have multiple interfaces as WAN links and all of them could be in WAN zone. Users can see WAN Link Manager stats per interface, not by zone.

2) WAN Zone Report statistics:

This is the statistics of traffic passed through Firewall rules per Zone
Traffic destined towards WAN zone can take one of the multiple WAN Links as defined by load balancing configuration and WAN Link weights/ active-backup configuration.

The attached logical diagram would also explain difference between WAN Link Manager and WAN Zone reports.

• Data Transfer usages In WAN Link Manager shows Layer 1/ Physical level stats and can be compared against ISP data transfer. 

• ISP Data Transfer traffic usages report can be compared with WAN link manager. WAN Zone data transfer report is not meant for that. 
      

• SF 17.0 MR6 (17.0.6.181)

• Authentication

Setup sso client agent following KB 123159

log into a machine and it works correctly. When they try and login to the same machine through RDP they get a popup windows that just say default

Logs will show the following
C:\Users\admin1\AppData\Roaming\Sophos\admin1.log

05/08/18 17:23:17 Return Message Code From Server Is -- > 5
05/08/18 17:24:35 Console has been disconnected. Switch user detected. logging out user 
05/08/18 17:24:35 Posting End Session....

Using the SSO client agent with RDP is not supported

• SF 18.0 EAP1 (18.0.0.102)

• NoRelease

• Firewall

The UI in v18 shows a wrong negotiation speed for virtual machines using the PCnet32 driver. This is only a UI issue.

• SF 17.0 GA (17.0.0.80)
• SF 17.0 MR1 (17.0.1.98)

• IPsec

You can not find/select an IPsec Profile from within an IPsec connection when this IPsec Profile has Aggressive mode enabled and the Connection is using PSK after you upgrade from any version to V17

VPN > IPsec connections> select an upgraded vpn connection> Under Encryption > click on Policy, the old custom policy used for this connection is not listed

Reason: Strongswan is not supporting PSK and Aggressive mode for security reason.

Either disable Aggressive mode on the IPsec Profile or Use RSA/Cert for Authentication instead of PSK.

• SF 17.0 GA (17.0.0.80)

• IPsec

IPSec v16 to v17 update does not set SHA2 truncation on custom policy.
This will mostly affect tunnels between v16.5 and v17 .

Impact
The customers migrating from v16 to v17 with IPSEC tunnels configured with the Encryption AES256 and Authentication SHA2 256 on custom policy in Phase-1 and Phase-2 will be affected.
The SA will be established however the traffic will not flow through the tunnel.

*How to Identify the issue *

The tunnel status could be verified from the GUI , The Status and Connection will be Green .
This could be verified from the Advanced shell with uptime .

#ipsec statusall
Output:
Status of IKE charon daemon (strongSwan 5.5.3, Linux 3.14.22-Aum, x86_64):
uptime: 68 minutes, since Nov 20 18:02:23 2017

The workaround is to enable the SHA2 with 96-bit truncation on v17 policy.
Go to Configure > VPN > IPSec Profiles.
Under General Settings, select SHA2 with 96 bit truncation.
Click Save.

• SF 17.5 MR5 (17.5.5.433)

• NoRelease

• L2TP

Username with backslash "\" character are unable to authenticate when logging with domain via L2TP

The character "\" is not supported as part of the username in XG Firewall.

User can simply check this by creating new user manually having "\" character in username, XG firewall will not allow you to create such user.

XG Firewall supports authentication with the sAMAccountName username (i.e. asystest) or with the fully qualified username (i.e. asystest@xyz.local)  which works, but not with the NETBIOS format, indifferent of the server.

• SF 17.0 MR6 (17.0.6.181)

• SSLVPN

Self Signed certificates are not supported as SSL server certificate in SSL VPN . You cannot issue the certificate for yourself but requires a CA to sign / approve server certificate. 

A certificate signed by local CA i.e.  issued by default certificate authority (CA)is supported i.e. certificate "ApplianceCertificate" shown in below screenshot is supported. 

• SF 17.5 MR7 (17.5.7.511)

• Authentication

XG firewall supports a maximum of 3042 Corporate Authentication Agent connections at the same time.

If the number of users is exceeding this then logs like "Failed to establish connection! Too many open files" will appear in access server log file.
This number is only for users using Corporate Authentication Agent, Live user count for other authentication mechanism are not included in this limit.

• SF 17.5 MR8 (17.5.8.539)

• IPS Policy

The "show ips-settings" command in the console only displays 8 firewall rules in case you have configured more.
The related database entry contains all configured firewall rules.
This is only a display issue.

• SF 17.0 MR6 (17.0.6.181)

• Web

When a file is scanned by sandstorm, Admin get a cannot reach page after scanning (throw by Sophos XG captive portal).

This is observed When Any to Any firewall rule is configure as DROP.

Create Specific LAN/WAN zone instead of Any zone for DROP firewall rule

• SF 17.5 MR8 (17.5.8.539)

• RED

When multiple WAN gateways are configured on the XG, any action that causes the backup gateway or the gateway not being used by the RED tunnel to reconnect will cause all RED tunnels to reconnect.

None

• SF 17.5 GA (17.5.0.310)

• Firewall

There might be a delay before an SSH session is shown in the LogViewer.

• SF 17.1 MR1 (17.1.1.175)

• WAF
• Web

When LAN users want to use a webserver protected by a WAF in the LAN zone than those requests don't work. Reason is that requests from the LAN zone will reach the webserver(s) directly without passing the XG.

• SF 17.1 MR2 (17.1.2.225)

• NoRelease

• RED

*ISSUE -* Trying to start the RED results in unknown internal error:

*BACKGROUND -* The customer upgraded the XG 135 to v17.1.2 MR2 and thereafter out of 2 red tunnels only one was showing up on the GUI.
So they tried to restart the RED service by toggling the RED status but since they turn of the RED configurations on XG, it is not getting enabled back again.
Error message: [Unknown Internal Error occurred]

INVESTIGATION:

Following rebind issue logs were found

Mon Sep 17 04:02:36 2018 REDD ERROR: Rebind of RED devices failed: Failed to get config of all devices: Expected reply from get_object_by_hash() with status
 200 but got 500 without error message. $VAR1 = {
          'status' => 500,
          'Records' => []
        };

REDD: Red::Backend->enable_feature_event failed; result 520

Browser debug shows the following:

{transactionID: "5690", status: 520, message: "", opcodeMessage: "Enabling RED feature failed",…}
entity
:
{map: {country: "AU", Entity: "redconfiguration", ___serverport: 65003, ___component: "GUI",…}}
map
:
{country: "AU", Entity: "redconfiguration", ___serverport: 65003, ___component: "GUI",…}
APIVersion
:
"1701.1"
Entity
:
"redconfiguration"
Event
:
"UPDATE"
city
:
"Narangba"
country
:
"AU"
currentlyloggedinuserid
:
4
currentlyloggedinuserip
:
"127.0.0.1"
email
:
"licensing@ahe1.com.au"
mode
:
1320
organization
:
"Atlas Heavy Engineering"
status
:
"1"
transactionid
:
"5690"
___component
:
"GUI"
___serverip
:
"127.0.0.1"
___serverport
:
65003
___serverprotocol
:
"HTTP"
___username
:
"support"
message
:
""
opcodeMessage
:
"Enabling RED feature failed"
redirectionURL
:
""
status
:
520
transactionID
:
"5690"

Looks quite similar to the JIRA NC-27578
I am attaching the combined logs

 for the following :
CSC DEBUG
RED
TOMCAT DEBUG
APPLOG
APACHE

and CSCHELPER 

Backup of the unit - 

ACCESS ID

05894141-f8b9-3615-ba4d-cb876759c539

• SF 17.1 MR4 (17.1.4.254)

• NoRelease

• Email

Chinese characters in the subject of quarantined mail are not displayed correctly within the quarantine digest mail. The display in the GUI itself is correct, but appears garbled in the quarantine digest email only.

Changing the encoding used in the end user's mail client to encoding to UTF-8 acts as a workaround for this issue. We also have plans to resolve this in a future software update but no timelines on this currently.

• NoRelease

• Hardware

XG125/135 Rev.3 does not work with Halfduplex in any setting on Port 1,2,3,4.
Port 5,6,7,8 will work with halfduplex.

• SF 16.05 GA (16.05.0.117)
• SF 17.0 GA (17.0.0.80)
• SF 17.1 GA (17.1.0.152)
• SF 17.5 GA (17.5.0.310)

• Networking (deprecated)

We do not support Policy Based Routing (PBR )on return traffic on any version prior to v18

• SF 17.5 GA2 (17.5.0.321)

• Email

Any manual change to the disable_offline_relate is lost during a firmware upgrade.

If, prior to an upgrade, the /static/proxy/smtp/scanner.conf file has been changed to set the disable_offline_relate setting to 'no' this will be lost during a firmware update and will need setting again.

We plan to introduce a GUI option to set this option that will persist through a firmware upgrade in a future release

Once firmware upgrade is complete edit /static/proxy/smtp/scanner.conf and update the disable_offline_relate again

• SF 17.5 GA (17.5.0.310)

• Networking (deprecated)

System route_precedence is configured to give VPN Routes a higher priority than Static Routes however the XG firewall is not sending the expected traffic over the IPSEC tunnel and instead routing it via a matching static route.

This occurs if there is a static or local route that directs this traffic to a non-WAN zone. The route precedence command only applies to traffic that is destined for a WAN zone 

In this scenario manually creating an IPSEC route for the remote subnet will resolve the issue.

E.g
console> system ipsec_route add net 192.168.1.0/255.255.255.0 tunnelname

Hitting tab twice after tunnelname will show a list of available tunnels.

• SF 16.01 StagedRelease (16.01.0.190)

• Routing (deprecated)

Policy based routes for RED interfaces are not working.

• SF 15.01.0 MR2 (15.01.0.418)

• Clientless Access(HTTP/HTTPS)

Clientless Access feature requires rewrites HTML links within the response document, to ensure that links work for users outside the proxy. If website contains URL links with UTF-16 encoded special characters like example below, then site will not open properly using Clientless Access(HTTP/HTTPs) feature

Example:. http:\u002f\u002fportal.example.com  -> contains character encoded in UTF-16 format

• SF 17.1 GA (17.1.0.152)

• ATP Framework

Let us know if there is any limit on adding Threat Exceptions under Protect - Advanced Threat - Advanced Threat Protection.

*Web Admin:* _Protect - Advanced Threat - Advanced Threat Protection_

• There are no limitations to add Threat exceptions.

• However there is a limit of 128 characters for the "length" of Threat exception.

• SF 17.1 GA (17.1.0.152)

• Wireless

Limit on adding number of wireless networks.

Web Admin: Protect - Wireless - Wireless Networks

• There are no limitations on creating Wireless Networks.  

• However there is a limit of "8 SSIDs/Networks" that can be assigned to a Single Access Point. 

• SF 16.01 Beta3 (16.01.0.144)

• SecurityHeartbeat

On ATP flipside, host information for blocked sources is displayed. This information is not updated, the flipside needs to be manually reloaded/re-opened to see changes (e.g. host states green, red, missing)

• CaptivePortal

Local user with names that contains umlauts (ööööööö) cannot login (if the login is happening via AD / STAS then a login is possible.)
Local user with with special characters ( UTF-8) could not becreated , even existing AD user with those name cannot login.

• SF 15.01.0 MR1.1 (15.01.0.407)

• Clientless Access(HTTP/HTTPS)

Access of HTTTP/s bookmark to web servers which contains JavaScript based dynamically generated URLs is not possible.

• Hardware

a small percentage of SG and XG 430/450 Rev.1 appliances not being accessible  anymore except via serial. This is caused by a SSD software/firmware issue. The serial console output shows the errors:

• Reboot and Select proper Boot device

• Insert Boot Media in selected Boot device and press a key

• I/O error on SDA

• SQUASHFS error

This issue is based on problems with the Solid State Disk (SSD) firmware. 

If you have an SG or XG 430/450 Rev.1 that is experiencing issues like those shown above, please contact Sophos Support for further instructions. If possible go ahead and make a backup with one of the KBA's mentioned below:

• Sophos XG Firewall:
  How to backup and restore a configuration:https://community.sophos.com/kb/en-us/123145|

• Sophos UTM:
  How to backup and restore a configuration: https://community.sophos.com/kb/en-us/115187

• VPN (deprecated)

No L2TP connection is possible to mobile phone with Android (5.0.1 on Samsung S4) or iOS (10).
Both negotiated successfully IPsec phase 1 (main mode) but fail negotiating phase2 (quick mode).
Log excerpt from /log/ipsec.log, valid both for Android and iPhone connection attempts:

Oct 06 10:46:33 "l2tp"[1] 10.147.34.103 #15: STATE_MAIN_R2: sent MR2, expecting MI3
Oct 06 10:46:33 "l2tp"[1] 10.147.34.103 #15: Main mode peer ID is ID_IPV4_ADDR: '10.147.34.103'
Oct 06 10:46:33 "l2tp"[1] 10.147.34.103 #15: I did not send a certificate because I do not have one.
Oct 06 10:46:33 "l2tp"[1] 10.147.34.103 #15: transition from state STATE_MAIN_R2 to state STATE_MAIN_R3
Oct 06 10:46:33 "l2tp"[1] 10.147.34.103 #15: STATE_MAIN_R3: sent MR3, ISAKMP SA established {auth=OAKLEY_PRESHARED_KEY cipher=aes_128 prf=oakley_sha group=modp1024}
Oct 06 10:46:33 "l2tp"[1] 10.147.34.103 #15: Dead Peer Detection (RFC 3706): enabled
Oct 06 10:46:33 "l2tps"[1] 10.147.34.103 #15: ignoring informational payload, type IPSEC_INITIAL_CONTACT
Oct 06 10:46:33 "l2tp"[1] 10.147.34.103 #15: received and ignored informational message
Oct 06 10:46:34 "l2tp"[1] 10.147.34.103 #15: cannot respond to IPsec SA request because no connection is known for 10.8.18.51:17/1701...10.147.34.103:17/%any
Oct 06 10:46:34 "l2tp"[1] 10.147.34.103 #15: sending encrypted notification INVALID_ID_INFORMATION to 10.147.34.103:500
Oct 06 10:46:37 "l2tp"[1] 10.147.34.103 #15: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x635c829e (perhaps this is a duplicated packet)

• WAF

After the successful form-based authentication the user is always redirected to the defined path in the corresponding site path routing profile and not to the original requested path of the user.

• SF 16.05 MR1 (16.05.1.139)

• Clientless Access(HTTP/HTTPS)

Website which strictly require the destination domain in the URL host part could not be accessed through Clientless Access.  An example for this is CNN.com

• SF 15.01.0 MR1.1 (15.01.0.407)

• Clientless Access(HTTP/HTTPS)

Webadmin access through an clientless access VPN bookmark on the same appliance is not possible.

• SF 15.01.0 MR2 (15.01.0.418)

• WAF

Outlook Anywhere is not working when CTF (Common Threat Filter) is enabled in Business Application Rule.

Disable CTF (Common Threat Filter) in *Web App Protection Policies

• SF 15.01.0 MR1.1 (15.01.0.407)

• WAF

WebSockets is an advanced technology that makes it possible to open an interactive communication session between the user's browser and a server. Sophos XG Firewall only supports WebSocket passthrough starting from version 17.0, in earlier versions this functionality of Webserver Protection is not availableos XG.

• SF 15.01.0 MR1 (15.01.0.398)

• Hotspot

A Custom logo is not displayed if the Hotspot name is including a whitespace.

Dont use whitespaces in Hotspotnames

• SF 15.01.0 GA (15.01.0.376)

• Firewall

Its not possible to create a Hotspot with an HTML file name through SFM which contains a space.

-------------------------------------------------------------------------------------------------------------------------------------

Dont use spaces in file names.

• SF 15.01.0 GA (15.01.0.376)

• VPN (deprecated)

IPSec Site-to-Site VPN with SonicWall is not supported with Aggressive mode

Use Main Mode

• SF 15.01.0 MR3 (15.01.0.447)

• Firewall

– After installation of SFOS v15 MR3 on Super Micro X10SDV-TP8F, the Dual 10G SFP+ Network cards from D-1500 SoC are not recognized anymore.
– Issue is also reproducible in SFOS v16

More about device specifications can be found here :

https://www.supermicro.com/products/motherboard/Xeon/D/X10SDV-TP8F.cfm

– Output of Dmesg related to Ethernet is shown below
– Output of lspci is needed by developers to analyse further

[    6.505941] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    6.512798] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    6.523049] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    6.538388] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.1.23
[    6.547374] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k
[    6.587508] igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection
[    6.634442] igb 0000:08:00.0: Intel(R) Gigabit Ethernet Network Connection
[    6.819952] igb 0000:0b:00.0: Intel(R) Gigabit Ethernet Network Connection
[    7.002801] igb 0000:0b:00.1: Intel(R) Gigabit Ethernet Network Connection
[    7.190630] igb 0000:0b:00.2: Intel(R) Gigabit Ethernet Network Connection
[    7.378468] igb 0000:0b:00.3: Intel(R) Gigabit Ethernet Network Connection
[    7.380785] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.0.2-k
[    7.386529] ixgb: Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI
[    7.397845] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.17.3
[    7.399517] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.12.1-k
[    7.481665] QLogic/NetXen Network Driver v4.0.82
[    7.586272] tehuti: Tehuti Networks(R) Network Driver, 7.29.3

No workaround available

• SF 16.01 StagedRelease3 (16.01.1.202)

• Web

– Safe search is enforced globally and on all the policies without any exception once it is enabled.

Issue reproduction :
– Use the default 'Allow All' policy from the Web Protection policies
– Enforce the policy in a firewall rule and enforce safe search
– Try to search a word which shows explicit results, you would see that explicit results will be filtered even though safe search ins disabled
– Even youtube would enforce safesearch in this case

Now disable 'Enforce Safesearch' option and do the same search with caution. You will see all the related results which is explicit in content.

• SF 16.05 MR1 (16.05.1.139)

• Networking (deprecated)

The username field for PPPOE interface configuration is limited to 50 characters.

If the username is more than 50 characters for eg: john.doe0123456789012345678901234567890123456789@example.com

Use the workaround described below

Insert any dummy username in the GUI PPPOE interface config where username is less than 50 characters

Goto the advanced shell and enter:=> psql -U nobody -d corporate (Go to corporate DB)
=> corporate=>update tblpppoeconf set "user"='john.doe@example.com';

After applying the above command do disconnect the pppoe connection and reconnect again to bring the changes into effect.

• SF 16.05 GA (16.05.0.117)

• Email

• In Legacy Mode, Configure a policy with Action : Prefix Subject with Umlaut (Ü,Ä,Ö) in the prefix. The email prefix subject is incorrectly decoded.

• SF 16.05 MR5 (16.05.5.233)

• Clientless Access(HTTP/HTTPS)

Bookmark of websites  that requires NTLM  authentication in clientless access will not work.

• SF 16.05 MR7 (16.05.7.305)

• Email

When using IMAP, prefix subject (Spam) is not visible in many e-mail clients unless specifically selecting the message.

Some of the Mail Clients download only root header's from Server before downloading full Mail. SFOS IMAP proxy doesn't scan headers for spam checking as headers are not enough information to detect spam. IMAP proxy scan Mail for spam when mail client download full Mail.

• SF 16.05 MR6 (16.05.6.266)

• Web

Issue: Citrix Base Web Application (www.bimco.org) is not working with Allow ALL Web Policy

In transparent mode, Citrix clients are not aware of the fact that there is an http/https proxy in between, thus it starts talking a proprietary protocol (not http/https) using http/https ports which is not understood by the proxy, which in turn results in a kind of stalemate (proxy is waiting for client request, while Citrix client is expecting something from server first).

Due to the above behavior, launching an .ica file with any Citrix web or application based will fail.

For workaround, user must have a hole punched in firewall to the bimco.org ip address(es) to launch the ica file..

1: Allow none web policy in LAN-WAN for destination addresses associated with www.bimco.org and launching the ica file.
2: Allow all web policy in LAN-> WAN

• SF 17.0 MR3 (17.0.3.131)

• Email

If greylisting is enabled on server side all subsequent mails are getting rejected. This is because Legacy Mode doesn't support retry of E-Mail. If E-Mail fails to send, Legacy Mode Proxy generates Notification and inform Sender. So, as per greylisting, failed E-Mail should retried but this is rejected with Log entry "451 Temporary local problem, please try again!"

https://community.sophos.com/kb/en-us/131686

• SF 16.01 MR1 (16.01.2.222)
• SF 16.05 RC1 (16.05.0.098)

• NoRelease

• Hardware

Issue : The device doesnt boot up after HA takeover when the unit is equipped with 4x10GE SFP+ flexi modules

How to identify :

• After a HA takeover the following BIOS error appears 'PXE-E01: PCI Vendor and Device IDs do not match' 

• This is resolved after removing 4x10GE SFP+ flexi modules everything works fine.

• This could be noticed only sporadically after 4-5 reboots

Root cause and Fix :

This is caused due to old BIOS versions. The latest BIOS version of XG devices is R1.02, this is not affected by this issue. This can be verified during the startup or by interrupting the startup by pressing TAB or DEL. For older devices we have the steps to upgrade BIOS manually. Please contact Sophos support.

• SF 17.0 MR3 (17.0.3.131)

• Firewall

SSL VPN user can ping to LAN but LAN can not ping to SSL VPN.

If both SSL VPN and Policyrouting is configured for a destination network then by default policyrouting is enabled That is because routing precende by default is doing policyrouting first. To change this routing precendence needs to be changed.

This could be done via console:

console> system route_precedence set static policyroute vpn

 To reach the destination through SSL VPN the static route precendence has to be the firste entry in the routing precendence table.

Checking the actual status could be done via console :

console> system route_precedence show

Routing Precedence:

1. Static routes

2. Policy routes

3. VPN routes

• SF 15.01.0 MR1.1 (15.01.0.407)

VPN Authentication for IPSec / L2TP / PPTP is not working with AD.

Use Authentication method PAP instead

For XG85/w and 125/135/w Port 3 and Port4 Link/Act LEDs are glowing without the port being enabled and configured.

• SF 17.0 MR3 (17.0.3.131)

• Networking (deprecated)

A static route cannot apply to the system for the connected network i.e. any static route cannot be configured for connected networks. 

Ex:-

Any interface configured with IP 192.168.115.115/24 then system kernel will not add the route for static route
'192.168.115.0/24 via 10.250.41.21'.

• SF 17.0 MR6 (17.0.6.181)

• SF 17.1 Beta3 (17.1.0.147)

• VirtualAppliance

Due to a VMware Issue on vSphere a random network interface mapping occurs with more than 3 network interfaces on SFOS. This happens only on vmxnet3 and e1000e NIC driver.

Use e1000 or flexible (pcnet32) NIC driver

• SFM 15.01.0 MR-1 (15.01.0.425)

• Base System

• HA is only supported for Hardware SFM devices

• HA is not supported in Virtual SFM

No Workaround

• SFOS Compatibility in SFM

• SF Compatibility

Device is shown as unsynced for upto 5 minutes after changing/adding an IPS rule in SFM at device level.

Note: Device comes in sync after few minutes and configuration is applied.

• SFM 17.1 MR2 (17.1.2.300)
• SFM 17.1 MR3 (17.1.3.200)

• SFM-SCFM

You are unable to upload v18 firmware to SFM devices to deploy to XGs running v17.5.x devices.

Trying to upload the file gets to 97% and then nothing happens.

This is a known issue.

Load firmware manually to XG

• CFM 17.1 MR3 (17.1.3.xxx)

• SCFM

When applying RED configuration from CFM group level in the System services module the configuration will fail with the error message: _Data is invalid and cannot be synchronized on the device._ 

This issue is observed for SF 17.5.MR11 onwards because of UI for SF 17.5.MR11 onwards for RED configurations has been changed.

Use single device management by selecting device from Select devices and then applying configuration for RED

• SFOS Compatibility in SFM

• SF Compatibility

SFM has default IPS signature set and XG appliance supports signature set based on RAM size.

If Admin pushes signatures from SFM then signature will be displayed on XG based on RAM size and other signatures wouldn't be display even Admin see the success message on SFM UI. 

• CCC-10.6.5

• CCC-CCMS

User unable to download and upgrade Cyberoam firmware from CCC

User can upgrade the Cyberoam firmware from Cyberoam UI.

• CFM 17.1 GA (17.1.0.132)

• SCFM

CCL not being populated with changes applied to CCL enabled device in SCFM

Example: 

XG has CCL enabled on it,

• Created a test object called "asdf3_delete" with IP "7.7.7.7" on SCFM and pushed it to the device.

• The XG received the object and created it successfully.

• But no CCL log has been generated in SCFM.

• CROS Compatibility in CCC

• SCFM

CCC Import Template is not working with 10.6.6 MR-5. 

Template is imported successfully but it is imported without any configuration Data.

• CFM 17.1 GA (17.1.0.132)

• SCFM

SCFM connection tracking gets full which results in XGs working with syslog port/protocol from being able to sync fully or templates to be pushed.
There are no plans to fix this issue and as such we recommend using HTTPs instead.

Use https instead of syslog

• CFM 17.0 GA (17.0.0.101)

• SCFM

In some cases it seems like SCFM can't push the template to the device. In fact it just takes a very long time to do this ( could be a few hours).

• VFM 17.0 VarioSecure GA (17.0.0.111)
• SFOS Compatibility in SFM

• SF Compatibility

In SFM/CFM import template support for Web Proxy Configuration General setting is not supported for SFOS v17.5.

 Web Proxy Configuration import template does not support for Web - General Settings - HTTPS Decryption and Scanning and Web-General Settings for SFOS v17.5.

• SFM 16.05 GA (16.05.0.157)

• SFM-SCFM

There's no option to 'Create' a network for Local or Remote S2S VPN, only choosing from the one manually created before, same behavior also in the Firewall rule.

• Android

The “Security & Antivirus Guard” app is not available anymore on devices running Android 10 or higher.

After recent changes made by Google apps that haven’t been updated for a while cannot be installed anymore.

There have been several changes to the Android operating system and the Intercept X app, reducing the need for the Security & Antivirus Guard app.
The app will remain unavailable for devices running Android 10 or later. It will be completely removed in the near future.

• Android

For some Android versions and devices, Gmail doesn’t attach log and trace files to the email you send to Sophos support.

Send log and trace files with a different email app than Gmail.

• Android

Web Filtering supports the following browsers:

• Google Chrome

• Mozilla Firefox

• Microsoft Edge

• The native Android browser (preinstalled on older devices)

• Android

On some devices, Android doesn’t restore Sophos Intercept X for Mobile app settings when you reinstall the app or install it on another device using the same Google account.

This issue is caused by the Android Backup Service.

• Android

Because of Android limitations, App Protection can only prevent user interaction with a password-protected app via the app’s user interface. Users can still interact with the app via other apps like Google Assistant or Android system functionality.

Also, App Protection can’t prevent interaction with an app that runs in a multi-window mode, such as split-screen, floating windows, or tiny windows.

For details, see Sophos Mobile - Access to protected / controlled apps still possible by 3rd party apps.

• Android

On some devices (such as the Asus Zenpad 10), Android turns off the Sophos Accessibility Service, which Web Filtering requires, when Sophos Intercept X for Mobile is updated.

Either turn on the service in the Android settings or restart the device.

• Android

On some devices, Android turns off the Sophos Accessibility Service, which Web Filtering requires. Sophos Intercept X for Mobile detects this and asks the user to turn on the service again.

• Android

App Protection can’t protect apps running in Samsung pop-up view.

Pop-up view is a feature of some Samsung devices, such as the Samsung Galaxy S7 and S8.

• Android

On Android 6.0 and later, an app isn’t allowed to change a Wi-Fi configuration added by another app or by the user. Therefore, QR Code Scanner can only change the Wi-Fi password of networks added by Sophos Intercept X for Mobile.

• Android

On Android 6.0 and later, Sophos Intercept X for Mobile can’t monitor copying files to the device at all times. This is a known issue of the Android functionality we use for monitoring SD card access.

For example, the app can’t detect copying files from a computer connected via USB.

This limitation doesn’t affect copy operations initiated by the user on the device, such as downloading files from the internet to the SD card.

• Android

The App Protection feature on Xiaomi devices only works if the client was once opened and if the Display pop-up windows while running in the background permission in App info > Other permission is turned on.

Please find details on how to enable the "Display pop-up windows while running in the background" permissions in this KB:
https://support.sophos.com/support/s/article/KB-000044671?language=en_US

• Android

You can install Intercept X for Mobile from Google Play on Chrome OS devices supporting Android apps, such as all Chromebooks launched after 2019.

When Intercept X for Mobile runs on Chrome OS, the following limitations apply:

• Device Security can’t check the Screen lock and Require PIN to start settings.

• Web Filtering only works for Android browser apps. For the Chrome browser included in Chrome OS, use the Web Filtering feature of the Sophos Chrome Security extension.

• App Protection doesn’t work.

• Link Checker only works if there’s an Android browser app installed.

• Android

Wi-Fi Security can’t detect ARP Spoofing on devices running Android 10 or later.

This is an Android limitation.

The Threat Analysis Center Dashboard will not contain any information/data if a customer only has an Intercept X Advanced or Server Intercept X advanced only license.

The default Threat Analysis Center (TAC) Dashboard (New dashboard) contains widgets and details about XDR and MDR level detections only. For non-XDR/MDR customers this dashboard will show zero detections or other data.

The Intercept X Advanced licenses include the ability to see the ‘Threat Graphs’ details. This data can be seen within the TAC area, by either selecting the submenu section ‘Threat Graphs’ or switching the toggle on the TAC dashboard to view the ‘Original dashboard’. The Original dashboard will show a widget showing the 5 most recent threat graphs created.

Currently this is expected behavior and the only data Intercept X Advanced only customers will have access to, is the 'Threat Graphs' data within the Threat Analysis Center' section

• Sophos Mobile server

When using the QR code enrollment method the login within the Sophos Mobile Control app does not work with the provided user credentials even though the used email address. This behavior can occur if the Sophos Sign-In settings are set to “Federated Authentication” and the user is added to the Exception list.

The login within the Sophos Mobile Control client will not work in this scenario.

Within the Sophos sign-In settings change the sign-in method to "Sophos Central Admin or Federated credentials".
After saving the settings change, login in the Sophos Mobile Control client will work.

• Sophos Mobile Control (Android)

If WiFi-only devices are used and a certificate-secured WiFi connection is distributed via Sophos Mobile, the connection will be lost after the assigned policy is changed.
This is caused by the way how policies are distributed via Sophos Mobile. If there is no alternative network connection available, devices have to be reset to get them connected again.

• Sophos Mobile server

When a “Send message” task is included in the enrollment task bundle, it might fail with an error message indicating that APNS or FCM information is missing.
This can be caused if the device requires too long to send the required information to the Sophos Mobile backend.

There is currently no workaround available. A fix might be included in a future update of the Sophos Central Mobile backend.

• Sophos Mobile server

When opening an email policy after navigating through the Sophos Central Mobile user interface the checkboxes for the enabled services are sometimes cleared.

• Sophos Mobile Control (iOS)

In some cases, the silent trigger sent by Sophos Mobile doesn’t result in automatic background synchronization.

Let your users synchronize the app manually.

• Sophos Mobile Control (iOS)

Installing a recommended or required app via an iTunes link on an iOS device requires the Safari web browser. When you restrict Safari, users can’t install recommended and required apps via an iTunes link.

• Sophos Mobile Control (Android)

Due to technical limitations of the Android platform, the App Protection and App Control features can only prevent direct interaction with an app through its user interface. Users can still interact with a protected app via other apps like Google Assistant or via Android system functionality.

Also, note that App Protection can’t stop interaction with an app that runs in multi-window mode, for example, split-screen, floating windows, or tiny windows.

For details, see support article 135017.

• Sophos Mobile Control (Android)

On some devices capable of Factory Reset Protection (FRP), we’ve noticed an FRP is not supported error when you turn on FRP via Sophos Mobile.

This issue isn’t caused by Sophos Mobile.

• Sophos Mobile Control (Android)

There’s a known Android issue related to the work profile. Starting with Android 8, the Android internal WebView app is disabled by default. As a result, apps in the work profile that rely on the WebView app might stop working.

Google resolved this issue by enabling the Chrome app, which enables the internal WebView app. However, you might not want to allow a browser app in the work profile.

For more information regarding this issue, see the Google article https://support.google.com/work/android/answer/7506908.

To disable Chrome in the work profile, use the App Control configuration of your Sophos Mobile Android Enterprise policy.

• Sophos Mobile server

In rare cases, binding Sophos Mobile with a third-party service such as Microsoft Intune Mobile Threat Defense fails with a 401 Unauthorized HTTP error. We've only seen this with Google Chrome, not with other internet browsers. Apparently, Google Chrome sometimes doesn't attach a required authorization token to the request.

Open Sophos Central in a different internet browser than Google Chrome.

• Sophos Mobile Control (iOS)

On some devices, users can uninstall apps even if you turn off the Allow app removal restriction in the iOS device policy.

This is an issue in iOS.

• Sophos Mobile Control (iOS)

Updating an iOS Single App Mode profile doesn’t update all contained settings. The Disable… options are updated correctly. All other options only work on the first installation of the profile.

This is an issue in iOS.

To change the settings, remove and reinstall the profile.

• Sophos Mobile server

In some cases, Windows 10 computers might be reported as compliant even if Windows Defender is turned off. This is because the Defender activated compliance rule can only check if the Defender service is running. It doesn’t check if real-time protection is turned on.

• Sophos Mobile server

When you rename profiles, removal tasks might show the old profile name.

• Sophos Mobile server

Some pages of Sophos Mobile Admin might look corrupted after an update of Sophos Mobile.

Clear your browser cache and reload the page.

• Sophos Mobile server

An Android profile that has been created by using the Duplicate command in an older version of Sophos Mobile can't be removed from devices using a task bundle.

• Sophos Mobile Control (Android)

“Small apps” are Sony-specific apps on Sony devices that overlay existing apps. You can’t control or protect these apps with the Sophos Mobile Control app or App Protection.

• Sophos Mobile Control (Android)

The device ignores the Knox premium restriction Prevent installation of another administrator app on a device if there’s already another device administrator activated.

Make sure Sophos Mobile Control is the only device administrator before you assign the restriction.

• Sophos Mobile Control (Android)

You must restart Samsung devices with Knox Standard (formerly called SAFE) SDK version earlier than 5.4 after installing a Kiosk Mode profile. If you don’t, users can stop all running apps in the task manager and switch to the default launcher home screen.

• Sophos Mobile server

In some cases, you get a Text contains forbidden HTML elements error when you try to save enrollment texts for the Sophos Central Self Service Portal that contain HTML formatting, although the text you've entered is valid.

This issue is caused by an error in the HTML parser library.

Change the font size of underlined text and delete any styling attributes.

• Sophos Mobile server

When you invite too many users to the Apple Volume Purchase Program (VPP) at once, Apple might reject further requests for a few minutes.

We will fix this issue in a future version of Sophos Mobile.

Reduce the number of users included in the invitation.

• Sophos Mobile server

Some Windows 10 computers don’t register correctly for the Windows Notification Service (WNS). There’s a time-out of their push registration after 30 days, and the devices fail to renew the registration automatically.

Although the Sophos Mobile server enforces the renewal, some devices send the old, invalid push registration information to the Sophos Mobile server when they re-register. As a result, the Sophos Mobile server can't send push notifications to these devices to synchronize the built-in MDM agent.

This is a known issue in Windows 10.

• Sophos Mobile Control (Android)

Starting with Android 8, the installation of apps from unknown sources isn’t a device setting. It’s a permission setting for apps that can install other apps. For example, a file manager app.

Sophos Mobile can’t check if any third-party app has this permission. Devices with Android 8 ignore the Apps from unknown sources compliance rule.

• Sophos Mobile Control (Android)

When you transfer an Exchange mail account to an Android work profile, the account remains configured in the profile when you remove the policy. You can assign a policy with a different Email configuration to the device. The device always uses the latest Email configuration. However, you can’t remove the configuration from the work profile.

To remove the configured account, remove the whole Android work profile from the device.

• Android

Sophos Secure Email for Android can’t show messages that are larger than 3 MB.

• Android

Sophos Secure Email for Android doesn’t support email encryption such as S/MIME or PGP. Also, Sophos Secure Email for Android doesn’t support the verification of digitally signed emails. You can view S/MIME-signed emails, but you can’t verify the signature. You might not be able to view emails at all that are signed with a different certificate, such as PGP.

• Android

When you select the Real push notification or New email without information notification setting, Sophos Secure Email for Android shows a second, unrelated notification for each New email notification.

Select a different notification setting.

• iOS

In rare cases, the calendar might stop syncing when Sophos Secure Email for iOS runs for a long time with a poor network connection.

Close the app (double-press the Home button and swipe up on the app in the app list) and restart it.

• iOS

When searching for local contacts, entries with accented characters in their name, such as umlauts, aren't found.

• iOS

There’s no badge displayed on the app icon when you’re using a Microsoft Exchange server.

• iOS

In search results, Sophos Secure Email for iOS disables actions (reply, forward, delete, etc.) for emails stored on the server but not on the device.

• iOS

Sophos Secure Email for iOS only supports writing plain-text emails.

Support for RTF and HTML emails is planned for a future app version.

• iOS

If the password contains special characters such as umlauts, authentication with Exchange Online (Microsoft 365) might fail.

• iOS

In rare cases, Sophos Secure Email for iOS doesn’t show email and appointment notifications, although you turned on notifications.

Close the app (double-press the Home button and swipe up on the app in the app list) and restart it.

• iOS

Sophos Secure Email for iOS doesn’t mark spelling mistakes in email text.

• Android

Sophos Secure Email for Android only works when you configured a secure screen lock method such as PIN, Pattern, or Password. The app might fail to open if you set no or an insecure screen lock method such as Swipe.

• Android

Currently, Sophos Secure Email for Android doesn’t support viewing PDF documents in Google PDF Viewer.

Open PDF documents in a different app, for example in Adobe Acrobat Reader.

• Android

On some devices, Sophos Secure Email for Android stops responding while unenrolling from Sophos Mobile.

Stop the app (remove it from the list of recent apps) and restart it to check that it’s unenrolled.

• Android

On some devices, Sophos Secure Email for Android might show the policy check window every time it starts. This issue can be caused by a poor network connection with recurring connection losses.

Stop the app (remove it from the list of recent apps) and restart it.

• Android

In rare cases, Sophos Secure Email for Android stops responding while showing the registration window that is part of the enrollment process.

Stop the app (remove it from the list of recent apps) and restart it.

• iOS

In rare cases, users might get locked out of Sophos Secure Email after you reset the Sophos container password. Users can’t open the app to set a new password.

To resolve the issue, do as follows:
1. Run the Unenroll Sophos container device action.
2. Reassign the container policy to the device.
3. Reinstall Sophos Secure Email.

• iOS

Because Sophos Secure Email for iOS doesn’t support the voice control system added with iOS 13, the dictation feature isn’t available.

• iOS

Sophos Secure Email for iOS doesn’t support email encryption such as S/MIME or PGP. Also, Sophos Secure Email for iOS doesn’t support the verification of digitally signed emails. You can view S/MIME-signed emails, but you can’t verify the signature. You might not be able to view emails at all that are signed with a different certificate, such as PGP.

• Android

Sophos Secure Email for Android uses the Firebase Cloud Messaging notification service. This service only works reliably when you set the date and time on the device correctly.

We recommend that you use the automatic date and time setting.

• iOS

Sophos Secure Email for iOS doesn’t receive “New email available” notifications when using an HCL Domino or Traveler mail server.

• Android

Sophos Secure Email for Android doesn’t support the Samsung DeX Pad docking stations or similar devices. The app might stop responding when running in the DeX UI, which the device uses when connected to a DeX Pad docking station.

• Android

Currently, Sophos Secure Email for Android only supports the IPv4 protocol and can’t be used with IPv6 networks.

• Android

When you take a photo and attach it to a new email, you can select the photo’s quality and size. If you select the Original size option, Sophos Secure Email for Android doesn’t send the attached photo.

Select a lower quality.

• Android

On some devices, photos that you take with Sophos Secure Email for Android and attach to a new email are of low quality.

We’ve seen this issue on a Huawei Mate 10 and a Samsung Galaxy Tab A.

• Android

You can’t view PDF attachments that are larger than about 10 MB.

Open the PDF file in Sophos Secure Workspace.

• Android

Some Samsung tablets don’t play the configured alarm for calendar event notifications.

We’ve seen this issue on a Samsung Galaxy Tab 4 and a Samsung Galaxy Tab A.

• Android

When Sophos Secure Email for Android registers with an Exchange server whose SSL certificate isn’t signed by a trusted CA, the app shows a general connection error instead of a more specific error that indicates the certificate issue.

• Android

Sharing an encryption key as explained in the online documentation is currently not possible.

The option is not available at all.

Users can share an encrypted file that is secured with the key in question.
When a user tries to open the file a password prompt for the key appears. After entering the passcode the key is imported accordingly.

• iOS

Adding a Microsoft OneDrive account to Sophos Secure Workspace for iOS is not possible.
When trying to link an account, the login page shortly opens and then disappears again.

There is no workaround available.
The OneDrive component will be removed in a future version of Sophos Secure Workspace.

• Android

Sophos Secure Workspace sometimes shows the OneDrive ID instead of the file name for OneDrive files in Favorites. Also, Sophos Secure Workspace sometimes shows OneDrive files twice after you copied multiple files.

Open the file’s location in the OneDrive view to refresh the information.

• iOS

In rare cases, Sophos Secure Workspace managed by Sophos Mobile becomes unmanaged after an update.

This is caused by a problem with the iOS mechanism used for managing the app. The managed settings are lost.

Install the profile again for the device in Sophos Mobile Admin.

• Android

After an update, Sophos Secure Workspace sometimes shows Dropbox files you added to Favorites with an outline star icon, as if they’re not a favorite. When you tap the icon, you create a duplicate entry in Favorites.

Remove the duplicate entry by tapping its solid star icon in Favorites.

• Android

Some third-party apps can’t open Sophos Secure Workspace files because of permission problems.

Sophos Secure Workspace grants permissions for displaying the file content, but some third-party apps require universal access and thus can’t open the file.

We’ve seen this issue with ASTRO Image Viewer and ES Image Browser.

• Android

When you change a file from the Favorites list in Sophos Secure Workspace and then open it with a third-party app, some apps show an out-of-date version of the file. This issue is caused by the third-party app, which doesn’t notice the change and shows a cached version of the file.

We’ve seen this issue with Android Gallery.

Stop the app and restart it to clear its cache or use a different app.

• iOS

When trying to save a picture or file to Sophos Secure Workspace. the app shortly opens and then automatically closes again.

• Android

Suppose you turn on the Don’t keep activities Android developer setting. In that case, Sophos Secure Workspace might close or stop responding while interacting with a cloud storage provider (for example, when signing in).

As recommended by Google, don’t turn on “Don’t keep activities” during everyday use of the device.

• Android

After an update, Sophos Secure Workspace forgets favorites from a WebDAV provider if the file name contains special characters or spaces.

• Android

When you view or edit office documents (Word, Slides, or Sheets), Sophos Secure Workspace might display some characters incorrectly. You can view the document without issues in other apps.

This issue is caused by a third-party library Sophos Secure Workspace uses. We’ve seen it with specific Samsung and LG devices.

• Android

Suppose you install Sophos Secure Workspace in the Sophos container. In that case, you must update the Sophos Mobile Control app to version 6.1 before updating Sophos Secure Workspace. If you don’t, Sophos Secure Workspace resets the container password and asks you to set a new one the next time you start the app.

• Android

When viewing unencrypted text files larger than about 3 MB, Sophos Secure Workspace might show the content truncated. Also, you can’t edit unencrypted text files larger than about 50 KB.

These limitations are caused by a third-party library Sophos Secure Workspace uses.

• Android

Sophos Secure Workspace shows animated GIFs as static images without animation.

This limitation is caused by a third-party library Sophos Secure Workspace uses.

• Android

When you open large image files with Sophos Secure Workspace on Samsung Galaxy devices, the app might stop responding.

• EAP1

• Switch-Software

VLANs created in the switch local UI are not synched with Central.

Central to switch config sync is allowed, but the reverse sync is not available currently.

User common observation:

I have three VLANs in my switch, but Central does not show them correctly.

• Switch-Agent

Problem Statement:

High latency when pinging switch management interface. This latency is isolated to only management plane.

Note : This does not impact the user plane traffic where the user traffic is managed.

• EAP1

• Switch-SDK

The ping response time from the Sophos switch shows a higher latency compared to XG/XGS. This latency is seen even when we try to ping switch management IP from any directly client connected to switch.

There is no issue with the data plane traffic i.e. When we ping one host from another host both connected via same or different switch.

• EAP1

• Switch-SDK

The uplink identification intermittently goes away in the local GUI even though the gateway and Internet are reachable from the switch.

• 2023.16.MR3 (Firmware + Agent): Australia

• Switch-SDK

On the local switch GUI, when you click the SSL key import reset button an 'Unknown error' is displayed instead of 'Applicated the configuration.'

• EAP1

• Switch-SDK

[ Intermittent issue ] When moving an uplink cable from one port to another, sometimes it might take more time for the uplink tick to come, even in the local UI. Under these circumstances, the port status event is sent, but the uplink status moves to 0; after a few seconds, the uplink status changes in the local UI, but, at that time, no events are sent to the Central UI.

The faulty status won’t change until the user will update something or a port refresh event will trigger the uplink state refresh on Central UI.

• 2022.36.Central

• Cloud-Backend

Switch Firmware (01.2.1091) will not synch locally created LAG into Sophos Central configuration.

Any locally created LAG interface needs to be de-activated locally and re-created in the Central UI.

• Cloud-UI

The Switch alert counter doesn’t show beyond 100 from switch list page.

Whenever there unread alert count number increases beyond 100 then UI doesn’t get increment. However alerts continue to generate and get updated in Central alert page. This is just alert counter increment issue but functionality will continue to work.

Switch alerts in summary page is limited to a count of max 50.

When there is the 51st alert for a switch, the admin doesn't get notified from the Switch inventory page/Switch details page. The count remains 50. However new alerts ( 51th ) will be displayed on the Central alerts/Dashboard page.

If admin acknowledges the previously received alerts then the count will reduce ( New alert no. = 50 - no. of alerts acked ) and new alerts count will increase thereafter. If admin doesn't Ack the alerts and just reads from the dashboard, the alert count on the inventory page will reach the max of 50 and will never show additional alerts. Those alerts are still visible on the Central Dashboard page.

Whenever unread alert counter reaches to 100, switch list page doesn't show further incoming alert count. In this case admin can view the latest alert from Central dashboard - Alert section and view the latest/all the unread alerts. This section will list alerts beyond hundred count.

Sophos Switch must be able to reach the following FQDN domains in order to successfully register the switch:

sophos.jfrog.io
jfrog-prod-use1-shared-virginia-main.s3.amazonaws.com

Using SSL/TLS Description will cause the connection to fail due to certificate chain handling, as a result, the decryption must be disabled on appliances between the switch and the internet or the domains added to exclusions on those appliances.

Note: Refer additional info added in comment section

• SUM 4.309

• Basesystem

Unable to schedule SUM updates from the Management > Up2date section past 31/dec/2019.

Inspect the year select element in your browser and change any year to 2021 in the source. Select that year and click save.

• SUM 4.309

• Accd

• SUM's ACCD service port 4433 only accepts weak ciphers that fail the PCI compliance check.

• SUM offers all the ciphers which don't support 'Forward Secrecy(FS)' and are considered to be weak ciphers.

• We don't have any plans to fix this issue. 

• For security hardening and as a workaround, UTM's should be accessing the SUM locally or through a VPN only. The SUM access from the direct external network should be blocked. 

For security hardening, UTM's should be accessing the SUM locally or through a VPN only. The SUM access from the direct external network should be blocked.

• SUM 4.309

• WebAdmin

Pushing URL filter list with 1000+ URLs may not work in all cases.  On the UTM side they will appear all gibberish and will not apply to web traffic. 

 Note this may not affect every web filter policy over 1000+ URLs. It is possible to have some that are over 1000+ and not have the issue.

Patch is available through support

• SUM 4.309

• Basesystem

When importing a web exception from UTM into SUM that has the "Refer to Sandstorm" options ticked a "Syntactic object verification" error is displayed

Temporarily disabling the "Refer to Sandstorm" from the exception should allow the exception to be imported

• SUM 4.308

• NoRelease

• WebAdmin

After activation of IPv6 (on UTM), SUM deployed IPv4/IPv6 Network Objects will have a placeholder icon on Webadmin.

• SUM 4.302

• Accd

In some cases the object import from a gateway via the Gateway manager fails.
If this happens you see one of the following messages:

"The system encountered an internal error. Please contact your administrator if the issue persists".
"syntactic object verification failed"

Those messages appear if a not fully qualified hostname is used, like e.g. Testsystem10.

use a fully qualified domainname as hostname

• 2.3.4-5 ( CWIFI MR Release )

• AP Software

Due to concurrent instance changes for Central, there could be a requirement that the access points will require a manual restart for a successful firmware upgrade if the instance change and upgrade have happened at the same time. Please note that during this time, do not interrupt the upgrade process. Kindly wait for 30-40 minutes before attempting a manual restart, and avoid interrupting the upgrade process. After the specified duration has passed, one can proceed with a manual reboot.

Restart the Access point manually after waiting for 30-40 minutes

• EAP-3

• Edimax-FW

The AP6 will send IPv6 router advertisements to all wireless clients when multiple Virtual Access Points (VAP) SSIDs are defined. This results in all wireless clients showing multiple IPv6 addresses in the wireless network adapter.

• UI

If the central account is hosted in new regions, the Central Wireless Product is unavailable, and there are no plans to make it available in the new regions. When customers create an account in central, in a new region, they will face a message describing which products are available. A warning message describing a wireless product does not yet have a plan or date for when new regions will be supported.

• EAP-2

• AP-Firmware

If you configure an AP6 SSID policy using special characters (BS!@#$%^&*) and have enabled Captive Portal, the SSID policy will not be applied to the AP6 access point correctly and the Captive Portal may not work correctly.

If you have a requirement to use the Captive Portal with the AP6 access points use an SSID that does not contain special characters.

• EAP-3

• AP-Firmware

For the AP6 access points, when setting the channel bandwidth explicitly to Auto on the 2.4GHz radio, wireless clients will only negotiate on the 20MHz frequency and not the 40Mhz frequency.

If there is a need to have wireless clients on the 2.4GHz radio negotiate to both 20MHz and 40MHz frequencies, the channel bandwidth must be set manually to 40MHz.

• EAP-3

• AP-Firmware

For the SSID that is configured with Captive Portal on the AP6 access point, that interface will provide access to the local GUI management interface.

• GA

• Cloud-Backend

If a wireless client is connected to an APX access point and then roams or moves to an AP6 access point, then the wireless client details will still show on the APX device tab within Central and not the AP6 device details tab.

• EAP-3

• Cloud-Backend
• Cloud-UI

When an SSID is configured with Captive Portal and the authentication type as password schedule. Wireless clients connected to that SSID do not show up in the SSID<

• EAP-2

• AP-Firmware

When the AP6 is configured to use an external Radius server. The Radius re-authentication does not appear to be working if the wireless user’s session times out.

• GA

• AP-Firmware

After the firmware upgrade is complete, we have seen intermittent issues where the AP6 access point does not auto reboot when configured with 10 or more SSIDs. From Central, the access point will show as offline and wireless clients may be unable to connect on any band.

The AP6 access point may recover in approximately 15 minutes after the firmware upgrade was completed or a manual reboot of the access point will be required.

• GA

• AP-Firmware

When you create an SSID profile on the AP6 local GUI using the DD/WW/MM password feature and 802.11r, some of the mandatory settings are left blank which can cause the AP6 to reboot.

If the mandatory fields for 802.11r are filled in properly the reboot will not happen.

• GA

• AP-Firmware

In certain scenarios, we have seen the AP6 interfaces intermittently reset. This causes the access point to not receive an IP address assignment through DHCP and wireless clients may fail to connect. This issue seems to happen when the Spanning Tree Protocol (STP) is enabled on the AP6 access point.  

From the local GUI on the AP6, go to the STP Management tab, and disable STP under Network Settings.

• EAP-2

• AP-Firmware

When enabling the Proxy ARP from Central, the underlying functionality is working as expected, and the Proxy ARP setting does get enabled successfully. However, the output of SSH command show status network proxyarp is ProxyArp Disable.

• GA

• AP-Firmware
• Cloud-Backend
• Cloud-UI

If you try and apply an AP6 SSID policy from Central Wireless with Band steering and MAC filtering enabled, the MAC filtering will not apply to the AP6. In Central, the MAC filtering will show as None.

Disable band steering if you have a requirement to enforce MAC filtering on the AP6 access points. From Central Wireless go to the SSID<

• 2.3.4-4 ( CWIFI MR Release )

• AP Software

Due to an SSL error, the user can not log in to the network with social login credentials. We found that TLS1.2 is not available in the AP100 device.

• UI Design

Sophos Central Wireless Captive Portal page supports only the English language. Some elements will remain in English after the language is changed.

• Leibniz 2.3.2

• UI

Currently there is a limitation which leads to the issue that only the first 50 entries will be exported to CSV irrespective of the number of clients.

Development threads this as a feature request and will address it in future releases. But there is no ETA yet for this.

N/A

• Cloud Platform

The connection of the captive portal page delivered by the access point is secured by a self-signed certificate.
Most browsers will deliver a warning message about this.
Some browsers allow the user to override this warning message and proceed with the connection to the captive portal page.
Other browsers do not allow this, making it impossible for the user to access the captive portal page.

You may try with another browser which would provide you an option to proceed further.

• Leibniz 2.3.0

• AP Hardware
• AP Software

Following AP models might brick when a firmware update is interrupted due to a power loss: AP 15,15C,55,55C,100,100C and 100X.

1.Making sure that there will be no power outage during the upgrade process.
2.If a power outage were to happen and AP's get bricked, The recovery process is very simple, by using the below URL the recovery tool can be downloaded and the process is also explained on the same page - https://support.sophos.com/support/s/article/KB-000039314?language=en_US
P.S: After recovery, the previous config will be retained so the AP can be used straight away.

• Leibniz 2.2.0

• AP Software

Wireless client connected on Sophos AP/APX managed by Sophos Central Wireless might able to access more data then define on voucher.

Sophos AP/APX sends period update of data usage on voucher to Sophos Central at every 4.5 minutes. In worst case user may get free access to internet for maximum 4.5 minute over mentioned 'Access time/Data Limit' on voucher.

• Leibniz 2.2.0

• AP Software

Devices fail to disconnect from the AP when the Connected SSID is removed from the AP.

Clients like Macbook Air, Android Phone, Dell laptop with Linux are still showing as connected to the AP when connected SSID is removed from AP page.

On the clients WiFi page, it still shows the device as connected and with an connected IP address.

Disconnect the client.

• Leibniz 1.16.0
• Cloud_2018.22

• UI

Attempting to filter connected clients by Vendor only works for the first 8 characters entered. If more than this are entered into the filter then 0 results are returned.

Significant improvements are planned for the filtering in Central Wifi later in 2019 at which point we expect this behaviour to be resolved

• Leibniz 2.0.0
• Cloud_2018.28

There is no work around for this at the moment. Dynamic and Sync security should not be enabled on the same SSID.

• Cloud_2018.28

• UI

Sync security feature is not supported for AP platforms but user can edit the SSID assigned to the AP platforms and can enable the sync security feature.

This can create a issue in mixed platform environment where the SSID is part of both APX and AP platforms in a network. There would be different behavior when the AP roams from APX to AP platforms.  

There is no work around for this. User should not enable the Sync security on a SSID which is assigned to AP platforms.

• AP Software

SSIDs are not getting broadcasted on 5GHz when mesh is established between APX and legacy AP platform.

Steps:

This is a known limitation.

• AP Software

Usage graphs are only updated every 20 minutes
Steps:

lient details including Usage graphs are shown and updated every 20 minutes..

• Leibniz 2.0.0

• AP Software

Sometimes Current Network(SSID) under Accesspoint->Clients-> is displayed wrongly. Current Network info does not get updated immediately in Cloud UI , so there could be entry of previously connected SSID instead of current one. It takes around 4 to 5 minutes for the proper information to be updated under clients page.

There is no workaround for this.User has to wait for around 5 minutes from the time clients gets connected to the SSID for the proper UI update under Accesspoint->Clients->.

• Leibniz 2.0.0

• AP Software

No workaround for this. In all the APX platform if reset button is pressed for about 8 to 10sec APX goes for reboot and if the reset button pressed for more than 15 sec it goes for config wipe out.

• AP Software

This in case where MacOS has both Mobile SMC and Endpoint, If Mobile Says "Red" and the Endpoint says "Green", the Status keeps on toggling so is the change in clients functionality.

There is no workaround for this. MacOS should have either Mobile SMC or Endpoint software not the both.

• Leibniz 2.0.0

• AP Software

Refreshing the page again will allow the access of Sophos friendly white listed URLs.

• Leibniz 1.15.0

• AP Software

When a client roams from one AP to another, clients MAC entry will be present in old AP as well as in the new roamed AP in UI ( under Accesspoint->Client page). Ideally the client MAC entry should be present only in new roamed AP and entry in older AP should be removed when it roams to new AP.

There is no workaround for this. Client MAC entry in older AP will be removed after 5 minutes and there will not be any effect on AP functionality. This is only a UI issue.

• Cloud_2018.03

• Cloud Platform
• UI

Under clients page when we search for client using first 2 bytes Mac address , duplicate entries of the same client can be seen.

Use 3 bytes or more of the clients Mac address in search option under clinets page.

Currently, background automatic channel selection is not working. This means that an AP will not switch a channel even if it becomes too crowded or has too much interference.

To make sure that MESH works between APs, you need to ensure that the APs which should be part of the MESH network are broadcasting on the same channel and use the same channel bandwidth. Manual channel selection is highly recommended.

As we'll be shipping frequent updates, we would recommend to schedule firmware updates to happen daily or weekly. If you set it to monthly you might be missing out for a long time!

See https://community.sophos.com/sophoswireless/b/sophos_wireless_blog/archive/2016/08/10/manual-action-required-for-mesh-networks-in-upcoming-ap-firmware-release-1-3 for details.

This is a one-time effort and is not needed for future releases. There won't be a fix for this.

• connect the repeater AP to an ethernet connection

• reboot/power cycle the AP

• wait for the AP to have the correct firmware applied

• disconnect the repeater AP from ethernet

• power cycle the AP

The AP firmware that is on UTM <= 9.404 has firmware that does not have the reliability improvements that we've added to the firmware update process in later firmware releases.
This means that the firmware update has a higher chance of failing and rendering the APs non-functional.

Please make sure to not unplug an AP after it has been registered by the Cloud until it is shown as online in the Cloud.

• AP Software
• Cloud Platform
• UI

Due to an UI issue, whenever you try to register more than one AP in the Wizard, the UI might show an error even though the registration works. Unfortunately, this affects a common workflow: a new customer wants to set up multiple APs in one go.

• UTM 9.7 MR7 (9.707)

• Web

When using services that test network speed for individual devices, results may indicate lower than expected bandwidth when web filtering is enabled. This is generally due to the way that traffic is received, scanned, and forwarded by the UTM’s web proxy and the need to ensure that resources consumed by a single connection does not impact resources available for other traffic on the network. It does not represent an overall limit on the bandwidth that can be handled by the firewall – under normal use conditions, the UTM handles multiple parallel connections from different endpoint devices which allows parallelization of processing and allows the full bandwidth of the network connection to be used.

• Authentication Clients

An issue was found where the existing version of the Sophos Network Agent is using an older version of the Google API’s. This prevents the Sophos Network Agent from being downloadable for devices running the latest version of the Android OS. The Sophos Network Agent will continue to function on devices running the older version of Android OS.

• UTM 9.7 MR11 (9.711)

• Wireless

Roaming between APX and AP models is not supported

Legacy AP to APX and vice versa roaming won’t work as its not supported due to different driver constraint.  

• UTM 9.4 MR2 (9.404)

• Email

The pop3 mailaccount bindings will not store correctly to the database if no prefetch server is configured.

As a side effect, a user will not be able to release items from the quarantine if no prefect server is specified.

• UTM 9.4 MR2 (9.404)

• WAF

Non-standard Webpages Not loading With WAF .

If there any encoded slashes in the URL responsible for Loading the Web pages those URL would not load and are replied with 404 by WAF although the resource exists on the backend server .

 The signs for identifying such an URI is it contains slashes in encoded format (%2F)

The Apache directive AllowEncodedSlashes is set to No by default for security reasons. This means Apache will reply with a 404 to every request containing encoded slashes. Setting the parameter to NoDecode is not an option since that setting is not compatible with mod_proxy since it would result in double encoding .

The reason why the endcoded slashes are not allowed is that you can access locations that were otherwise restricted. E.g. if you have a location configured for /something on example.com and you access example.com/something%2F..%2Fadmin, you can reach a location that might have no site path configured in WAF. This is for setting AllowEncodedSlashes to yes.

More information would be at

https://httpd.apache.org/docs/2.4/mod/core.html#allowencodedslashes

• UTM 9.35 MR2 (9.353)

• Email

Recipient Verification is set to verify recipients in Active Directory and messages to non-existant recipients are not rejected as expected.

After you confirm that recipient callout works with port 3268 and without SSL you could try the following:

In WebAdmin create a "New network definition" in Definitions & Users >> Network Definitions >> Network Definitions tab. Set its type to "DNS Host" and enter the DNS hostname for the Active Directory server. After we click on the Save button we can use this definition with the Authentication Server in Definitions & Users >> Authentication Services >> Server tab.

• UTM 9.4 MR6 (9.409)

• WAF

Webserver protection is only warning on SQL injection instead of blocking.

reverseproxy logs will show ModSecurity: Warning message and does not block the connection

This was caused because the following where added to the skip filer rules list
981203, 981176, 981204

These rules are need to decide if the SQL inject should be blocked, because they are not done the SQL inject is not blocked.

• UTM 9.35 SR3 (9.355)

• Email

On UTM quarantine directories are sycned across all nodes. Any e-mail quarantined on a node is synced to the node directory across all nodes - this is valid also for "RESERVED" nodes.

Directory structure:
spool/quarantine//

Spool directory:
/var/chroot-smtp/spool

E-mails on HA systems are by design not automatically syned if there is a failover. To retrieve e-mails of a failed node the administrator has to copy the e-mails manually.

Copy e-mails from the failed to the current node (ID):
spool/quarantine// to spool/quarantine/

After this restart the SMTP:
/var/mdw/scripts/smtp restart

• UTM 9.4 MR8 (9.411)

• Email

The logs show the following error message
2017:03:03-18:59:57 example-utm exim-in[8500]: 2017-03-03 18:59:57 1cjx77-0002D6-0E spam acl condition: cannot parse spamd output

This issue is being cause because the spam lookup module is failing to connect to the lookup servers

• UTM 9.5 SR1 (9.504)

• Email

Is it expected behaviour that the retry time includes the time a mail was in quarantine

If a mail was moved to quarantine and was released later the mail server rejects the mail with a temp error 421.
Instead of a retry the UTM logs "retry timeout exceeded" and sends a bounce message to the sender.

• UTM 9.5 SR2 (9.505)

• Email

When an email is sent with an attachment and that attachment has space then # sign the SPF truncates the name of the attachment in the encrypted pdf. The attachment cannot be opened

example file name
"Test #1.pdf"

In the pdf it will say 'Test' you cannot open or save the attachment from the pdf when this happens

PDF meta XML parsing of "#" character after space is not supported by pdf utility used for SPX

• UTM 9.5 MR3 (9.503)

• Email

Domain which have a valid SPF Record could bypass the SPF checking if you send a non-ascii character in the HELO string.

Example : If there is a domain test.com with SPF Record

v=spf1 mx a ip4:X.X.X.X -all

when you try to telnet into the server and try sending a non-ascii character in the helo string the SPF check fails .

system-1:/var/log # telnet test.com 25
Trying X.X.X.X ...
Connected to test.com
Escape character is '^]'.
220 mail.lochem.nl ESMTP ready.
HELO test♥.nl
500 non-US-ASCII characters are not allowed in SMTP commands
mail from: test@abc.in
250 OK
RCPT TO:XYZ@example.com
250 Accepted
^]
telnet> quit
Connection closed.

Reason : When EHLO/HELO is missing or rejected by exim, the spf check will fail due to missing EHLO/HELO.
We already have behavior that rcpt will be accepted in such case of spf fail.

Workaround : Enable Reject invalid HELO/ missing RDNS

• UTM 9.5 MR7 (9.509)

• NoRelease

• WAF

Question: What is the max_processes max setting  for the WAF service ?

There is no max value for this setting. The limiting factor will be how much memory is available, which then depends on how many features are being used on the UTM.

Suggestion is to increase the max_processes value slowly, making sure there's enough memory on the SG to handle it.

• UTM 9.6 MR1 (9.601)

• Email

UTM is expecting an encrypted signed message. It reverts it by decrypting the message first then verifies the signature.
Google Gsuit signs, encrypts and signs the encrypted mail again. The UTM does not know how to process/verify these emails.

• UTM 9.7 MR5 (9.705)

• Email

Which S/MIME versions do we support in UTM?

Sophos UTM supports the following S/MIME versions:

• RFC2311 S/MIME 2

• RFC 2632 S/MIME 3.0 

• RFC 3850 S/MIME 3.1 

Using the command line, you can define which S/MIME version Sophos UTM uses:
The confd option "encryption_utility" can have these values:

smime: Sophos UTM handles S/MIME version 2 (default)
cms: Sophos UTM handles S/MIME up to version 3.1

• UTM 9.7 MR7 (9.707)

• Hardware
• Network

The number of VLANs supported per interface is dictated by the Ethernet Controller used by the NIC.

82599ES based ethernet controllers support up to 64 VLANs.
XL710 based ethernet controllers support up to 256 VLANs, but share forwarding/routing tables with other features and this number is smaller in practice. It ranges between 100 and 180 depending on features in use.

The aforementioned Ethernet Controllers are used by the following NICs:

Other modules may support more or less VLANs.

An indication that the threshold is being crossed is the existence of the following log in dmesg (or kernel.log on UTM):

i40e 0000:04:00.0: Error I40E_AQ_RC_ENOSPC, forcing overflow promiscuous on PF

If the log above is being seen, lower the amount of VLANs per interface and spread them across multiple interfaces until the logs are no longer generated – this should improve performance.

• Auth Client macOS 2.1.0

• Authentication Clients

Issue description :

When MAC books comes up from the Sleep mode its takes 2-3 minutes for the user to be able to browse the internet .

This happens only incase we have a User based firewall rule . It takes CAA around 2-3 minutes to authenticate the user .

Workaround :

The user can disconnect and reconnect the client .

Disconnect the CAA , Reconnect

• STAS

*Question:*  

Do we support Secure LDAP port 636 in the Novel eDirectory configuration of STAS?

Answer:

Secure LDAP port 636 is not supported in the Novel eDirectory configuration of STAS.

• STAS 2.5.1.0

• STAS

STAS Users are getting disconnected frequently if dead entry timeout configured other than zero.

Dead Entry Timeout does not work and it MUST be set to zero. If the value for the dead entry timeout is configured anything other than zero then such behavior encountered and users may get disconnected randomly.

Need to set the dead entry timeout to zero to avoid user disconnection due to dead entry timeout. It is recommended to use the WMI mechanism in STAS for log-off detection.

• UTM 9.7 MR5 (9.705)

• Access & Identity

The HTML5VPN portal offers RDP connections and HTTP / HTTPS connections.
HTTP / HTTPS connections are for accessing a web server.
RDWEB is accessing an RDP server via HTTPS to use apps/clients via RDP.

Acessing RDP systems via an HTML5VPN HTTPS connections is not supported and there is no plan to support this in the future.

To use RDP use an  RDP connection from the HTML5VPN portal.

None

• UTM 9.7 MR5 (9.705)

• Network

In IPv6, the local link address is created and assigned to an interface by Linux system when the interface is brought up. The interface will lose its link local address if it is brought down

This issue will occur in the following scenario:
i) There is ethX (IPv6 global address and link local address) and ethX.VLAN and both of these are up
ii) A new global IPv6 address is assigned to ethX
iii) After assigning newer IPv6 address, then ethX losses its link local IPv6 address

Work-around for this issue