limitChecksAfterStartup

Determines whether to limit the amount of security checks that Shield continues to perform after the app has launched.

Usually, App Shielding performs regular security checks in the background in case the process is attacked after launch. This is not a problem for apps that do not perform a lot of performance critical work after they have launched. However, in some cases where the performance is very important during the whole lifetime of the app (e.g. in games), these checks can cause performance problems. In these cases, it is possible to limit the checks that App Shielding does regularly after the app has launched. This increases performance but has a security impact. However, if App Shielding has determined during launch that neither the process nor the device is in an insecure state, this impact is limited.

This option, when enabled, limits the amount of checks that App Shielding does after launch. To guarantee that the app and the device are in a secure state initially, we require the checkJailbreak, exitOnJailbreak, checkLibraryInjection, exitOnLibraryInjection, checkHookingFrameworks and exitOnHookingFrameworks options to be enabled when using this feature.

• Type: boolean

• Default Value: false

• Multiple allowed: No

• Required: No

• Requires:

  • checkJailbreak

  • exitOnJailbreak

  • checkLibraryInjection

  • exitOnLibraryInjection

  • checkHookingFrameworks

  • exitOnHookingFrameworks