I'm actually using this config profile for pushing system/kernel approval and PPPC control.
Everything looks to be working except for the "System extension approval", it keeps asking for the approval.
It is actually working in macOS Catalina, but I'm not that lucky for macOS bigSur. Any advice?
@alessio.tedesco You are missing some System Extension options in your profile. Having said that, I don't have an answer for you but I'm actively working with both CrowdStrike and Jamf support right now. When I know more I'll post to the following thread.
Thanks @alessio.tedesco Still no dice for me. I mirrored your settings, I believe, and other than some of the order of things which I can't seem to control, I don't think I missed anything. End result, CS is running but I get the update prompt in my last photo.
Client Profiles Pane in System Preferences
Prompt and other information
So i've been doing a lot of work with version 6.14. First thing ... split up your profiles! Make the PPPC it's own, the KEXT it's own, the SysExt it's own and so on... Trust me, your Apple Silicon macs will eventually thank you. I've attached how the System Extension payload should look.
I believe you need to further modify the provided .mobileconfig.
The last two sections don't have the bundle id string defined and instead show "StaticCode" and you need to add X9E956P446 so they look like this:
Worked on Catalina as of this week.
Here's my problem - I have two different profiles, one for Catalina, one for Big Sur. The Catalina profile has KEXT, and the Big Sur does not. Everything is fine and working smooth, except when I upgrade from Catalina to Big Sur. Then, at log in, I get the prompt that system extensions were blocked from launching. Anyone tested the upgrade and figured this out?
I think I found a solution for the "System Extension Updated" pop-up. The configuration profile with all your (good) settings for Crowdstrike needs to be run again. This is very simple solution, but implementing it is the tricky part...
This is how I've done it, looks ugly and it's not that clean, if someone finds another better way to run a configuration profile after policy to install Crowdstrike is run, please share it.
1. Create/modify your post install script for Crowdstrike .pkg installer to include: (this has to be after you run falconctl license ID and falcontctl load)
if [ $? -eq 0 ] then mkdir -p /Library/Application\ Support/JAMF/sample_folder touch /Library/Application\ Support/JAMF/sample_folder/crowdstrike /usr/local/bin/jamf recon fi
2. Create an Extension Attribute (in Settings) that checks if file exists and use this script:
#!/bin/sh if [ -e /Library/Application\ Support/JAMF/sample_folder/crowdstrike ] then echo "<result>True</result>" else echo "<result>False</result>" fi
3. Create a smart group that checks if the file exists using that new Extension Attribute you created and setting the value to true.
4. Duplicate your good Configuration Profile for Crowdstrike and scope it to this new Smart Group.
I'm still testing it but looks like is doing the job...
I have an answer for those like me who got here with a Google search. If you have the "System Extension Updated/Blocked" window (first it's a lie, it's a legacy kernel extension), it's because the BIOS Standard Visiblity is enabled on a Falcon policy. This will not only show up at the sensor installation (on Big Sur and above), but at every sensor update going forward. Note that whatever the end user does, Falcon is still running and working. It just won’t gather firmware data until the kext is approved and the computer rebooted.
The popup won't show up on M1 computers because this firmware analysis feature doesn't seem to exist.
FYI - We are running Crowdstrike at my organisation and we've just been informed that the BIOS visibility settings for any Mac running at T2 chip should be disabled
See extract from Crowdstrike email:
BIOS Visibility is not supported on M-series Apple Silicon (M1)-based Macs.
BIOS Integrity Check is not supported on Macs with T2 chips - which at this point is the vast majority of Mac hardware.
Given the limited percentage of Mac hardware that can take advantage of BIOS Visibility, we no longer recommend to customers that this feature be enabled on Macs.
The BIOS stuff requires a KEXT to work period, no matter the device type or OS. That's the reason it should be disabled as the functionality isn't exposed via system extensions.
The CS guys on mac admins slack highly recommend disabling it, and we've had zero issues since doing that at my org.