Appaloosa lets you enforce a passcode policy on your iOS and iPadOS devices to secure access.
All settings are available on the configuration page of your iOS / iPadOS configuration:
Managed devices — under the Security tab, in the Passcode card.
BYOD devices — under the BYOD configuration tab, in the Access code card.
How it works
When the configuration is applied, iOS / iPadOS checks whether the current passcode meets the configured rules.
If the current passcode is compliant, the policy is applied silently.
If it is not compliant, the user is prompted to set a new passcode that meets the policy. If the user does not comply within 60 minutes, the system forces them to enter a passcode using the specified settings; otherwise they cannot use their device anymore.
When the policy is disabled, all related restrictions are removed from the device.
Minimum passcode length
The minimum number of characters the user's passcode must contain.
0 — no minimum length is enforced.
4 to 16 — iOS / iPadOS enforces a length within this range.
Minimum complex characters
The minimum number of non-alphanumeric characters (for example !, $, #, %) the passcode must contain.
Accepted values: 0 to 4.
0 means no complex character is required.
Require alphanumeric
Controls the type of characters required.
On — the user must set an alphanumeric passcode (letters and digits).
Off — a numeric passcode is accepted.
Maximum Auto-Lock (in minutes)
The maximum amount of time the device can stay idle before it is automatically locked. The user can pick any timeout shorter than this value in their iOS / iPadOS settings, but cannot exceed it.
Accepted values: 0 to 15 minutes.
0 means no timeout is enforced.
On the device: Settings > Display & Brightness > Auto-Lock will only show timeout values up to the configured maximum.
Maximum grace period (in minutes)
How soon the device can be unlocked again after use without having to re-enter the passcode. This is independent of Auto-Lock — Auto-Lock controls when the screen turns off after inactivity, while the grace period controls how long after a lock the user can wake the device without typing their passcode.
Accepted values: 0 to 15 minutes.
0 means the passcode is required immediately after every lock.
Allow simple passcode
Controls whether common patterns such as 1111, 1234 or repeated/sequential characters are accepted as passcodes.
On — simple sequences are allowed.
Off — simple sequences are rejected.
Maximum passcode lifetime (in days)
How long a passcode can be used before the user is forced to change it.
Accepted values: 0 to 730 days.
0 means the passcode never expires.
On the device: when the lifetime is reached, iOS / iPadOS asks the user to choose a new passcode the next time they unlock the device. The new passcode must satisfy all the other rules in the policy.
Number of unique passcodes required before reuse
How many previous passcodes are remembered to prevent the user from reusing them. The current passcode is included in the count, so a value of 1 prevents reusing the current passcode, 5 prevents reusing the current and the four previous ones, and so on.
Accepted values: 1 to 50.
On the device: if the user tries to set a passcode that matches one in the remembered history, iOS / iPadOS rejects it and asks them to pick a different one.
Notes
If a user enters too many wrong passcodes in a row, iOS / iPadOS adds an increasing time delay between attempts, and after enough failures all data and settings on the device are securely erased. This is enforced by Apple, independently of Appaloosa.
Each field can be locked from the default configuration so that all sibling iOS / iPadOS configurations of the same type inherit the same value. See Lock Configurations for details.
