Appaloosa lets you require a PIN code (or a password) on your Android devices and define how strong it must be. When a device does not meet the requirements, the user is asked to set a new code.
Where you configure it depends on the enrolment mode:
Managed devices: open your Android managed configuration, then the Security tab, Access code card. On COPE devices (company owned, personally enabled), this code applies to the Work Profile only.
COPE devices, whole device: in the same configuration, Personal usage tab, Access code card. This code protects the whole device.
BYOD devices: open your Android BYOD configuration, then the Security tab, Access code card. This code protects the Work Profile only, the personal side of the device is not affected.
How it works
Once you save the configuration, the policy is sent to every device using it. If the current lock screen does not meet the requirements, the device displays a notification asking the user to change their code. The Passcode line of the device overview shows whether a lock screen is set on the device.
Android handles password rules differently depending on its version, which is why the card has two ways of describing the code:
Android 12 and above use the Password complexity level.
Android 11 and below use the Minimum PIN length. It is also used on any version when no complexity is set.
Appaloosa sends both, and each device applies the one its Android version supports, so a mixed fleet is covered by a single configuration.
Enable PIN restriction
Turns the requirement on or off. When it is off, Appaloosa does not require any code and the other fields of the card are not applied.
Minimum PIN length
The minimum number of characters of the code, from 4 to 16.
On Android 11 and below, the code must also avoid repeating (4444) or ordered (1234, 4321, 2468) sequences. A PIN or a password both work, as long as they are long enough.
Watch out for the Low complexity: when Password complexity is set to Low, devices on Android 11 and below only require a lock screen (pattern, PIN or password) and the minimum length is not enforced.
Password complexity
On Android 11 and below, complexity levels do not exist: Medium and High are applied as the Minimum PIN length rule described above, and Low only requires a lock screen.
On Android 12 and above, you can choose one of the following levels to define the weakest lock screen the user may choose:
Not defined: the device uses the Minimum PIN length instead.
Low: a pattern, or a PIN with repeating (4444) or ordered (1234) digits, is accepted.
Medium: a PIN without repeating or ordered digits, or an alphabetic or alphanumeric password, with at least 4 characters.
High: a PIN without repeating or ordered digits and at least 8 digits, or an alphabetic or alphanumeric password with at least 6 characters.
A pattern is only accepted with the Low level.
Settings available on managed devices
The Access code card of the Security tab offers three more settings. They are available once Enable PIN restriction is on.
Maximum Auto-Lock (in minutes): the device locks itself after this idle time, from 1 to 15 minutes. The user can still pick a shorter delay in the device settings, not a longer one.
Number of unique passwords required before reuse: how many previous codes the user cannot use again. With 3, the new code must differ from the last three.
Maximum password lifetime (in days): after this number of days, the user is asked to change their code.
Leave a field empty to apply no restriction.
COPE devices
A COPE device has a Work Profile and a personal side, so it can carry two codes:
the Security tab code protects the Work Profile, the work apps and their data;
the Personal usage tab code protects the whole device, it is the one used to unlock the screen.
The Personal usage card offers Minimum PIN length and Password complexity, which work as described above.
BYOD devices
On a personal device, Appaloosa only manages the Work Profile. The Access code card of the BYOD configuration offers Minimum PIN length and Password complexity, applied to the Work Profile. The user keeps full control over the code of their device.
Compliance settings (BYOD)
The Compliance settings card of the BYOD Security tab defines what happens when a Work Profile stays without a valid code:
Days before blocking a non compliant work profile: after this number of days, work apps are blocked and the user receives a notification explaining how to fix the issue. Personal apps keep working. Use 0 to block right away.
Days before wiping a non compliant work profile: after this number of days, the Work Profile and its data are deleted from the device. Personal data is not touched.
The wipe delay must be greater than the block delay, otherwise the rule is not applied. Set both to 0 to disable it. As soon as the user sets a valid code, the Work Profile is unblocked.
Notes
Appaloosa never sees the code chosen by the user. If a user of a managed device forgets it, use the Change PIN code action from the device page to set a new one, consistent with the requirements of the configuration. You can also lock the device right after the change.
On the default configuration, each field has a lock icon. A locked field applies its value to every other configuration of the store, where it can no longer be changed.




