County librarian Macs on macOS 12 and later install the Carbon Black Cloud sensor, but the sensor stays degraded until a system extension is approved. What should the administrator push with the sensor?
Select an answer to reveal the explanation.
Short Explanation
Modern macOS treats extra kernel-level helpers like a locked staff door—MDM has to badge them in or they sit in the lobby. A UEM system-extension and PPPC profile is that badge, shipped with the sensor. Clicking Allow at login, dropping a GI SVM on a Mac, or a host profile will not approve the extension.
Full Explanation
Carbon Black Cloud sensors on macOS 11/12 and later require MDM-approved system extensions and Privacy Preferences Policy Control payloads. Workspace ONE UEM should deploy those profiles with the sensor so the agent is not left in a degraded state waiting for a user click. Guest Introspection SVMs and vSphere host profiles are NSX/vSphere constructs, not Mac endpoint approvals. An org API key in a login item is not a supported system-extension grant.