-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for additional Apple Silicon columns in secureboot
table
#8215
Conversation
This adds the additional columns "description", "allow_kernel_extensions", and "allow_mdm_operations". These correspond to the options presented in the Startup Security Utility. Closes osquery#8195
@@ -176,17 +184,120 @@ Status getSecureBootSetting(Row& row) { | |||
return Status::success(); | |||
} | |||
|
|||
Status getAarch64SecureBootSetting(Row& r) { | |||
@autoreleasepool { | |||
// BEWARE: Because of the dynamic nature of the calls in this function, we |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pattern for accessing SPSupport.framework is adapted from the connected_displays table. I think if another table is going to use this it should be refactored out into a helper function.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't been able to test this by enrolling a machine in MDM, but the code seems fine.
Looks okay on my MDM enrolled m1:
|
secureboot
table
Add the additional columns "description", "allow_kernel_extensions", and "allow_mdm_operations". These correspond to the options presented in the Startup Security Utility.
This has been tested across all the possible configurations on a M2 MacBook Pro with Manual MDM enrollment.
Closes #8195