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.
We have made this process significantly easier. Our installer download now includes an MDM profile for permissions and a script for use to deploy the endpoint via MDM. Here are our instructions for how to use these. It is written for JAMF Pro, however the MDM profile and script should work in other MDM solutions.
docs.sophos.com/.../index.html
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.
identifier SophosMDR and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "2H5GFH3774"
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.
Note: Apple has added a new, optional, method of setting authorization of applications for Privacy in Big Sur with MDM. This new method replaces an existing true/false option with a string value option instead. Here is the Apple article on it: https://developer.apple.com/documentation/devicemanagement/privacypreferencespolicycontrol/services/identity Allowed is the normal method of setting permissions, however as of Big Sur, Apple allows you to instead use Authorization. Our detection for permissions has been configured for the “Required” property (which isn’t actually required if you have Authorization instead). If you can set your MDM provider to use the Allowed True/False (Boolean) setting, it should work without any issues. To check if this applies to you, open the .mobileconfig file in a text editor and search for Sophos. Check if you see - <key>Allowed</key><True/>, or <key>Authorization</key><String>Allow</string>. If it is Authorization, this applies to you. We do recognize that there is a move to this alternate form, and as such, we have made an improvement, coming out in our 10.1.3 release in July, to detect both versions. Until this releases, we recommend using the Allowed True/False style privacy permission setting for Sophos processes.
The same profile configuration can be used.
Alternate method
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
Sophos Central MDM Configuration
How to Configure JAMF Privacy Preferences for 10.15 Compatibility
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:
This popped up again this week. All setting via KB article does not fix. Also created a Config Profile for JAMF using PPPC Utility. No joy! All of my Catalina users are experiencing the issue. Sophos Endpoint v10.0.1
We are getting the same thing. Previously, this was not alerting. We have all the necessary components whitelisted with a PPPC config profile in jamf .In the notes for the latest release, the say The notification "Full disk access required" that asks the user to grant Sophos processes full disk access may be re-triggered but offer no solution for getting rid of it.
http://downloads.sophos.com/readmes/savmosx_10_cld_rneng.html
Created a support ticket with SOPHOS, which was of little help. They did not fully read my case and suggested the very thing I had already implemented. Annoying as ##@$%@
Same here.
Just received something from SOPHOS. But, its not something I can do because I am not a SOPHOS Admin.
We can only review 1-2 machines per case to see what exactly is still needed. Please run SDU log gathering tool directly from Central on one of the machines using steps in the article: https://support.sophos.com/support/s/article/KB-000038603?language=en_US
After I receive the logs and send you back the confirmation of receipt email, based on the technical severity and complexity of the case, please expect an update within 1 business day.
At any point you can call on the support line 1 (888) 767-4679 and we will start helping you right away over a remote session.
Please also confirm that the Central dashboard remote assistance is enabled:
I will provide the same reply in the support case, but here is what needs to be done:
In Sophos version 10.0.1 both the Live Response and MDR have to be approved, or you see the pop-up (even if you don't have the license).
Solution: The admins will have to add 2 more lines via Sophos MDM, Jamf or other MDM solutions:
This macOS 10.15+ Security Permissions Required KB will also show all the components required to be added to the Full Disk Access in MacOS.
Additional resources:
Sophos KEXT files for Mac explanation: https://sophos.lightning.force.com/lightning/r/Knowledge__kav/ka03Z0000000FNGQA2/view
Terminal command to list all Sophos kext files: kextstat | grep Sophos
MacOS location and files required to be listed under MacOS System Preferences/ Security&Privacy/Full Disk Access: /Library/Sophos Anti-virus
SophosAutoUpdate (Enterprise Console managed only)
SophosCleanD
SophosScanAgent
SophosServiceManager
Sophos Endpoint UIServer (Central Managed only)
SophosLiveResponse (Central only)
SophosMDR (Central with MDR only, from /Library/Sophos Managed Detection and Response)
Sophos Diagnostic Utility (from /Library/Sophos Anti-virus/tools/)
Hope that helps!
The additional lines you suggest adding do not make sense, they are the same. I added one of them. No change.
@Matthew Hegge
been working on this issue since last week. I added the two bundle IDs and code requirement per Sophos to my Jamf PPPC payload config and still not working. BTW the code req for SophosMDR should be:
identifier "com.sophos.SophosMDR" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "2H5GFH3774"
But I tried already and still not working. Sophos thought there was a white space in their code requirement for SophosMDR prior to 11/13 afternoon in this KB but even the corrected code it still not working.
My thought is that 10.0.1 broke something that is now causing this re-trigger of Full Disk Access. Here their release notes for 10.0.1 essentially confirming such. I asked for when 10.0.2 will come out in the hopes they are aware and working on fix but no reply from them yet.
If anyone finds solution please post.
We have the same issue, which caused all our machine to flag to users that they need to make changes under 10.0.1 I raised this to support who just pointed me back to this page.
We're having the same issue. Another item on my list of reasons to move away from this blighted product.
Waiting for an update on the newer version. Nowthing ths far has cured the issue on Catalina or Big Sur