- Accurate
- Not particularly relevant for M1 systems. FileVault is embedded into the Secure Enclave’s storage controller, and storage is always encrypted. The key difference with FileVault on vs off on an M1 is that your password is combined with the fused AES keys to decrypt drive contents.
- Even less relevant for the same reasons as #2. There’s also acceleration hardware involved for the AES algorithm, and the internal drive is always encrypted. This has been true for Intel Macs with the T2 chip as well.
- Because the whole drive is encrypted anyways, it could very well be less effort for the user to just enable FileVault and call it a day rather than manage individual encrypted files or disk images.
- Technically accurate, but unfortunately not relevant for M1 or T2 Macs, because of the always-on encryption. SSDs tend to use internal encryption when writing to NAND, making recovery more difficult than HDDs to begin with. I’ve also only ever successfully recovered data once in 30 years from a failed HDD, without paying the high prices for a service to do the recovery for me. A good disaster recovery plan should always start with good backups, and drive recovery a last resort.
- Certainly not, but it does mean that if I use my machine to conduct business, I’m not letting someone rummage through all that just because they managed to take possession of my laptop. And it prevents them from making further inroads to my accounts. Last thing I want is for someone to take my laptop and get access to my financial accounts because a cookie failed to expire in time.
- Sure. But I don’t encrypt to keep people I trust out. Yet, encryption helps me build trust with those I do work for, by demonstrating I can be trusted with their sensitive data. When it comes to data my family needs access to if I drop dead, they already have copies of everything needed. My device isn’t going to give them anything they don’t already have (good disaster recovery practices there again).
One of the best arguments for enabling FileVault is to simply make sure that if you do misplace your device, or it is stolen, the impact to you is limited. If you do online banking, store website account passwords in your keychain, or have accounts that will send you e-mail with reset codes that are important, that’s all data useful to a bad actor. Having one take possession of your laptop can then create headaches for weeks, months, or even years down the road in the form of identity theft and fraud. And since more and more people do online banking, or have more and more vital information accessible via laptops and other devices, the risks are higher now than when they were a decade ago.
All very fair. My bullet points were for my situ
- Accurate
- Not particularly relevant for M1 systems. FileVault is embedded into the Secure Enclave’s storage controller, and storage is always encrypted. The key difference with FileVault on vs off on an M1 is that your password is combined with the fused AES keys to decrypt drive contents.
- Even less relevant for the same reasons as #2. There’s also acceleration hardware involved for the AES algorithm, and the internal drive is always encrypted. This has been true for Intel Macs with the T2 chip as well.
- Because the whole drive is encrypted anyways, it could very well be less effort for the user to just enable FileVault and call it a day rather than manage individual encrypted files or disk images.
- Technically accurate, but unfortunately not relevant for M1 or T2 Macs, because of the always-on encryption. SSDs tend to use internal encryption when writing to NAND, making recovery more difficult than HDDs to begin with. I’ve also only ever successfully recovered data once in 30 years from a failed HDD, without paying the high prices for a service to do the recovery for me. A good disaster recovery plan should always start with good backups, and drive recovery a last resort.
- Certainly not, but it does mean that if I use my machine to conduct business, I’m not letting someone rummage through all that just because they managed to take possession of my laptop. And it prevents them from making further inroads to my accounts. Last thing I want is for someone to take my laptop and get access to my financial accounts because a cookie failed to expire in time.
- Sure. But I don’t encrypt to keep people I trust out. Yet, encryption helps me build trust with those I do work for, by demonstrating I can be trusted with their sensitive data. When it comes to data my family needs access to if I drop dead, they already have copies of everything needed. My device isn’t going to give them anything they don’t already have (good disaster recovery practices there again).
One of the best arguments for enabling FileVault is to simply make sure that if you do misplace your device, or it is stolen, the impact to you is limited. If you do online banking, store website account passwords in your keychain, or have accounts that will send you e-mail with reset codes that are important, that’s all data useful to a bad actor. Having one take possession of your laptop can then create headaches for weeks, months, or even years down the road in the form of identity theft and fraud. And since more and more people do online banking, or have more and more vital information accessible via laptops and other devices, the risks are higher now than when they were a decade ago.
- Accurate
- Not particularly relevant for M1 systems. FileVault is embedded into the Secure Enclave’s storage controller, and storage is always encrypted. The key difference with FileVault on vs off on an M1 is that your password is combined with the fused AES keys to decrypt drive contents.
- Even less relevant for the same reasons as #2. There’s also acceleration hardware involved for the AES algorithm, and the internal drive is always encrypted. This has been true for Intel Macs with the T2 chip as well.
- Because the whole drive is encrypted anyways, it could very well be less effort for the user to just enable FileVault and call it a day rather than manage individual encrypted files or disk images.
- Technically accurate, but unfortunately not relevant for M1 or T2 Macs, because of the always-on encryption. SSDs tend to use internal encryption when writing to NAND, making recovery more difficult than HDDs to begin with. I’ve also only ever successfully recovered data once in 30 years from a failed HDD, without paying the high prices for a service to do the recovery for me. A good disaster recovery plan should always start with good backups, and drive recovery a last resort.
- Certainly not, but it does mean that if I use my machine to conduct business, I’m not letting someone rummage through all that just because they managed to take possession of my laptop. And it prevents them from making further inroads to my accounts. Last thing I want is for someone to take my laptop and get access to my financial accounts because a cookie failed to expire in time.
- Sure. But I don’t encrypt to keep people I trust out. Yet, encryption helps me build trust with those I do work for, by demonstrating I can be trusted with their sensitive data. When it comes to data my family needs access to if I drop dead, they already have copies of everything needed. My device isn’t going to give them anything they don’t already have (good disaster recovery practices there again).
One of the best arguments for enabling FileVault is to simply make sure that if you do misplace your device, or it is stolen, the impact to you is limited. If you do online banking, store website account passwords in your keychain, or have accounts that will send you e-mail with reset codes that are important, that’s all data useful to a bad actor. Having one take possession of your laptop can then create headaches for weeks, months, or even years down the road in the form of identity theft and fraud. And since more and more people do online banking, or have more and more vital information accessible via laptops and other devices, the risks are higher now than when they were a decade ago.
All very fair. I wrote my post for my situation, with my equipment, and not too seriously.
Auto login I do value and have it on my computers other than my M1 because then it would affect touch sensor functionality. I’ve always resented having to login to my own computer, I want to just switch on and use it like a toaster or other appliance. The M1 I simply don’t power down, so I just lift the lid and touch the sensor. Obviously , anyone can turn on my iMac or MBP and access any file but the few financially sensitive ones are password protected, and I never, not once yet, take them out of the house.
Sure I rely on internet banking, but it’s just not possible to browser login to my bank (First Direct) system without using a phone with biometric ID, the passwords get so far into the system and then a time-limited access code has to be generated by the phone.
I didn’t know all M1 SSDs were encrypted anyway, but as Homer Simpson said, you can prove anything with facts!
All my data is mine alone, I finished my last job in 2011 so have no responsibility to others, if I did that would mean many changes to my security. Mind you, that last job was on contract to IBM and they didn’t rely entirely on individuals good practice, they issued an (ancient) Thinkpad and the only way to connect to their systems was via their VPN on their laptop.
When I wrote about system recovery I was probably recalling long ago times when it was easy to take a HDD from a PC and see what could be read on it with a decent set of utilities external to another PC. Not relevant to my computers of today, I accept.
Thanks for reading and responding in detail.