Note: This information is provided as-is for the benefit of the Community. Please contact Sophos Professional Services if you require assistance with your specific environment.
This article describes the steps to configure JAMF to allow configure permissions for Sophos Mac Endpoint on macOS 10.15+
Applies to the following Sophos products and versionsSophos Central Mac Endpoint 10.0.0 and above,Sophos Central Intercept X 10.0.0 and above,Sophos Central Device Encryption 1.5.2 and above,Sophos Anti-Virus for Mac OS X 9.9.7 and above
With macOS 10.13, Apple introduced a new security level that required each 3rd party vendor's kernel extension to be approved. This required Team ID to be allowed, also known as the Apple Developer ID.
With macOS 10.15, Apple added a new default behavior that prevented applications from writing to the disk.
The information below covers both topics:
To alert and inform users, Sophos implement a notification popup. The endpoint will check after each reboot (and continuously every 30 minutes) if the system permissions are compatible.
Note: In Sophos for Mac 9.9.5, a notice is displayed if required permissions are not fully enabled. On October 31st, an issue was found where the notice is triggered if the permissions have been added via an MDM profile, as Apple records these in a different location. Sophos is actively working on updating the detection to correct this.
There are 2 steps required to configure compatibility for macOS 10.15.x (Catalina) and below.Note: One additional step is required if you want to apply the profile to a macOS 11 (Big Sur) device.
codesign --display -r - <app path from table above>
The same profile can be used, but the option "Approved Kernel Extensions" needs to be selected. If this is not configured yet, select the "open" button at the center to begin the configuration.
During configuration, 3 kernel extensions will need to be added, as well as the Sophos Team ID [2H5GFH3774]
Note: Please ensure that "Allow users to approve kernel extensions" is unchecked.
Referring to the screenshot above, add the following kernel extensions:
Make sure to save your changes.
The same profile configuration can be used.
Note: Sophos does not guarantee the security of third party applications and they should be used at your own risk.
There is a utility called PPPC Utility on Github which allows you to build a configuration profile for Privacy Preferences. It can be located here: https://github.com/jamf/PPPC-Utility. To use this, follow the guidance on the link, and drag and drop the Sophos items into it.
This profile can then be loaded into JAMF.
Special thanks to MichaelCurtis
How to Configure JAMF Privacy Preferences for 10.15 Compatibility
Sophos Approve Endpoint KEXT
How to make a Sophos Central macOS installation package in Jamf Pro
How to make an installation script for Sophos Central macOS endpoint deployment in Jamf Pro
How to deploy Sophos Central macOS endpoint via Jamf Remote
Special thanks to mscottblake for sharing this!
Within the same Configuration Profile, add a Content Filter payload (this requires Jamf Pro 10.26+) with the following keys and values configured:
Note that the Filter Name can be anything, but it is required.
Once the complete, the payload should look like this:
I have followed the instructions on this article. However, in Big Sur I am still getting the prompts to allow the System Extensions for SophosScanD and SophosWebNetworkExtension. I have a configuration…
Here's my current state of affairs:
Sophos 10.0.4 + Intel Big Sur 11.2.3Config Profile with System Extension + PPPC + Web Filter (no KEXT!)
After opening my MBP lid after sleep, my wifi is connected and I can perform DNS queries - however, I can't browse the web on any browser. All other devices in my household were fine.
This may be due to a Sophos Network Extension located in Applications/Sophos/Sophos Network Extension
When I dragged this to the trash, my browser started working again and Sophos barked at me. After an update - it put it back. I was still able to browse the web.
These are only my initial findings - if anyone else has a chance to confirm - that'd be great.
I am seeing the same thing, all traffic is completely blocked even though i can perform a DNS query... however I've uninstalled Sophos in troubleshooting and I still have no access. So, this system is a brick at the moment. It was a freshly bootstrapped MacBook Air 2019 Intel... we use Jamf, Sophos installed as part of Enrollment process and worked fine until I restarted the computer after installing some software... after that all traffic dead. Not good as I manage a fleet of 330 Macs, but thankfully we have Big Sur blocked on campus... this laptop was going to be the first one given to Faculty with Big Sur. :|
I just had it occur again on a clean install of an older 2013 MacBook Pro Retina, clean install of Big Sur which I did as a test... everything was fine until I rebooted after I told Sophos to update. I've lost network on this machine now... we pay for Premium support so I am calling Sophos now.
I've dropped you a DM asking for more info about this issue that you’re facing.
The exact issue here, only I have about 2200 2017 MacBook Airs to image and redeploy in about a month. Any updates would help. I opened a ticket but I have not heard back yet!
Hi Adam Lalicker,
Thank you for reaching us, Can you DM me the case ID for me to validate and help you follow up the process.