Version 7.0.3 (December 2024)

Description: To prevent conflicts with other frameworks or naming conventions, ShieldConfig and ShieldConfigUpdateCallbacks have been renamed to PRMShieldConfig and PRMShieldConfigUpdateCallbacks, respectively. The sample included in the product package also has been updated.

The original names have been marked as deprecated and will be removed in a future release.

Description: The coverage of the Block screenshot configuration option has been improved for apps using UISceneDelegate.

The detection of newer Jailbreak hiders and associated hooking tools has been improved.

Description: Previously, when building the library and uploading the package to a Package Registry (e.g., Artifactory or GitLab), the following error was encountered:

[!] Unable to install vendored xcframework `ShieldSDK` for Pod `react-native-appshield`, because it contains both static and dynamic frameworks.

Status: This issue has been fixed. The proper handling of symbolic links within ShieldSDK.xcframework is now ensured.

Description: App Shielding now provides an additional detector for Dopamine-based jailbreaks.

Description: The thread safety has been improved for restoring bindings. This also resolves an issue where in rare cases the application could terminate unexpectedly on launch.

Description: The coverage of the new screenshot blocking feature for apps using UISceneDelegate has been improved.

Description: Previously, the Exit on Developer Mode option would not trigger on devices running iOS 15 and earlier versions, but the Developer Mode callback would still trigger, always returning true.

Status: To ensure consistency, the Developer Mode callback now always returns false on iOS 15 and earlier versions, reflecting that Developer Mode is only available on iOS 16 and later.

Description: Because of the nature of pure Javascript frameworks such as Cordova, the effectiveness of the push and pull bindings of App Shielding is affected. As a result, it might be possible to extract all Javascript files from a shielded application and build a new Cordova-based application with the extracted Javascript files. That new application will behave identical to the original one but has two major differences:

1. It is not longer protected with App Shielding.

2. It is signed with a different developer certificate.

Because this new application is signed with a different developer certificate, it is recognized by the stores or every device as a completely different and new application in comparison to the original shielded application. It cannot be avoided that a new application like this is built that looks and behaves similar to the original application.

OneSpan risk assessment: Threat actors will need to make heavy use of targeted phishing attacks to convince users of the original application to install the rogue version. For attackers, however, it is much easier to use existing malware frameworks that mimic hundreds of login screens in one single piece of malware. In addition, the existence of any rogue versions of the application does not affect the security features of the original shielded application. Everyone who is using the genuine, shielded application is protected with all the features of App Shielding, including all security measures of the original application. Therefore, we consider this issue to be of low risk.

Xcode marks the ShieldSDK.xcframework package as not signed or verified and might move it to quarantine mode. If Xcode displays a message like ShieldSDK.xcframework cannot be opened..., follow these steps to resolve it:

1. Select Cancel.

2. Open the macOS System Settings.

3. Navigate to Privacy & Security.

4. Scroll down to the security warning and select Allow Anyway.

This will be fixed as soon as possible.

Blocking external screens (e.g. AirPlay) is currently not working for apps that use UISceneDelegate in iOS 13 and later.