Frequently Asked Questions

What devices may I use for jailed testing with NowSecure Gadget? What iOS versions?

You may use any Apple device for jailed testing running iOS 11.0 - 11.4.


Will I continue to have the ability to conduct tests on jailbroken devices?

Yes. NowSecure Workstation 5.2.1 will provide the flexibility to test on both jailbroken and jailed (protected) devices. ​Do not upgrade your NowSecure provided jailbroken device to conduct jailed testing. ​ Jailed testing does not require additional configuration from NowSecure or your organization, so customers may leverage their own devices for jailed tests.


Can I use jailed testing option for 3rd party public App Store apps?

Not at this time. The NowSecure Gadget injects a dynamic library into the debug build of a mobile app when it is launched. If the app is encrypted and non-debug, we’re unable to hook into the app and inject the code. Jailed testing may only be leveraged for debuggable, first-party developed apps at this time.


Are there any differences in NowSecure Findings for jailbroken tests vs. jailed tests?

Jailed testing produces the same findings as jailbroken tests, except jailed testing does not include Snapshots at this time. This is because Snapshot requires system level permissions and jailed testing operates with only app level permissions. A workaround is planned for the future.


Are there differences in workflow between jailed and jailbroken testing?

Yes, there is one slight difference. When conducting jailbroken tests, Analysts must first launch the application on the mobile device to get started. With jailed testing, NowSecure Workstation will launch the chosen application on the Analyst’s behalf.


How do I provision a non-jailbroken device?

For Jailed testing, there is no provisioning method for new devices, the jailed agent only communicates via the API once the dynamic lib is injected into the app. There are three overall requirements to use a jailed device:

  1. Use a debuggable app.
  2. Install the mitmproxy profile, from the device, navigate to ​https://cydia.nowsecure.com and click the “Install Profile” link
  3. Developer image mounted. Workstation 5.2.1 will handle this for you if running iOS 11.0-11.4 using the Device Manager “test” button.

If Workstation isn’t seeing the device, make sure it is passed through to the VM, and that you have selected the “Trust” option on the device to make sure it gets mounted into the OS properly. If you connected the device before updating the Workstation deb, then the device may be stuck in an odd state, and to fix it, you should just need to disconnect/reconnect it (this is related to some dependency updates that were pulled down upon deb install).


The application was unable to launch. This could be caused from the build expiring, or that it is no longer trusted. Check the trust settings under General -> Device Management to ensudre the app is verified. Other, you may need to reinstall the application.

If you are receiving this error:

  • Try verifying the application on your device:

On the iOS device, navigate to Settings > General > Profiles & Device Mangement, Click on the email address under the Developer App section. Then click Verify App


  • Try re-installing the application on the device:

  • Download Cydia Impactor from http://www.cydiaimpactor.com/

  • Create an Apple ID: https://appleid.apple.com/account#!&page=create

  • Make sure you have DISABLED 2-Factor Authentication on your Apple ID.

  • With your iOS device connected to your computer and iTunes closed out, launch Cydia Impactor

  • With Cydia Impactor launched, you will see the device name in top field of the window.

  • Drag your application on to the Impactor window.

  • You will be prompted to enter an Apple ID. Enter your Apple ID Username and Password.

  • Impactor will sign and sideload the IPA automatically to your device.

  • On the iOS device, navigate to Settings > General > Profiles & Device Mangement, Click on the email address under the Developer App section. Then click Verify App


  • Try remounting the Developer Image for the iOS Device Version:

  • In Workstation, click on Options > Device Manger

  • Click on the Jailed button and click the Test button.

This will automatically mount the developer image for the iOS device version.