First added to Macs in the T1 chip, the Secure Enclave makes it far harder for an attacker to gain access to secrets like the FileVault encryption key.
encryption
Do you need to back it up when the problem is minor? Should you erase its internal storage? Anything else you need to do?
If you’re wondering how to store snippets of private info, sensitive files, or folders full of secrets, here’s how to use the right features in macOS.
How to protect collections of files using different encryption passwords, and making most efficient use of storage space.
hdiutil chpass, the only means of changing passwords for sparse bundles, doesn’t work in macOS Ventura 13.3.1. The workaround requires a VM and 13.1.
Here’s an APFS (Encrypted) volume that isn’t encrypted, and an unencrypted volume with FileVault active. Something must be wrong.
Details of what happens when an APFS (Encrypted) volume is mounted, when mounting a Time Machine snapshot, unmounting a volume, and loading a Cryptex.
T2 and Apple silicon Macs always encrypt the Data volume in internal storage. So why bother with enabling FileVault? And can you do that on external bootable disks?
Is the performance overhead of using APFS Encrypted volumes to store sensitive data a reason for not doing so?
Plain read/write (UDRW), sparse image (UDSP), and sparse bundle (UDSB) compared for storage efficiency, performance, and convenience.
