SOPHOS/SIP error kext rejected due to insecure location

Hello World!

I have a macbook running MacOS 10.13.6. I installed SOPHOS home premium on the system. The SOPHOS shield which should be all black is orange and when I click on it, it indicates that the system is not protected for any of its features such as virus scanning, web filtering, etc, etc. I found the following errors in the log files:

kext rejected due to insecure location <Hexadecimal Location> {url = "file:///Library/StagedExtensions/Library/Extensions/SophosFileMonitor.kext/", ID = "com.sophos.kext.sfm"}

kext rejected due to insecure location <Hexadecimal Location> {url = "file:///Library/StagedExtensions/Library/Extensions/SophosFileProtection.kext/", ID = "com.sophos.kext.oas"}

kext rejected due to insecure location <Hexadecimal Location> {url = "file:///Library/StagedExtensions/Library/Extensions/SophosWebProtection.kext/", ID = "com.sophos.kext.swi"}


If I turn off SIP (csrutil disable) from safe mode and then boot the system, SOPHOS works with no issues.

The wonderful tech support at SOPHOS told me to completely reinstall my system starting with a fresh load of the OS to correct this issue.


I think this is a permission thing with SIP and the file locations? Amy help or suggestions on where to look or how to fix this would be greatly appreciated.


Respectfully;

Mark K.

MacBook

Posted on Dec 23, 2018 10:10 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 23, 2018 9:43 PM

Well ladies and Gentlemen:

I was able to fix this issue on my own. I did a comparison of permissions between a working MacBook and the one having issues. On the working MacBook under /Library, there is a sub-directory called StagedExtensions. On the working MacBook, the permissions are as follows:

drwxr-xr-x  4 root  wheel  restricted  128 Dec 10 03:45 StagedExtensions


On the MacBook that was having the issue, the permissions were:

drwxr-xr-x  4 root  wheel  -  1027 Dec 22 11:45 StagedExtensions


I booted the MacBook into recovery mode and disabled SIP (csrutil disable).

I then Booted the system and logged in as Administrator. I changed to /Library and ran the following command:

sudo chflags -R restricted StagedExtensions


I then booted the MacBook into recovery mode again and enabled SIP (csrutil enable).

I then Booted the system and logged in and all is well, Sophos is working correctly.



I know this solution does not answer the question as to why this was happening on this MacBook in the first place, but it is up and running with Sophos and no errors!


I want to thank those of you who responded and wish you all a Very Merry Christmas!

Respectfully;

Mark K.

Similar questions

21 replies
Question marked as Top-ranking reply

Dec 23, 2018 9:43 PM in response to Batman-15

Well ladies and Gentlemen:

I was able to fix this issue on my own. I did a comparison of permissions between a working MacBook and the one having issues. On the working MacBook under /Library, there is a sub-directory called StagedExtensions. On the working MacBook, the permissions are as follows:

drwxr-xr-x  4 root  wheel  restricted  128 Dec 10 03:45 StagedExtensions


On the MacBook that was having the issue, the permissions were:

drwxr-xr-x  4 root  wheel  -  1027 Dec 22 11:45 StagedExtensions


I booted the MacBook into recovery mode and disabled SIP (csrutil disable).

I then Booted the system and logged in as Administrator. I changed to /Library and ran the following command:

sudo chflags -R restricted StagedExtensions


I then booted the MacBook into recovery mode again and enabled SIP (csrutil enable).

I then Booted the system and logged in and all is well, Sophos is working correctly.



I know this solution does not answer the question as to why this was happening on this MacBook in the first place, but it is up and running with Sophos and no errors!


I want to thank those of you who responded and wish you all a Very Merry Christmas!

Respectfully;

Mark K.

Dec 23, 2018 5:06 PM in response to Batman-15

Hello,

I assume that if you’ve turned off SIP, you would be willing to try some command-line utilities. Try the following:

ls -laO /Library/StagedExtensions/


The result should look like this:

total 0

drwxr-xr-x@  3 root  wheel  restricted   96  3 Nov 16:13 .

drwxr-xr-x+ 67 root  wheel  sunlnk     2144  3 Nov 16:10 ..

drwxr-xr-x   3 root  wheel  restricted   96  3 Nov 16:13 Library


If it doesn’t, you can try the following to fix it (while booted from recovery):

chflags -R restricted /V*/*/Library/StagedExtensions


I found this information here: https://stackoverflow.com/questions/50897253/macos-kext-with-valid-signature-rejected-after-2nd-installation-high-sierra

My results aren’t quite the same as listed in the link. I strongly suggest a backup before doing anything.


If you don’t have that restricted flag (and after turning off SIP, who knows what you have) then I think it might be a good idea to follow Sophos’ advice and do a wipe and reinstall. Something looks fishy about your system.


That being said, I don’t disagree with the advice you received so far. The macOS operating system already includes multiple layers of malware protection. You don’t need anything else. But if you ask anyone in the security industry, they will tell you the exact opposite. It has become trendy in certain circles to proclaim Apple’s malware protection as being a complete failure. You can see some of that misinformation right here in this thread. Don’t fall for it.

Dec 23, 2018 2:00 PM in response to Batman-15

No. You don't need Sophos, or anything even remotely like it. There are no actual viruses to stop in the Mac OS. There are plenty of Trojans (software you have to install, knowingly or unknowingly) that blow right past all AV software since there's nothing to detect until it's already been installed. Even then, most don't notice anything is wrong.

Dec 23, 2018 3:32 PM in response to Kurt Lang

Hi Kurt, I am a senior information assurance officer and a CISSP. There are viruses and malware that affect the MacOS. Please see the information provided in the link below my response. You are correct in that most malware and viruses have to be introduced into a Mac via users actions. But that is true in most cases with Windows systems as well. One of the issues in a heterogeneous environment is that Macs can act as a transport device for windows viruses to move through your network and systems. I have Dealt with this issue with the government for many years.

Thanks for your feedback and help.


[Link Edited by Host]

Dec 23, 2018 3:34 PM in response to Batman-15

Any of us can say we are an expert in any domain. Please name one virus out in the wild that can run on a Mac.

Macs do not act as transport devices for Windows devices. Windows virus' can be included in emails etc sent to Mac users and then the email can be forwarded to a Windows user but it is the responsibility of Windows users to not send virus' and then to defend against them. It is not the responsibility of Mac to intercept Windows virus'. Why should Mac users use system resources and tools that provide no benefit while potentially harming a Mac trying to protect Windows users?

Dec 23, 2018 4:56 PM in response to Batman-15

No, I am interested in educating myself. as demonstrated by my question to you. You are not as interested by your refusal to learn that running third party anti virus apps on Macs is of no value, provides no benefit, and uses system resources needlessly. And in fact these third party apps may cause problems on a Mac.

You came here seeking assistance and you have been provided some. But because you have a preconceived erroneous idea of security of Macs from virus' you refuse to accept what you are told.

Dec 23, 2018 5:18 PM in response to Batman-15

I am a senior information assurance officer and a CISSP. There are viruses and malware that affect the MacOS. ...
Macs can act as a transport device for windows viruses to move through your network and systems. ...
try googling Mac iOS malware and do a little research on your own

There are no viruses that affect macOS. There are a handful of crude malware apps, but they have been long-since blocked by Apple and are no threat to Mac users. The idea that there is some kind of “Typhoid Mac” effect is ludicrous, regardless of how many times people from the security industry repeat it. It is Windows users’ responsibility to keep their machines free from malware. Finally, I’m not sure what a “Mac iOS malware” is. Macs run macOS and other devices run iOS. Running them together like that pretty much eliminates any potential for credibility.

Dec 23, 2018 5:21 PM in response to BobTheFisherman

As I stated earlier, in my experience and the experience of others that I’ve worked with, Macs have and can be infected (Crossrider) and also be the point of transfer for malware to other systems. In my current position, I do not have the luxury of not running antivirus software. Your help is simply not to install the software. That is not an option. This software has been installed successfully on other Macs without this issue. I am seeking expert help with understanding why this particular Mac is reporting the errors listed above and how to correct them. Thank you for your input, but I still need a technical solution to this problem.

Dec 23, 2018 7:25 PM in response to Kurt Lang

Understood. I already stated much earlier in this thread that most malware has to be introduced into Macs (and Windows systems) via user action. And yes, it is upon the user to be wary and not choose to run or install suspicious software on any computer system. But no matter how careful you try to be or how much you try to educate your users, sh*t happens!


In closing, I am still looking for a technical solution to my original problem other than reinstalling the entire system and applications.

Dec 23, 2018 7:54 PM in response to Batman-15

But no matter how careful you try to be or how much you try to educate your users, sh*t happens!

Absolutely! Can't tell you how many times I've read about, and heard IT people complain about the users in almost any company. No matter how many memos they put out telling staff NOT to open unexpected attachments they receive, whether they recognize the sender's name or not, they do it anyway.


The human element is, and always will be the main problem. Both the crooks who create them, and the users who continue to fall for them.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

SOPHOS/SIP error kext rejected due to insecure location

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.