*This Knowledge Base article will be focusing on the Defender 3000, Elite 300, Elite 30, Bio-Elite 30, Life Planner, HDD/SSD 35, and HDD/SSD 350
Unmanaged Drives:
For Unmanaged Defender Drives or drives that are not connected to a KRMC Hosted, or On-Prem account and/ or not connected to a UKLA instance, the default number of failed login attempts is set to 7.
After the 7 failed attempts, the drive will reset itself to factory settings and delete all the data that was stored on the drive. If this does occur, unfortunately there is no way to recover the data that was on the drive.
Managed Drives:
For Managed Defender Drives or drives that are connected to a KRMC Hosted, or On-Prem account and/ or connected to a UKLA instance, the default number of failed login attempts is set to 7. This number can be changed by the SA of your account or the UKLA instance anywhere between 3 and 15 attempts.
By default, after the set number of failed login attempts is reached, a managed drive will be disabled. To re-enable the drive, an “enable” action will need to be sent to the drive from KRMC, or the drive will need to be re-enabled via UKLA. This behavior can also be changed in the settings of KRMC or UKLA. The options for how the drive can act once the set number of failed login attempts is reached are the following:
| Format | The device will automatically format itself if the user exceeds the number of allowed password retried. This will erase all admin settings and user data stored on the device and reset the device to the factory default settings. |
| Timeout | The device will automatically activate a timeout period if the user exceeds the number of allowed password retries. The user will have to wait for the timeout period to pass before they are allowed to attempt to enter a password again. |
| Disable | The device will become disabled if the user exceeds the number of allowed password retries. The device user will be unable to login to their device or access the device’s secure partition again until it is enabled by an ‘Enable Device’ remote action. |
Comments
0 comments
Please sign in to leave a comment.