PPPC-Utility VS macOS-enterprise-privileges

You will likely further down the road when you have the basics setup need this tool https://github.com/jamf/PPPC-Utility This is a very useful tool to create configs that allows you to deploy app permissions so the end user does not have to allow things. For example you could create a profile that gives Microsoft Teams camera and disk access for sharing files so it does not nag the user to allow it.

For other permissions, check out PPPC Utility from Jamf: https://github.com/jamf/PPPC-Utility

we're currently using Jamf Connect and Intune to enroll our Mac´s. For the privacy settings, we're using the PPPC-Utility from Jamf. Now the question: After applying these PPPC-Profiles the silders (In Privacy Settings) are still turned off, but it seems to work. Is this behavior normal?

Also, if you need them to have admin rights, you can use something like https://github.com/SAP/macOS-enterprise-privileges

> For technically-inclined users, I'm still largely unconvinced of the value of SIP.

Problem is technically-inclined users are the ones most likely to not be running "defense in depth" and therefore susceptible to zero days such as the H.264->code execution discussion earlier this week.

Arguably, technically-inclined users participating in the software supply chain should go beyond SIP and run in Lockdown mode permanently, both on the dev machine and any mobile devices used for MFA, or at the very least self-install SAP's "Privileges" or equivalent that requires a deliberate unlock to act as Administrator.

https://github.com/SAP/macOS-enterprise-privileges

This helps* prevent drive-bys with persistent payloads without the extra attack surface that is commercial AV or anti-malware.

* Helps prevent, not prevents.