|x||Device Storage||Device Memory||Keychain||SecureEnclave||Transport||iCloud||Inbox||Outbox|
|Compromise conditions||Sandbox escape is enough||Requires either kernel compromised or binary modified, coupled to app version||Codesigning compromise is enough||No known attacks yet||Person in the middle attacks||Not controlled by us||Possible malicious content||Can include quote from incoming message|
|Solution||MainKey||Not much can be done||MainKey||_||Certificate pinning||Do not use||DOMPurify, CSP, no JS in WebViews||DOMPurify, CSP|
As most iOS appications, our application needs to store some data locally:
- encrypted messages and attachments cache
- private and public keys for sending and reading messages
- access token for communication with back end
- token for push notification payload decryption
- details of user account
Some of these pieces of data is kept in Keychain, some in our local CoreData database, and some in UserDefaults dictionary inside the application directory. iOS offers high level of data protection using Keychain Data Protection and File Data Protection classes, but on top of them we've introduced our own additional layer of protection called MainKey mechanism (for cases when user has TouchID/FaceID or PIN is active).
|Auth token||High: allows to steal session||High: session can be closed from website||Low: wrong token leads to correct logout||Low: no token leads to correct logout|
|Mailbox Password (this is not Login Password!)||Critical: allows decryption of messages, contacts and attachments||Critical: in 2 password mode can be reused by user on other services||Low: wrong value will not decrypt local data and will throw user to Mailbox Password screen||Low: wrong value will not decrypt mailbox and will throw user to Mailbox Password screen|
|Email Private and Public Keys||Critical: allows decryption of messages caught in the air||Critical: allows decryption of old messages||Moderate: messages will not be properly decrypted||Moderate: messages will not be properly decrypted|
|CoreData (Messages, Attachments, Contacts, Labels)||Critical||Critical||Critical: can mislead user on this device until relogin||Moderate: poor UX|
|Username||Critical: connects account to person||Critical: connects account to person||Low||Low|
|Settings||Low||Low||High: can affect privacy if not noticed by user (Autoload Images, Remove image meta-data)||Low|
|Push payload encryption key||High: push payload contains senders name and message title||Low: key is per-session, iOS does not keep pushes on device for long||Low||Low|
Default Data Protection
Most Keychain items are saved with
kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly flag. We could not use more strict flags because its pretty common that app needs to complete its work in background even when the device is locked - for example, when user is sending email with heavy attachments. In order to share them across all our application extensions (Share and Push Application Extensions), we keep them in one Keychain Access Group. We do not want them to be restorable from backup on ther devices.
Data protection class for files is set as
NSFileProtectionComplete in app entitlements with a default exceptions for CoreData and UserDefaults files, which we need to access in background and when the device is locked.
More information is available in iOS Security documentation.
In order to increase our chances to protect the data when iOS sandbox is compromised or when rouge applicatoin managed to dump keychain, we've introduced MainKey protection system. The idea is to encrypt all sensible local data with per-login local key called MainKey, which will not be stored in compromisable places.
MainKey may be persisted by means of 2 techniques:
- TouchID/FaceID protection. SecureEnclave chip generates asymmetric keypair, keep private key inside and give public key to the app. We encrypt MainKey with public key and save to Keychain, asking SecureEnclave to decrypt it every time we need to retrieve cleartext MainKey. SecureEnclave decrypt the MainKey only after biometric authentication or device passcode and the private key never leaves it.
- PIN protection. We can derive temporary key from user-input PIN string, symmetrically encrypt MainKey with this temporary key and save cyphertext to Keychain. Temporary key and PIN string are never persisted and are removed from memory as fast as possible. No PIN input - no access to MainKey.
- No protection. For cases when user does not want to switch on additional protection in app Settings, MainKey is saved cleartext in Keychain. This case is weak against forensic attacks in cases when device is compromised, but the data should not be extractable from backups. This case is trivial and will not be discussed furter.
- Most attributes of items saved in CoreData
- User account and user's encryption keys
- Access token
On every app launch MainKey cyphertext from Keychain should be decrypted and placed into memory of the app process before any other part of the app will start its work. That's why the app is not functional unless user enters PIN/TouchID/FaceID - the app can not access local data and does not know anything about user to request data from server. Side effect of this architecture is that Share extension requires authentication every time, as it runs in separate process.
MainKey is kept in memory of the app process according to Autolock Time settings: it can be removed from memory after certain amount of time or each time apps goes background.