---
title: Tamper-Evident Configuration
slug: kronpam-reference-guide-3-9-0/tamper-evident-configuration
description: Learn how to enable or disable the tamper proof parameter and configure the Tamper Proof Log Job in your system. Ensure the batch process runs smoothly by enabling the default tamper proof parameter. Automate background hashing of logs with the Tamper Pro
docTags: 
createdAt: 2022-08-02T09:42:12.000Z
---

The tamper-proof parameter is enabled by default, and hashing is used in the batch process. If tamper-evident is disabled, the batch process will not be executed.

1. Navigate to** Administration >** **System Config Man**.
2. Click **Add.**
3. Add the **tamper.proof.enabled **parameter and set its value as true or false to enable or disable it.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/DXxrdU3q_efy1QTiLj9y1_image.png "System Config Man. section")

1. Navigate to **Administration >** **Job Scheduler**.
2. Click the **Add.**
3. Set the Tamper Proof Log Job parameters. By setting this job, logs will be hashed in the background. This job can be set periodically or triggered manually.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/VHKFw1mlXHc9cd9KPD111_image.png "Job Scheduler Section")

:::hint{type="info"}
**"Tampered Records"** filter button is under the More menu on all logging screens (User Auth Logs, Session Logs, Activity Logs, Command Logs, HTTP Proxy Logs, RADIUS Accounting Logs, TACACS Accounting Logs, Newly Discovered Users, Vault). When clicked, the system analyzes the most recent 10,000 records matching the current filters and lists only the tampered ones at the top. If the total matching record count exceeds 10,000, the user is informed of the analyzed subset size and prompted to narrow the time range or refine filters. The 10,000 threshold is fixed and not configurable. The existing "Enable Tamper Proof Column" control and the new "Tampered Records" button remain synchronized.
:::