- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
Apple File Systems (APFS) in macOS 10.13 changed the way Apple manages FileVault encryption keys.
To secure and provide access to encryption keys, which are required for FileVault decryption, Apple introduced secure tokens.
Secure tokens are granted to the macOS users who create a local account using Apple's Setup Assistant for the first administrative user, and then subsequently through Apple's Users & Groups pane in System Preferences.
Apple's Deployment Reference for Mac describes additional methods in which a system account may be granted a secure token. Users with a secure token may enable and manage FileVault on a macOS system, and users created by these users are also given secure tokens via a chain of trust methodology.
Expected Behavior:
- The service account doesn’t appear on the main login window or show in the list of users in USER MANAGEMENT > Users unless FileVault is enabled for this user.
- The service account appears in the list of users on the FileVault login screen on boot (when Filevault is enabled for this user.
- New users will need to log in to be added to FileVault and allowed to decrypt the system.
- Existing users that doesn't have secure token wont be able to update\upgrade OS.
- PVWA will rotate password only if both of the users (regular logged in user & EPM user (_cyberarkepm)) have secure token enabled.
- Some system settings needs EPM user to have secure token to elevate the request, such as "Users & Groups" and etc..
Dos and Don'ts:
- Don't delete all your users with the secure token leaving our user as the only user with the Secure Token
- Don't force password reset using sysadminctl for the last secure token enabled account.
- Don't let the EPM user ( _cyberarkepm ) to be the last user with secure token enabled.
- Always manage FileVault with centralized solution such as MDM & use bootstrap token to avoid crucial issues.
- Do inheritance of EPM installation using IT user with secure token
- Always save recovery password of FileVault.
Considerations:
- If the app rejects the local account password, this is likely because the admin does not have a valid secure token. If that is the case, first verify the secure token status of the admin: sysadminctl -secureTokenStatus insert_username_here.
- If the secure token is disabled: The account is missing a secure token. If this is the only user account on the Mac, then the Mac is not in a state where it can provision secure tokens, and it must be wiped and macOS must be reinstalled. However, if there’s another user account on the Mac with a valid secure token, use those credentials to finish enrollment, or log in to that account and leverage the following command in Terminal to provision a secure token to the user account without a secure token:
sysadminctl -adminUser admin_user_here -adminPassword ‘admin_pass’ -secureTokenOn user_here -password ‘user_pass’.