Endpoint Standard: How to Verify Sensor 3.1 KEXT Approval

Endpoint Standard: How to Verify Sensor 3.1 KEXT Approval

Environment

  • Endpoint Standard (formerly known as CB Defense): 3.1.x.x and higher
  • Apple macOS: 10.13 and higher

Objective

Verify that the Endpoint Standard kernel extension (KEXT) has been approved on a macOS machine

Resolution

  1. Open a Terminal window
  2. Enter the following to search for the kernel extension according to sensor version:
    kextstat | grep -s com.carbonblack
  3. Verify that com.carbonblack.defense.kext is found:
    0 0xffffff7f828e2000 0x46000 0x46000 com.carbonblack.defense.kext (3.1.0fc8) A0B8D03C-57AD-3516-B3E7-16D8130ICBA3 <78 51 46 24 12 7 5 4 3 2 1>

Additional Notes

  • Secure Kernel Extension Loading was introduced with macOS 10.13 High Sierra. As a result, the KEXT associated with the Cb Defense Sensor must either be manually approved by end users or pre-approved with an MDM profile.
  • When Secure Kernel Extension Loading was first introduced in macOS 10.13.0, it was bypassed as long as the Mac was managed with any MDM profile. Beginning with macOS 10.13.4, MDM management alone is not sufficient. The Cb Defense Team ID and Bundle ID must be added to the profile for KEXT approval.
  • The Team ID and Bundle ID vary depending on the Cb Defense sensor version.
  • Additional required and optional parameters included with MDM profiles are covered in Apple's developer documentation.

Related Content


Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎04-30-2018
Views:
2555
Contributors