Advisory: Scheduled Cyberoam and NetGenie server maintenance on Saturday March 30, 2019 starting at 14:00 (UTC)

Scheduled Cyberoam and NetGenie server maintenance on Saturday, March 30 starting at 14:00 (UTC). Estimated time to complete maintenance is 1 hour.

A website banner will be displayed on the Cyberoam and NetGenie portal indicating there is ongoing maintenance occurring. This will be shown during the duration of the scheduled maintenance period.

Applies to the following Sophos product(s) and version(s)

Cyberoam UTM with Cyberoam OS

NetGenie

During this maintenance period:

  • Customers may experience issues connecting to the Customer or Partner Portal.
  • Activation and registration of Cyberoam products may be unavailable.

Please follow this KBA for the latest updates and information.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

RESOLVED Advisory: Sophos Central Partner and Enterprise dashboard – Central Mobile not available when managing Customer’s Central Admin dashboard

When a Partner or an Enterprise Admin launches their Central Admin customers dashboard, they may not see Central Mobile unless they have the super admin role for their partner or enterprise admin user.

The following sections are covered:

Applies to the following Sophos products and versions

Sophos Central Admin

Sophos Central Enterprise Dashboard

Sophos Central Partner

Partners that are unable to see the Central Mobile feature when managing their Sophos Central Customers:

  • Check that your Partner or Enterprise Admin user has the Super Admin role applied and then launch into your customers dashboard to manage their mobile devices.

Note: This is a temporary workaround to be able to manage your customer’s mobile devices.

Sophos is actively working to resolve this issue. This article will be updated as more information becomes available.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Advisory: Sophos Central Firewall Manager (SCFM): Devices disconnected and are unable to be added

We are currently investigating reports of XG devices being disconnected in SCFM. Device IP/Domain configuration has been removed and is unable to be added.

Applies to the following Sophos product(s) and version(s)

Sophos Central Firewall Manager

Some customers are unable to manage their XG devices on SCFM.

The problem has now been resolved. There will be residual lingering slowness issue whilst devices are reporting in. This should normalize within a couple of hours.

If you are still having this issue, please log a support case and reference this article.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Advisory: Sophos Central Partner and Enterprise dashboard – Central Mobile not available when managing Customer’s Central Admin dashboard

When a Partner or an Enterprise Admin launches their Central Admin customers dashboard, they may not see Central Mobile unless they have the super admin role for their partner or enterprise admin user.

The following sections are covered:

Applies to the following Sophos products and versions

Sophos Central Admin

Sophos Central Enterprise Dashboard

Sophos Central Partner

Partners that are unable to see the Central Mobile feature when managing their Sophos Central Customers:

  • Check that your Partner or Enterprise Admin user has the Super Admin role applied and then launch into your customers dashboard to manage their mobile devices.

Note: This is a temporary workaround to be able to manage your customer’s mobile devices.

Sophos is actively working to resolve this issue. This article will be updated as more information becomes available.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Resolved – Advisory – Sophos XG Firewall: DDNS updates not working

We are investigating reports of some XG customers experiencing issues with DDNS updates failing when using Sophos as the service provider.

Applies to the following Sophos products and versions

Not product specific

Sophos has resolved this issue.

Any customers still experiencing issues, please raise a support case and reference this KB.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Install Sophos Anti-Virus with On-access scanning provided by Fanotify and Talpa on-access disabled.

This article describes the steps to install Sophos Anti-Virus with On-access scanning provided by Fanotify and Talpa on-access disabled.

The following sections are covered:

Applies to the following Sophos products and versions

Sophos Anti-Virus for Linux

Sophos Anti-Virus for Linux

Sophos Anti-Virus for Linux

In some environments, it is necessary to install Sophos Anti-Virus for Linux without Talpa on-access scanning starting and for SAV to install with fanotify on-access enabled.

The install commands for this are : –

For a Central managed install:

# ./SophosInstall.sh –disableTalpa –disableFanotify=false

For a Sophos Enterprise Console managed install:

# ./install.sh –disableTalpa –disableFanotify=false

After the install, the configuration options used can be confirmed with:

root@ubuntucl5:/opt/sophos-av/bin# ./savdstatus

Sophos Anti-Virus is active and on-access scanning is running

root@ubuntucl5:/opt/sophos-av/bin# ./savconfig disableFanotify

false

root@ubuntucl5:/opt/sophos-av/bin# ./savconfig disableTalpa

true

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Sophos Anti-Virus for Linux: Docker containers support

As containers are becoming more widely deployed on Linux Servers, the need for security is paramount to ensure any running containers have not been injected with malware.

Sophos Anti-Virus for Linux has been enhanced to improve detection of malware in Docker containers using on-access scanning and to improve the way in which detections in Docker containers are presented within the Sophos management consoles. Now, when a threat is identified within a Docker container, the threat report will state the path and hostname of the container. This will be displayed as container hostname=<hostname>.

This article details the addition of support for Docker containers within Sophos Anti-Virus for Linux.

Applies to the following Sophos products and versions

Sophos Anti-Virus for Linux 10

Sophos Anti-Virus for Linux 9

Threat detection within Docker containers has been available since the following versions of Sophos Anti-Virus for Linux:

  • Sophos Anti-Virus for Linux version 9.13.0 and later
  • Central-managed Sophos Anti-Virus for Linux version 10.1.1 and later

For Sophos Anti-Virus for Linux to detect threats in Docker containers, the Talpa on-access driver must be used. The Fanotify kernel interface does not support scanning inside containers.

A recent, supported version of Docker will need to be installed and configured, preferably from the operating system vendor’s package repositories.

The Sophos Anti-Virus for Linux Docker scanning functionality is available on supported releases of the following platforms:

  • Red Hat Enterprise Linux 7 – Server
  • CentOS 7
  • Oracle Linux 7
  • Ubuntu 16.04 and 18.04
  • SUSE Linux Enterprise Server 12 and 15

For more information on Sophos Anti-virus for Linux, take a look at the knowledge base article Endpoint Security and Control: Retirement calendar for supported platforms and operating systems.

From the Docker website:

When antivirus software scans files used by Docker, these files may be locked in a way that causes Docker commands to hang.

One way to reduce these problems is to add the Docker data directory (/var/lib/docker on Linux, %ProgramData%docker on Windows Server, or $HOME/Library/Containers/com.docker.docker/ on Mac) to the antivirus’s exclusion list. However, this comes with the trade-off that viruses or malware in Docker images, writable layers of containers, or volumes are not detected. If you do choose to exclude Docker’s data directory from background virus scanning, you may want to schedule a recurring task that stops Docker, scans the data directory, and restarts Docker.

For more information on what operating systems that Docker support, take a look at its Compatibility Matrix.

Note: In Sophos Anti-Virus for Linux, exclusions; a directory is defined with a trailing “/” so in the above example, the exclusion would be “/var/lib/docker/”.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable for us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Sophos Anti-Virus for Linux: Using mkinstpkg to create a deployment package

In Sophos Anti-Virus for Linux or Unix version 9, the deployment package tool mkinstpkg is already transferred to a new location and is no longer available in the Central Installation Directory (CID).

Applies to the following Sophos products and versions

Sophos Anti-Virus for Linux 9,

Sophos Anti-Virus for Unix 9

  1. Go to the directory /opt/sophos-av/update/
  2. Do one of the following:

    • To create a tar format deployment package called savinstpkg.tgz, type the command ./mkinstpkg
    • To create an RPM format deployment package (Linux only) called savinstpkg-0.0-1.i586.rpm, type the command ./mkinstpkg -r
  3. Note: The filename may vary slightly depending on the RPM setup.

  4. Use your own tools to copy this package to the endpoints where you want to install the Sophos Anti-Virus.

Configuration options can be set when creating the package with mkinstpkg ,such as setting the install package to default to Fanotify instead of Talpa for on-access scanning. The example in this case would be ./mkinstpkg --extra-options="--preferFanotify". Command-line options for mkinstpkg can be seen in page 16 of the Sophos Anti-Virus for Linux startup guide.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable for us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Advisory – Sophos Central Email: Certain characters from Office 365 emails are being rewritten as question marks

An inbound email received from an Office 365 (O365) domain which contains a URL link, will cause Time of Click (ToC) to re-write apostrophes and other characters as question marks.

Emails will still be delivered successfully.

Applies to the following Sophos product(s) and version(s)

Sophos Central Email

Apostrophe (‘) and dash (-) characters are being replaced with a question mark (?) in the email body.

Sophos is actively investigating this issue.

Please review the workaround below and check this article for the latest updates.

Option 1

If you are aware of the URL that will be sent, you can add the URL to the Time of Click allow list. This can be found under Central Email Settings.

Option 2

If you trust the sender of the email, you can add them to your Inbound Allow / Block list under Central Email Settings.

Option 3

Disable Time of Click for the user or group having the issue. This can be done by creating a new policy and only disabling this setting for users that are affected by the issue. This can only be applied to the recipient of the email.

This article will be updated when more information becomes available.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Sophos Anti-Virus for Linux: How to do a manual uninstallation

This article describes the steps to remove SAV for Linux manually in the event that a standard removal does not work or is not possible.

The following sections are covered:

Applies to the following Sophos products and versions

Sophos Anti-Virus for Linux

Sometimes it is necessary to remove SAV for Linux from a Linux server. One reason may be that an initial installation has gone wrong or been corrupted in some way. Before reinstalling, all parts of the original installation must be removed.

The first removal step should always be to attempt removal by running the normal uninstaller:

# /opt/sophos-av/unistall.sh

If this does not complete or will not run for some reason, the following steps can be used to remove SAV for Linux:

  1. Stop Daemons/services.

    # /etc/init.d/sav-protect stop

    # /etc/init.d/sav-rms stop

    # systemctl stop sav-protect

    # systemctl stop sav-rms

    # stop sav-protect (on upstart systems)

    # stop sav-rms (on upstart systems)

    # svcadm disable sav-protect

    # svcadm disable sav-rms

  2. Remove the startup configuration. Note that some of the commands are platform specific, so use the appropriate command for the given Linux/Unix platform.

    1. Remove the systemctl configuration.

      # systemctl disable sav-protect

      # systemctl disable sav-rms

      # rm -fv /lib/systemd/system/sav-{protect,rms,update}.service

      # rm -fv /usr/lib/systemd/system/sav-{protect,rms,update}.service

    2. Remove the Upstart configuration.

      # rm -fv /etc/init/{sav-protect,sav-rms,sav-update}.conf

    3. Remove the SVC configuration.

      # svccfg delete -f sav-protect

      # svccfg delete -f sav-rms

      # svccfg delete -f sav-update

    4. Remove SysV and compatibility scripts.

      # rm -fv /etc/init.d/sav-{protect,rms}

      # rm -fv /etc/init.d/rc*.d/S*sav-{protect,rms}

      # rm -fv /etc/init.d/rc*.d/K*sav-{protect,rms}

      # rm -fv /etc/rc*.d/S*sav-{protect,rms}

      # rm -fv /etc/rc*.d/K*sav-{protect,rms}

      # rm -fv /sbin/rc*.d/S*sav-{protect,rms}

      # rm -fv /sbin/rc*.d/K*sav-{protect,rms}

  3. Remove savscan/sweep symlinks.

    # rm -fv /usr/local/bin/{savscan,sweep} /usr/bin/{savscan,sweep}

  4. Remove man-pages.

    # rm -fv /usr/local/share/man/man1/savscan.1

    # rm -fv /usr/local/share/man/man8/savconfig.8 /usr/local/share/man/man8/savdstatus.8 /usr/local/share/man/man8/savscand.8 /usr/local/share/man/man8/savd.8 /usr/local/share/man/man8/savlog.8 /usr/local/share/man/man8/savsetup.8 /usr/local/share/man/man8/savdctl.8 /usr/local/share/man/man8/sav-protect.8 /usr/local/share/man/man8/savupdate.8

    # rm -fv /usr/local/share/man/ja/man1/savscan.1 /usr/local/share/man/ja/man8/savconfig.8 /usr/local/share/man/ja/man8/savd.8 /usr/local/share/man/ja/man8/savdctl.8 /usr/local/share/man/ja/man8/savdstatus.8 /usr/local/share/man/ja/man8/savlog.8 /usr/local/share/man/ja/man8/sav-protect.8 /usr/local/share/man/ja/man8/savscand.8 /usr/local/share/man/ja/man8/savsetup.8 /usr/local/share/man/ja/man8/savupdate.8

    # rm -fv /usr/local/share/man/ja_JP.UTF-8/man1/savscan.1 /usr/local/share/man/ja_JP.UTF-8/man8/savconfig.8 /usr/local/share/man/ja_JP.UTF-8/man8/savd.8 /usr/local/share/man/ja_JP.UTF-8/man8/savdctl.8 /usr/local/share/man/ja_JP.UTF-8/man8/savdstatus.8 /usr/local/share/man/ja_JP.UTF-8/man8/savlog.8 /usr/local/share/man/ja_JP.UTF-8/man8/sav-protect.8 /usr/local/share/man/ja_JP.UTF-8/man8/savscand.8 /usr/local/share/man/ja_JP.UTF-8/man8/savsetup.8 /usr/local/share/man/ja_JP.UTF-8/man8/savupdate.8

  5. Delete installation directory.

    # rm -rf /opt/sophos-av

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts