Steth IO uses a variety of different tools and techniques to ensure that all data captured by our stethoscope is securely maintained. Security features are split into two categories: those built into the Steth IO application and those inherent in the Apple’s iOS.
Passcode to access the device
The Steth IO software application for iOS will not install on an electronic device unless a security passcode to lock and unlock the device is enabled. This passcode feature keeps the physical device secure in terms of data security and integrity.
Passcode to access the application
The Steth IO software also requires a user to enable a PIN code to access the application. This added security ensures that any personal information stored in the software application is kept secure and data integrity maintained. This PIN code feature ensures a second layer of data security at the software application layer.
Account login to the app
The Steth IO iOS application, when downloaded and installed for the first time, requires the user to create an account. A request for account creation generates an email requiring a confirmation from the user to finalize the new account. This security feature helps identity authentication and allows secure password retrieval for the account holder only.
Data Encryption at Rest and in Transit
Data stored on iOS devices is encrypted with a 256 k encryption. Every iOS device has a dedicated AES-256 crypto engine built into the DMA path between the flash storage and main system memory, making file encryption highly efficient. On A9 or later A-series processors, the flash storage subsystem is on an isolated bus that is only granted access to memory containing user data via the DMA crypto engine. The device’s unique ID (UID) and a device group ID (GID) are AES 256-bit keys fused (UID) or compiled (GID) into the application processor and Secure Enclave during manufacturing. No software or firmware can read them directly; they can see only the results of encryption or decryption operations performed by dedicated AES engines implemented in silicon using the UID or GID as a key. Additionally, the Secure Enclave’s UID and GID can only be used by the AES engine dedicated to the Secure Enclave. The UIDs and GIDs are also not available via JTAG or other debugging interfaces.
File Data Protection (iOS Feature)
In addition to the hardware encryption features built into iOS devices, Apple uses a technology called Data Protection to further protect data stored in flash memory on the device. Data Protection allows the device to respond to common events such as incoming phone calls, but also enables a high level of encryption for user data. Key system apps, such as Messages, Mail, Calendar, Contacts, Photos, and Health data values use Data Protection by default, and third-party apps installed on iOS 7 or later receive this protection automatically. Data Protection is implemented by constructing and managing a hierarchy of keys, and builds on the hardware encryption technologies built into each iOS device. Data Protection is controlled on a per-file basis by assigning each file to a class; accessibility is determined by whether the class keys have been unlocked. With the advent of the Apple File System (APFS), the file system is now able to further sub-divide the keys into a per-extent basis (portions of a file can have different keys)
More information on both of these capabilities can be found in Apple’s Security Guide
iOS devices can be erased remotely by an administrator or user. Instant remote wipe is achieved by securely discarding the block storage encryption key from Effaceable Storage, rendering all data unreadable. A remote wipe command can be initiated by MDM, Exchange, or iCloud. When a remote wipe command is triggered by MDM or iCloud, the device sends an acknowledgment and performs the wipe. For remote wipe via Exchange, the device checks in with the Exchange server before performing the wipe. Users can also wipe devices in their possession using the Settings app. And as mentioned, devices can be set to automatically wipe after a series of failed passcode attempts.
If a device is lost or stolen, an MDM administrator can remotely enable Lost Mode on a supervised device with iOS 9.3 or later. When Lost Mode is enabled, the current user is logged out and the device can’t be unlocked. The screen displays a message that can be customized by the administrator, such as displaying a phone number to call if the device is found. When the device is put into Lost Mode, the administrator can request the device to send its current location and, optionally, play a sound. When an administrator turns off Lost Mode, which is the only way the mode can be exited, the user is informed of this action through a message on the Lock screen or an alert on the Home screen.
More information on Remote wipe and Lost Mode can be found in Apple’s Security Guide
No products will be shipped, nor charges incurred, before FDA clearance.