mirror of
https://github.com/usnistgov/macos_security.git
synced 2026-02-03 14:03:24 +00:00
FileVault enforcement requires FileVault payload #30
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @phaninder-scalefusion on GitHub.
Summary
FileVault subsettings are not applied if the FileVault payload itself is missing from the MDM configuration.
Steps to reproduce
Operating System version
(macOS 13 / 14 / 15)
Intel or Apple Silicon
Both
Current behavior
Subsettings silently fail when FileVault payload is absent.
Expected behavior
Compliance should either:
Possible fix
Ensure FileVault payload is always delivered with any subsetting.
@phaninder-scalefusion commented on GitHub:
This is regarding the rule “system_settings_filevault_enforce”, which checks whether FileVault is enforced. However, it does not validate against the FileVault payload sent to the device.
Therefore, I suggest adding a note in the description to clarify that this rule does not enable FileVault, so that Admins are aware.
@brodjieski commented on GitHub:
Hello! Which FileVault subsettings are you seeing this issue with? Are there specific rule files that are affected? I want to be able to accurately reproduce the issue so if there is any more additional information you can provide, that would be most helpful.
Thanks!
@brodjieski commented on GitHub:
Ahh, I see. Ok, so we do include the following in the fix of the rule yaml file, however, the guidance does not use this because it also has the mobileconfig_info.
fix: |
NOTE: See the FileVault supplemental to implement this rule.
We will have to move this NOTE to the discussion.