How to Build Secure Enclave iOS Encryption Key
Learn to Enforce Secure Enclave in iOS apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Secure Enclave Key Encryption for iOS ?
iPhones with Touch ID or Face ID use a separate processor, ‘Secure Enclave’, to handle the user’s biometric information.
As an added layer of protection, when enabled, Appdome’s Enclaved Keys service will generate private keys and uses computations via the Secure Enclave processor. Those generated keys will be securely kept inside the Enclave at all times, making it extremely difficult to decrypt without proper authorization. Furthermore, since the Secure Enclave is tied into the Biometric component of the device, it offers an additional layer of protection, allowing the keys accessibility only when the device is unlocked by its original user.
How does Appdome Enhance the Secure Enclave Protection?
Appdome leverages signatures derived via the Secure Enclave in cases of a Sign-Verify scheme. Appdome’s offers Enclaved Keys on all supported hardware and will automatically select the most secure scheme based on the hardware capabilities present on the device.
Prerequisites to Using Enclaved Keys:
To use Appdome’s mobile app security build system to Enforce Secure Enclave , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Enclaved Keys
- Mobile App (.ipa For iOS)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Enforce Secure Enclave on iOS apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending iOS Apps that Enforce Secure Enclave without an SDK or gateway:
Upload the Mobile App to Appdome.
Upload an app to Appdome’s Mobile App Security Build System
Upload Method: Appdome Console or DEV-API
iOS Formats: .ipa
Enclaved Keys Compatible With: Obj-C, C+, Java, Swift, Flutter, React Native, Unity, Xamarin, Cordova and more
Build the feature: Enclaved Keys.
Congratulations! The Enclaved Keys protection is now added to the mobile app
Building Enclaved Keys by using Appdome’s DEV-API:
Create and name the Fusion Set (security template) that will contain the Enclaved Keys feature as shown below:
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Enclaved Keys feature via Appdome Console, to add the Enclaved Keys feature to this Fusion Set.
Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set, as shown in Figure 1 above, and get the Fusion Set ID from the Fusion Set Detail Summary (as shown below):
Figure 2: Fusion Set Detail Summary
Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).
Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Cirlce CI or other system:
Figure 1: Fusion Set that will contain the Enclaved Keys feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
Building the Enclaved Keys feature via Appdome Console
To build the Enclaved Keys protection by using Appdome Console, follow the instructions below.
Where: Inside the Appdome Console, go to Build > Security Tab > TOTALData™ Encryption section
How: Toggle (turn ON) Enclaved Keys, as shown below.
Figure 3: Enforce Secure Enclave option
When you select the Enclaved Keys you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Enclaved Keys
Figure 4: Fusion Set that displays the newly added Enclaved Keys protection
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Certify the Enclaved Keys feature in iOS Apps.
After building Enclaved Keys, Appdome generates a Certified Secure™ certificate to guarantee that the Enclaved Keys protection has been added and is protecting the app. To verify that the Enclaved Keys protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below:
Figure 5: Certified Secure™ certificate
Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Enclaved Keys has been added to each iOS app. Certified Secure provides instant and in-line DevSecOps compliance certification that Enclaved Keys and other mobile app security features are in each build of the mobile app
Using Appdome, there are no development or coding prerequisites to build secured iOS Apps by using Enclaved Keys. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.
Releasing and Publishing Mobile Apps with Enclaved Keys
After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:
- Customizing, Configuring & Branding Secure Mobile Apps
- Deploying/Publishing Secure mobile apps to Public or Private app stores
- Releasing Secured Android & iOS Apps built on Appdome.
All apps protected by Appdome are fully compatible with any public app store, including Apple App Store, Google Play, Huawei App Gallery and more.
- How to Enable Restore from Backup on Android & iOS Apps
- How to Encrypt Data at Rest in Android or iOS Apps
- How to Block Memory Editing tools for Android & iOS apps
- How to Share Authentication Between Android and iOS Apps
If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.
Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.