Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
en:how_to_configure_secure_tamper [2018/04/03 10:11] jypark created [How to configure Secure Tamper] |
en:how_to_configure_secure_tamper [2024/03/07 08:07] (current) kate [How to configure Secure Tamper] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== How to configure Secure Tamper ===== | ===== How to configure Secure Tamper ===== | ||
| ---- | ---- | ||
| - | If the device is separated from the bracket (**Tamper On** event happens), the information on all users, logs, encryption key and SSL certificates configured in the device will be deleted promptly. \\ \\ | + | When **Tamper On** option is ON: If the device is separated from the bracket (**Tamper On** event happens), the information on all users, logs, encryption key and SSL certificates configured in the device will be deleted promptly. \\ |
| - | Supported device: \\ | + | |
| - | {{:en:biostar2_secure_tamper_6.png?nolink&500|}} \\ \\ | + | <callout type="primary" icon="true"> |
| + | ** Supported device: \\ ** | ||
| + | * BioStation 2 V1.6.0 or above \\ | ||
| + | * BioStation A2 V1.5.0 or above \\ | ||
| + | * BioStation L2 V1.4.0 or above \\ | ||
| + | * CoreStation V1.1.0 or above \\ | ||
| + | * BioEntry P2 V1.1.0 or above \\ | ||
| + | * BioLite N2 V1.0.0 or above \\ | ||
| + | * BioEntry W2 V1.2.0 or above \\ | ||
| + | * BioEntry R2 V1.0.0 or above \\ | ||
| + | * XPass D2 V1.0.0 or above \\ | ||
| + | * FaceStation 2 V1.1.0 or above \\ | ||
| + | * FaceStation F2 V1.0.0 or above \\ | ||
| + | * FaceLite V1.0.0 or above \\ | ||
| + | * X-Station 2 V1.0.0 or above \\ | ||
| + | * BioStation 3 V1.0.0 or above \\ | ||
| + | * BioStation 2a V1.0.0 or above \\ | ||
| + | |||
| + | </callout> | ||
| + | \\ | ||
| <callout type="tip" icon="true"> | <callout type="tip" icon="true"> | ||
| - | * Once the **Tamper On** event is generated, the users saved in BioStar 2 cannot be no longer synchronized with the device. In this case, you should transfer users to the device manually. | + | * Once the **Tamper On** event is generated, the users saved in BioStar 2 can no longer be synchronized with the device. In this case, you should transfer users to the device manually. |
| * Slave device is not supported. | * Slave device is not supported. | ||
| </callout> \\ \\ | </callout> \\ \\ | ||
| Line 14: | Line 33: | ||
| There are two cases to configure. \\ \\ | There are two cases to configure. \\ \\ | ||
| === Case 1: === | === Case 1: === | ||
| - | If you do not set **Secure communication with device** to **Not Use** in **Setting** > **SERVER**, you should follow below instructions to configure secure tamper. \\ | + | If you set **Secure communication with device** to **Not Use** in **Setting** > **SERVER**, you should follow below instructions to configure secure tamper. \\ |
| {{:en:biostar2_secure_tamper_1.png?nolink&600|}} \\ \\ | {{:en:biostar2_secure_tamper_1.png?nolink&600|}} \\ \\ | ||
| Line 37: | Line 56: | ||
| {{:en:biostar2_secure_tamper_5.png?nolink&1200|}} \\ \\ | {{:en:biostar2_secure_tamper_5.png?nolink&1200|}} \\ \\ | ||
| - | If you change **Server & device encryption key manual management** into **Use**, you can see below warning message. Please note that, if you configure this setting, the function **Secure Tamper** will be applied automatically. Before you apply this setting, please be careful. | + | If you change **Server & device encryption key manual management** into **Use**, you can see below warning message. |
| + | \\ | ||
| + | Please note that, if you configure this setting, the function **Secure Tamper** will be applied automatically. Before you apply this setting, please be careful. | ||
| {{:en:biostar2_secure_tamper_7.png?nolink&600|}} \\ \\ | {{:en:biostar2_secure_tamper_7.png?nolink&600|}} \\ \\ | ||