iOS Application Protection | FAQ

Frequently Asked Questions

Collapse All

Will MAST affect my app's performance?

You’ll barely notice. The dummy code added for code diffusion is never executed; it’s just there to stymie human readers. If you’re really concerned, MAST’s protections are adjustable; you can tweak the layers of protection that it adds.

If you want to add all of the protections MAST affords without spending months learning them, uploading the bitcode is the easiest way to do so. Once MAST does its work, we don’t store your bitcode. If you’re more comfortable with local hosting, contact us for details.

Yes. New reverse engineering and runtime tampering tools, and Jailbreak techniques emerge every day. We know, because we monitor for new threats continuously. When we find a new threat, we teach MAST how to break it. Every time you recompile your app with MAST’s updated protections, it will break attacker’s newest tools immediately, setting them back to zero.

No, MAST won't shut out valid users. Here's why. Because Apple only releases one version of iOS, MAST relies only on specific, low-level jailbreak checks chosen intentionally to avoid false positives.

Yes. Your app can shut down completely, or it can just shut off certain functionality to misdirect attackers even more.

None. Just upload your app’s bitcode as if you were submitting it to Apple. MAST will return a functionally identical version of your app, which you can then submit to Apple immediately.

No. MAST never touches your app’s source code.


Yes. You get complete control over which passes MAST takes over your bitcode. Add all seven protections at full strength, and the binary size and run time will increase by a minimal percentage with limited impact to the deployed app. You can scale back these percentages by setting MAST to cover less of the overall code base.

Yes, you can customize MAST’s callbacks.

Yes. You could upload to Apple the bitcode MAST returns immediately, though we recommend you address any recommendations MAST makes about your app’s use of iOS security measures.

No. Because your certificate should be embedded in the source code project, we bundle in Trustkit, open-source software that will do this for you automatically. Trustkit won’t modify your code, it swizzles your connections, you can configure where certificate validation failures are reported, and it can be easily deployed using CocoaPods or by hand.

  • Objective-C
  • Objective-C++
  • Swift
  • C
  • C++

It’s never too late to protect your app’s sensitive data. We recommend you use MAST every time you’re ready to push an update.