---
title: "Configuration of Shielding Tool Rules on iOS"
slug: "oapps-igios-configuration-of-shielding-tool-rules-on-ios-8-1-3"
updated: 2026-10-20T11:53:02Z
published: 2026-10-20T11:53:02Z
canonical: "docs.onespan.com/oapps-igios-configuration-of-shielding-tool-rules-on-ios-8-1-3"
excludeFromSearch: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onespan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration of Shielding Tool Rules on iOS

You can specify rules to determine how App Shielding will modify the iOS application in a rules file.

## File integrity checks

As part of the Check Repackaging security feature, individual files can be checked for their integrity to ensure they have not been tampered with. These files are configured in a Shielding Tool rules file using the `verify` keyword. For example:

```plaintext
# Verify individual files
verify "Assets.car";
verify "AppIcon60x60@2x.png";

# Verify all plist files using a regular expression
verify ".*\.plist";
```

If any of the files marked with `verify` are modified between integrating App Shielding and running the application, App Shielding reports this as a repackaging event.

Integrity checks cannot be applied to files that are intentionally modified after the integration process (e.g., re-signed libraries) or during App Shielding runtime. This includes the following:

- The main app binary and other executables
- The main `Info.plist` file
- The App Shielding library (`libshield`)
- Other frameworks

If a `verify` pattern includes any such modified files, they should be excluded using the `skipVerifyPath` option. `verify` adds the specified file(s) to the integrity check process, `skipVerifyPath` excludes the specified file(s) from the integrity check process.

> The app binary, App Shielding library, and other frameworks are always verified as part of the overall App Shielding repackaging check.